From: Tony Lindgren <tony@atomide.com>
To: Pekon Gupta <pekon@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
Daniel Mack <zonque@gmail.com>
Subject: Re: [PATCH] ARM: OMAP2+: gpmc: fix: DT NAND child nodes not probed when MTD_NAND is built as module
Date: Thu, 13 Feb 2014 15:11:16 -0800 [thread overview]
Message-ID: <20140213231116.GL28216@atomide.com> (raw)
In-Reply-To: <1390889561-11410-1-git-send-email-pekon@ti.com>
* Pekon Gupta <pekon@ti.com> [140127 22:15]:
> 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
Applying into omap-for-v3.14/fixes for this and the onenand patch.
Tony
prev parent reply other threads:[~2014-02-13 23:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 6:12 [PATCH] ARM: OMAP2+: gpmc: fix: DT NAND child nodes not probed when MTD_NAND is built as module Pekon Gupta
2014-01-28 6:12 ` [PATCH] ARM: OMAP2+: gpmc: fix: DT ONENAND child nodes not probed when MTD_ONENAND " Pekon Gupta
2014-02-13 23:11 ` Tony Lindgren [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140213231116.GL28216@atomide.com \
--to=tony@atomide.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=linux-omap@vger.kernel.org \
--cc=pekon@ti.com \
--cc=zonque@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.