projects / J-u-boot.git / blame
| Commit | Line | Data |
|---|---|---|
| 810fd696 JT |
1 | menu "SPI Flash Support" |
| 2 | ||
| f94a1bed SG |
3 | config DM_SPI_FLASH |
| 4 | bool "Enable Driver Model for SPI flash" | |
| b3d023b4 | 5 | depends on DM && DM_SPI |
| f94a1bed SG |
6 | help |
| 7 | Enable driver model for SPI flash. This SPI flash interface | |
| 8 | (spi_flash_probe(), spi_flash_write(), etc.) is then | |
| 9 | implemented by the SPI flash uclass. There is one standard | |
| 10 | SPI flash driver which knows how to probe most chips | |
| 11 | supported by U-Boot. The uclass interface is defined in | |
| 12 | include/spi_flash.h, but is currently fully compatible | |
| 13 | with the old interface to avoid confusion and duplication | |
| 14 | during the transition parent. SPI and SPI flash must be | |
| 15 | enabled together (it is not possible to use driver model | |
| 16 | for one and not the other). | |
| 949dd81b SG |
17 | |
| 18 | config SPI_FLASH_SANDBOX | |
| 19 | bool "Support sandbox SPI flash device" | |
| 20 | depends on SANDBOX && DM_SPI_FLASH | |
| 21 | help | |
| 22 | Since sandbox cannot access real devices, an emulation mechanism is | |
| 23 | provided instead. Drivers can be connected up to the sandbox SPI | |
| 24 | bus (see CONFIG_SANDBOX_SPI) and SPI traffic will be routed to this | |
| 25 | device. Typically the contents of the emulated SPI flash device is | |
| 26 | stored in a file on the host filesystem. | |
| 810fd696 | 27 | |
| 2ce7e2b6 JT |
28 | config SPI_FLASH |
| 29 | bool "Legacy SPI Flash Interface support" | |
| 30 | help | |
| 31 | Enable the legacy SPI flash support. This will include basic | |
| 32 | standard support for things like probing, read / write, and | |
| 33 | erasing through cmd_sf interface. | |
| 34 | ||
| 35 | If unsure, say N | |
| 36 | ||
| 84d31b3b JT |
37 | config SPI_FLASH_BAR |
| 38 | bool "SPI flash Bank/Extended address register support" | |
| 39 | depends on SPI_FLASH | |
| 40 | help | |
| 41 | Enable the SPI flash Bank/Extended address register support. | |
| 42 | Bank/Extended address registers are used to access the flash | |
| 43 | which has size > 16MiB in 3-byte addressing. | |
| 44 | ||
| cd9accdc JT |
45 | config SPI_FLASH_DATAFLASH |
| 46 | bool "AT45xxx DataFlash support" | |
| 47 | depends on SPI_FLASH && DM_SPI_FLASH | |
| 48 | help | |
| 49 | Enable the access for SPI-flash-based AT45xxx DataFlash chips. | |
| 50 | DataFlash is a kind of SPI flash. Most AT45 chips have two buffers | |
| 51 | in each chip, which may be used for double buffered I/O; but this | |
| 52 | driver doesn't (yet) use these for any kind of i/o overlap or prefetching. | |
| 53 | ||
| 54 | Sometimes DataFlash is packaged in MMC-format cards, although the | |
| 55 | MMC stack can't (yet?) distinguish between MMC and DataFlash | |
| 56 | protocols during enumeration. | |
| 57 | ||
| 58 | If unsure, say N | |
| 59 | ||
| 7678dd93 JT |
60 | config SPI_FLASH_MTD |
| 61 | bool "SPI Flash MTD support" | |
| 62 | depends on SPI_FLASH | |
| 63 | help | |
| 64 | Enable the MTD support for spi flash layer, this adapter is for | |
| 65 | translating mtd_read/mtd_write commands into spi_flash_read/write | |
| 66 | commands. It is not intended to use it within sf_cmd or the SPI | |
| 67 | flash subsystem. Such an adapter is needed for subsystems like | |
| 68 | UBI which can only operate on top of the MTD layer. | |
| 69 | ||
| 70 | If unsure, say N | |
| 71 | ||
| 810fd696 | 72 | endmenu # menu "SPI Flash Support" |