2017-08-07 21:37:18 +00:00
|
|
|
|
|
|
|
|
menuconfig NAND
|
|
|
|
|
bool "NAND Device Support"
|
|
|
|
|
if NAND
|
2014-10-03 10:21:03 +00:00
|
|
|
|
2014-11-13 11:31:50 +00:00
|
|
|
config SYS_NAND_SELF_INIT
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
This option, if enabled, provides more flexible and linux-like
|
|
|
|
|
NAND initialization process.
|
|
|
|
|
|
2014-10-03 10:21:03 +00:00
|
|
|
config NAND_DENALI
|
|
|
|
|
bool "Support Denali NAND controller"
|
2014-11-13 11:31:50 +00:00
|
|
|
select SYS_NAND_SELF_INIT
|
2017-07-29 01:31:42 +00:00
|
|
|
imply CMD_NAND
|
2014-10-03 10:21:03 +00:00
|
|
|
help
|
|
|
|
|
Enable support for the Denali NAND controller.
|
|
|
|
|
|
2017-08-25 16:12:31 +00:00
|
|
|
config NAND_DENALI_DT
|
|
|
|
|
bool "Support Denali NAND controller as a DT device"
|
|
|
|
|
depends on NAND_DENALI && OF_CONTROL && DM
|
|
|
|
|
help
|
|
|
|
|
Enable the driver for NAND flash on platforms using a Denali NAND
|
|
|
|
|
controller as a DT device.
|
|
|
|
|
|
2014-10-03 10:21:03 +00:00
|
|
|
config SYS_NAND_DENALI_64BIT
|
|
|
|
|
bool "Use 64-bit variant of Denali NAND controller"
|
|
|
|
|
depends on NAND_DENALI
|
|
|
|
|
help
|
|
|
|
|
The Denali NAND controller IP has some variations in terms of
|
|
|
|
|
the bus interface. The DMA setup sequence is completely differenct
|
|
|
|
|
between 32bit / 64bit AXI bus variants.
|
|
|
|
|
|
|
|
|
|
If your Denali NAND controller is the 64-bit variant, say Y.
|
|
|
|
|
Otherwise (32 bit), say N.
|
|
|
|
|
|
|
|
|
|
config NAND_DENALI_SPARE_AREA_SKIP_BYTES
|
|
|
|
|
int "Number of bytes skipped in OOB area"
|
|
|
|
|
depends on NAND_DENALI
|
|
|
|
|
range 0 63
|
|
|
|
|
help
|
|
|
|
|
This option specifies the number of bytes to skip from the beginning
|
|
|
|
|
of OOB area before last ECC sector data starts. This is potentially
|
|
|
|
|
used to preserve the bad block marker in the OOB area.
|
|
|
|
|
|
2015-05-08 17:07:11 +00:00
|
|
|
config NAND_VF610_NFC
|
2017-06-14 03:49:40 +00:00
|
|
|
bool "Support for Freescale NFC for VF610"
|
2015-05-08 17:07:11 +00:00
|
|
|
select SYS_NAND_SELF_INIT
|
2017-07-29 01:31:42 +00:00
|
|
|
imply CMD_NAND
|
2015-05-08 17:07:11 +00:00
|
|
|
help
|
|
|
|
|
Enables support for NAND Flash Controller on some Freescale
|
2017-06-14 03:49:40 +00:00
|
|
|
processors like the VF610, MCF54418 or Kinetis K70.
|
2015-05-08 17:07:11 +00:00
|
|
|
The driver supports a maximum 2k page size. The driver
|
|
|
|
|
currently does not support hardware ECC.
|
|
|
|
|
|
2015-05-08 17:07:12 +00:00
|
|
|
choice
|
|
|
|
|
prompt "Hardware ECC strength"
|
|
|
|
|
depends on NAND_VF610_NFC
|
|
|
|
|
default SYS_NAND_VF610_NFC_45_ECC_BYTES
|
|
|
|
|
help
|
|
|
|
|
Select the ECC strength used in the hardware BCH ECC block.
|
|
|
|
|
|
|
|
|
|
config SYS_NAND_VF610_NFC_45_ECC_BYTES
|
|
|
|
|
bool "24-error correction (45 ECC bytes)"
|
|
|
|
|
|
|
|
|
|
config SYS_NAND_VF610_NFC_60_ECC_BYTES
|
|
|
|
|
bool "32-error correction (60 ECC bytes)"
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
2015-07-23 08:26:16 +00:00
|
|
|
config NAND_PXA3XX
|
|
|
|
|
bool "Support for NAND on PXA3xx and Armada 370/XP/38x"
|
|
|
|
|
select SYS_NAND_SELF_INIT
|
2017-07-29 01:31:42 +00:00
|
|
|
imply CMD_NAND
|
2015-07-23 08:26:16 +00:00
|
|
|
help
|
|
|
|
|
This enables the driver for the NAND flash device found on
|
|
|
|
|
PXA3xx processors (NFCv1) and also on Armada 370/XP (NFCv2).
|
|
|
|
|
|
2015-08-16 12:48:22 +00:00
|
|
|
config NAND_SUNXI
|
2016-06-15 19:09:23 +00:00
|
|
|
bool "Support for NAND on Allwinner SoCs"
|
2015-08-16 12:48:22 +00:00
|
|
|
depends on MACH_SUN4I || MACH_SUN5I || MACH_SUN7I
|
|
|
|
|
select SYS_NAND_SELF_INIT
|
2017-02-27 17:22:08 +00:00
|
|
|
select SYS_NAND_U_BOOT_LOCATIONS
|
2017-07-29 01:31:42 +00:00
|
|
|
imply CMD_NAND
|
2015-08-16 12:48:22 +00:00
|
|
|
---help---
|
2016-06-15 19:09:23 +00:00
|
|
|
Enable support for NAND. This option enables the standard and
|
|
|
|
|
SPL drivers.
|
|
|
|
|
The SPL driver only supports reading from the NAND using DMA
|
|
|
|
|
transfers.
|
2015-08-16 12:48:22 +00:00
|
|
|
|
2017-02-27 17:22:12 +00:00
|
|
|
if NAND_SUNXI
|
|
|
|
|
|
|
|
|
|
config NAND_SUNXI_SPL_ECC_STRENGTH
|
|
|
|
|
int "Allwinner NAND SPL ECC Strength"
|
|
|
|
|
default 64
|
|
|
|
|
|
|
|
|
|
config NAND_SUNXI_SPL_ECC_SIZE
|
|
|
|
|
int "Allwinner NAND SPL ECC Step Size"
|
|
|
|
|
default 1024
|
|
|
|
|
|
|
|
|
|
config NAND_SUNXI_SPL_USABLE_PAGE_SIZE
|
|
|
|
|
int "Allwinner NAND SPL Usable Page Size"
|
|
|
|
|
default 1024
|
|
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
|
2015-11-17 09:00:09 +00:00
|
|
|
config NAND_ARASAN
|
|
|
|
|
bool "Configure Arasan Nand"
|
2017-07-29 01:31:42 +00:00
|
|
|
imply CMD_NAND
|
2015-11-17 09:00:09 +00:00
|
|
|
help
|
|
|
|
|
This enables Nand driver support for Arasan nand flash
|
|
|
|
|
controller. This uses the hardware ECC for read and
|
|
|
|
|
write operations.
|
|
|
|
|
|
2016-10-08 12:30:25 +00:00
|
|
|
config NAND_MXS
|
|
|
|
|
bool "MXS NAND support"
|
2017-02-10 18:33:34 +00:00
|
|
|
depends on MX6 || MX7
|
2017-07-29 01:31:42 +00:00
|
|
|
imply CMD_NAND
|
2016-10-08 12:30:25 +00:00
|
|
|
help
|
|
|
|
|
This enables NAND driver for the NAND flash controller on the
|
|
|
|
|
MXS processors.
|
|
|
|
|
|
2016-09-27 05:25:46 +00:00
|
|
|
config NAND_ZYNQ
|
|
|
|
|
bool "Support for Zynq Nand controller"
|
|
|
|
|
select SYS_NAND_SELF_INIT
|
2017-07-29 01:31:42 +00:00
|
|
|
imply CMD_NAND
|
2016-09-27 05:25:46 +00:00
|
|
|
help
|
|
|
|
|
This enables Nand driver support for Nand flash controller
|
|
|
|
|
found on Zynq SoC.
|
|
|
|
|
|
2015-05-08 17:07:11 +00:00
|
|
|
comment "Generic NAND options"
|
|
|
|
|
|
|
|
|
|
# Enhance depends when converting drivers to Kconfig which use this config
|
|
|
|
|
# option (mxc_nand, ndfc, omap_gpmc).
|
|
|
|
|
config SYS_NAND_BUSWIDTH_16BIT
|
|
|
|
|
bool "Use 16-bit NAND interface"
|
|
|
|
|
depends on NAND_VF610_NFC
|
|
|
|
|
help
|
|
|
|
|
Indicates that NAND device has 16-bit wide data-bus. In absence of this
|
|
|
|
|
config, bus-width of NAND device is assumed to be either 8-bit and later
|
|
|
|
|
determined by reading ONFI params.
|
|
|
|
|
Above config is useful when NAND device's bus-width information cannot
|
|
|
|
|
be determined from on-chip ONFI params, like in following scenarios:
|
|
|
|
|
- SPL boot does not support reading of ONFI parameters. This is done to
|
|
|
|
|
keep SPL code foot-print small.
|
|
|
|
|
- In current U-Boot flow using nand_init(), driver initialization
|
|
|
|
|
happens in board_nand_init() which is called before any device probe
|
|
|
|
|
(nand_scan_ident + nand_scan_tail), thus device's ONFI parameters are
|
|
|
|
|
not available while configuring controller. So a static CONFIG_NAND_xx
|
|
|
|
|
is needed to know the device's bus-width in advance.
|
|
|
|
|
|
2016-06-06 08:16:57 +00:00
|
|
|
if SPL
|
|
|
|
|
|
|
|
|
|
config SYS_NAND_U_BOOT_LOCATIONS
|
|
|
|
|
bool "Define U-boot binaries locations in NAND"
|
|
|
|
|
help
|
|
|
|
|
Enable CONFIG_SYS_NAND_U_BOOT_OFFS though Kconfig.
|
|
|
|
|
This option should not be enabled when compiling U-boot for boards
|
|
|
|
|
defining CONFIG_SYS_NAND_U_BOOT_OFFS in their include/configs/<board>.h
|
|
|
|
|
file.
|
|
|
|
|
|
2015-08-21 19:49:51 +00:00
|
|
|
config SYS_NAND_U_BOOT_OFFS
|
|
|
|
|
hex "Location in NAND to read U-Boot from"
|
mtd: sunxi: Change U-Boot offset
The default U-Boot offset for the Allwinner SoCs was set to 32kB.
This was probably to try to maintain some compatibility with the current
image that we build for the MMC where the U-Boot binary is also located at
a 32kB offset.
However, this causes a number of issues. The first one is that it prevents
us from using a backup SPL entirely, which is troublesome in case where the
first would be corrupt (especially on MLC which have a higher number of
bitflips).
We also cannot use the original MMC image on the NAND, because we need to
prepare the SPL image to include the ECCs and randomizer settings, which
reduces the interest of setting it at that particular offset.
It also prevents us from upgrading and flashing the U-Boot and SPLs
independantly, since it's very likely that it will fall in the same erase
block.
Since that default wasn't used by any board, change it for 8MB, which will
be in an erase block of its own, all the erase blocks being multiple of
two. The highest erase block size we encountered is 4MB, which means that
in this particular setup, the first and second erase blocks will be for the
SPL and its backup, and the third for U-Boot.
Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
Reviewed-by: Jagan Teki <jagan@openedev.com>
2017-02-27 17:22:09 +00:00
|
|
|
default 0x800000 if NAND_SUNXI
|
2016-06-06 08:16:57 +00:00
|
|
|
depends on SYS_NAND_U_BOOT_LOCATIONS
|
2015-08-21 19:49:51 +00:00
|
|
|
help
|
|
|
|
|
Set the offset from the start of the nand where u-boot should be
|
|
|
|
|
loaded from.
|
|
|
|
|
|
2016-06-06 08:16:58 +00:00
|
|
|
config SYS_NAND_U_BOOT_OFFS_REDUND
|
|
|
|
|
hex "Location in NAND to read U-Boot from"
|
|
|
|
|
default SYS_NAND_U_BOOT_OFFS
|
|
|
|
|
depends on SYS_NAND_U_BOOT_LOCATIONS
|
|
|
|
|
help
|
|
|
|
|
Set the offset from the start of the nand where the redundant u-boot
|
|
|
|
|
should be loaded from.
|
|
|
|
|
|
2014-10-03 10:21:04 +00:00
|
|
|
config SPL_NAND_DENALI
|
|
|
|
|
bool "Support Denali NAND controller for SPL"
|
|
|
|
|
help
|
|
|
|
|
This is a small implementation of the Denali NAND controller
|
|
|
|
|
for use on SPL.
|
|
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
|
2017-08-07 21:37:18 +00:00
|
|
|
endif # if NAND
|
