diff options
| author | Pekon Gupta <pekon@ti.com> | 2014-01-28 11:42:40 +0530 |
|---|---|---|
| committer | Tony Lindgren <tony@atomide.com> | 2014-02-13 15:10:42 -0800 |
| commit | 6b187b21c92b6e2c7e8ef0b450181c37a3f31681 (patch) | |
| tree | 4e8363c7050d096ca64d10c2a2087d05b908b91f | |
| parent | 2d6ac29e6a043c3adc3e82f5200ae1e07617e3ea (diff) | |
| download | linux-6b187b21c92b6e2c7e8ef0b450181c37a3f31681.tar.gz linux-6b187b21c92b6e2c7e8ef0b450181c37a3f31681.tar.bz2 linux-6b187b21c92b6e2c7e8ef0b450181c37a3f31681.zip | |
ARM: OMAP2+: gpmc: fix: DT NAND child nodes not probed when MTD_NAND is built as module
Fixes: commit bc6b1e7b86f5d8e4a6fc1c0189e64bba4077efe0
ARM: OMAP: gpmc: add DT bindings for GPMC timings and NAND
OMAP SoC(s) depend on GPMC controller driver to parse GPMC DT child nodes and
register them platform_device for NAND driver to probe later. However this does
not happen if generic MTD_NAND framework is built as module (CONFIG_MTD_NAND=m).
Therefore, when MTD/NAND and MTD/NAND/OMAP2 modules are loaded, they are unable
to find any matching platform_device and remain un-binded. This causes on board
NAND flash to remain un-detected.
This patch causes GPMC controller to parse DT nodes when
CONFIG_MTD_NAND=y || CONFIG_MTD_NAND=m
CC: <stable@vger.kernel.org> # 3.9.x+
Signed-off-by: Pekon Gupta <pekon@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
| -rw-r--r-- | arch/arm/mach-omap2/gpmc.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-omap2/gpmc.c index d24926e6340f..c77a84b63a59 100644 --- a/arch/arm/mach-omap2/gpmc.c +++ b/arch/arm/mach-omap2/gpmc.c @@ -1339,7 +1339,7 @@ static void __maybe_unused gpmc_read_timings_dt(struct device_node *np, of_property_read_bool(np, "gpmc,time-para-granularity"); } -#ifdef CONFIG_MTD_NAND +#if IS_ENABLED(CONFIG_MTD_NAND) static const char * const nand_xfer_types[] = { [NAND_OMAP_PREFETCH_POLLED] = "prefetch-polled", |