summaryrefslogtreecommitdiff
path: root/arch/Kconfig
diff options
context:
space:
mode:
authorMasahiro Yamada <yamada.masahiro@socionext.com>2015-03-31 12:47:52 +0900
committerSimon Glass <sjg@chromium.org>2015-04-18 11:11:30 -0600
commitb3d023b4058acc83d211555e62068f84e322bcac (patch)
tree47a7cb39b7eabd1fc80f85dd669468acd47e7f1d /arch/Kconfig
parent5fd2733e5a821acf0358f51d436b61209deac9a5 (diff)
downloadu-boot-imx-b3d023b4058acc83d211555e62068f84e322bcac.zip
u-boot-imx-b3d023b4058acc83d211555e62068f84e322bcac.tar.gz
u-boot-imx-b3d023b4058acc83d211555e62068f84e322bcac.tar.bz2
dm: spi_flash: fix wrong dependency
CONFIG_SPI does not exist in Kconfig in the first place, so the dependency "depends on DM && SPI" is never met, i.e., DM_SPI_FLASH can never be enabled (unless you ignore the dependency in an illegal way. See below.) Actually, some defconfigs such as socfpga_*_defconfig define CONFIG_DM_SPI_FLASH=y, but it never appears in the .config file because of this wrong dependency. On the other hand, all the Tegra boards enable DM_SPI_FLASH because config DM_SPI_FLASH default y silently ignores the dependency. Unfortunately, this style of CONFIG definition is abused everywhere in U-Boot, so we easily miss such a wrong dependency. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Acked-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'arch/Kconfig')
0 files changed, 0 insertions, 0 deletions