diff options
| author | Pekon Gupta <pekon@ti.com> | 2014-01-28 10:12:41 +0400 |
|---|---|---|
| committer | Tony Lindgren <tony@atomide.com> | 2014-02-14 03:10:54 +0400 |
| commit | 980386d2d6d49e0b42f48550853ef1ad6aa5d79a (patch) | |
| tree | b81b66b1bca1d4c2c347de3bdd8fd89a1bc828b2 /arch/arm/mach-omap1/board-nokia770.c | |
| parent | 6b187b21c92b6e2c7e8ef0b450181c37a3f31681 (diff) | |
| download | linux-980386d2d6d49e0b42f48550853ef1ad6aa5d79a.tar.xz | |
ARM: OMAP2+: gpmc: fix: DT ONENAND child nodes not probed when MTD_ONENAND is built as module
Fixes: commit 75d3625e0e86b2d8d77b4e9c6f685fd7ea0d5a96
ARM: OMAP2+: gpmc: add DT bindings for OneNAND
OMAP SoC(s) depend on GPMC controller driver to parse GPMC DT child nodes and
register them platform_device for ONENAND driver to probe later. However this does
not happen if generic MTD_ONENAND framework is built as module (CONFIG_MTD_ONENAND=m).
Therefore, when MTD/ONENAND and MTD/ONENAND/OMAP2 modules are loaded, they are unable
to find any matching platform_device and remain un-binded. This causes on board
ONENAND flash to remain un-detected.
This patch causes GPMC controller to parse DT nodes when
CONFIG_MTD_ONENAND=y || CONFIG_MTD_ONENAND=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>
Diffstat (limited to 'arch/arm/mach-omap1/board-nokia770.c')
0 files changed, 0 insertions, 0 deletions