| commit | 2263b85e8822bc6f851281ce4f3567bd3877e933 | [log] [tgz] |
|---|---|---|
| author | Adam Ford <aford173@gmail.com> | Wed Jan 24 08:00:13 2018 -0600 |
| committer | Tom Rini <trini@konsulko.com> | Fri Feb 02 18:03:35 2018 -0500 |
| tree | c39ff7dbc957808e8d47d2b4cada93e228aec213 | |
| parent | ff213ba4af6bf0768093c6181d66738725ecaffd [diff] |
Convert CONFIG_SYS_MAX_NAND_DEVICE to Kconfig and add CONFIG_NAND Many boards are setting NAND parameters if/when CMD_NAND is set when in reality they should probably be doing it it CONFIG_NAND is set. Previuos attempts to make CMD_NAND select CONFIG_NAND resulted in some recursive selections, so I think this should be a better solution Using the moveconfig tool, I searched for CONFIG_SYS_MAX_NAND_DEVICE and then any suspicious defconfig files left behind, I added CONFIG_NAND=y, then retested the migration against that list. This should allows us to make the CONFIG_CMD_NAND now dependant on CONFIG_NAND and enable a bunch of NAND parameters under the NAND menu without appearing 'suspicious' This converts the following to Kconfig: CONFIG_SYS_MAX_NAND_DEVICE Signed-off-by: Adam Ford <aford173@gmail.com> Acked-by: <christophe.leroy@c-s.fr> [trini: Rework some headers given how CONFIG_NAND was abused] Signed-off-by: Tom Rini <trini@konsulko.com>