u-boot.git/drivers/mtd/Makefile, branch v2024.01

drivers/mtd/nvmxip: introduce NVM XIP block storage emulation

2023-04-27T21:01:14Z

add block storage emulation for NVM XIP flash devices Some paltforms such as Corstone-1000 need to see NVM XIP raw flash as a block storage device with read only capability. Here NVM flash devices are devices with addressable memory (e.g: QSPI NOR flash). The implementation is generic and can be used by different platforms. Two drivers are provided as follows. nvmxip-blk : a generic block driver allowing to read from the XIP flash nvmxip Uclass driver : When a device is described in the DT and associated with UCLASS_NVMXIP, the Uclass creates a block device and binds it with the nvmxip-blk. Platforms can use multiple NVM XIP devices at the same time by defining a DT node for each one of them. Signed-off-by: Abdellatif El Khlifi

flash: Remove pic32_flash.c

2022-08-04T20:18:47Z

As the only pic32 platform does not enable flash, this is dead code. Remove it. Cc: Purna Chandra Mandal Signed-off-by: Tom Rini

mtd: remove SPEAr flash driver st_smi

2021-09-24T16:09:47Z

Remove the driver st_smic.c used in SPEAr products and the associated config CONFIG_ST_SMI; this driver is no more used in U-Boot after the commit 570c3dcfc153 ("arm: Remove spear600 boards and the rest of SPEAr support"). Fixes: 570c3dcfc153 ("arm: Remove spear600 boards and the rest of SPEAr support") Signed-off-by: Patrick Delaunay Reviewed-by: Stefan Roese Reviewed-by: Tom Rini

mtd: remove drivers/mtd/mw_eeprom.c

2021-01-18T20:23:06Z

drivers/mtd/mw_eeprom.c contains code that never worked. mw_eeprom_write() and mw_eeprom_read() have incorrect loop conditions: while (len <= 2) { CONFIG_MW_EEPROM is not set anywhere. So let's simply drop the module. Signed-off-by: Heinrich Schuchardt

mtd: Makefile: deep cleanup

2019-12-04T22:10:51Z

Move MTD-related lines out of the root Makefile. Put them in their respective directories. Enclose some of these new lines to skip them when building the SPL. MTD core files and some MTD device drivers are compiled in a mtd.o object and included in the final object only if MTD support is required (there are two different symbols for that, one for U-Boot and one for the SPL). Now that all defconfigs have been fixed, we can stop the logic where enabling a command selects the core files to compile. This logic is broken since selecting a symbol with a 'depends on' will not enforce this secondary dependency. Signed-off-by: Miquel Raynal

cmd: nand/sf: isolate legacy code

2019-12-04T22:10:51Z

The 'sf' command is not supposed to rely on the MTD stack, but both 'sf' and 'nand' commands use helpers located in mtd_uboot.c. Despite their location, these functions do not depend at all on the MTD stack. This file (drivers/mtd/mtd_uboot.c) is only compiled if CONFIG_MTD is selected, which is inconsistent with the current situation. Solve this by moving these three functions (which are only used by the above two commands) out of mtd_uboot.c and put them in a C file only compiled with cmd/sf.c and cmd/nand.c. Signed-off-by: Miquel Raynal [trini: Don't export get_part function now] Signed-off-by: Tom Rini

mtd: rename CONFIG_MTD_DEVICE -> CONFIG_MTD

2019-12-04T04:04:10Z

Like in Linux, just use CONFIG_MTD to compile the MTD stack. Signed-off-by: Miquel Raynal Reviewed-by: Boris Brezillon

mtd: rename CONFIG_MTD -> CONFIG_DM_MTD

2019-12-04T04:04:10Z

CONFIG_MTD must be reserved for the MTD core. Like any other subsystem, prefix the symbol by DM when it comes to DM support. Signed-off-by: Miquel Raynal Reviewed-by: Boris Brezillon [trini: Add Kconfig files] Signed-off-by: Tom Rini

mtd: Add TI HyperBus Memory Controller driver

2019-10-24T07:49:10Z

AM654/J721e has HyperBus Memory Controller that supports HyperFlash and HyperRAM devices. It provides a memory mapped interface to interact with these devices. Add a driver to support the same. Driver calibrates the controller, setups up for MMIO access and probes HyperFlash child node. Signed-off-by: Vignesh Raghavendra Reviewed-by: Stefan Roese

cmd: mtd: add 'mtd' command

2018-10-02T16:42:32Z

There should not be a 'nand' command, a 'sf' command and certainly not a new 'spi-nand' command. Write a 'mtd' command instead to manage all MTD devices/partitions at once. This should be the preferred way to access any MTD device. Signed-off-by: Miquel Raynal Acked-by: Jagan Teki Reviewed-by: Stefan Roese Reviewed-by: Boris Brezillon