From: Mark Jackson <mpfj-list@mimc.co.uk>
To: Jon Hunter <jon-hunter@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Afzal Mohammed <afzal@ti.com>
Subject: Re: DT GPMC SRAM and NOR flash support ?
Date: Thu, 07 Feb 2013 10:34:08 +0000 [thread overview]
Message-ID: <51138320.8040706@mimc.co.uk> (raw)
In-Reply-To: <51137923.4070301@mimc.co.uk>
On 07/02/13 09:51, Mark Jackson wrote:
> Okay ... I have made some progress, but it's not ideal.
<snip>
> But the physmap driver (of_flash_probe()) is unable to use this information. It seems that although
> I can call of_flash_probe() from my NOR setup code, the platform_device being reference is wrong.
>
> The platform_device passed to my gpmc_probe_nor_child() routine from gpmc_probe_dt() points to my
> gpmc entry (above), but the physmap probe requires its own DT entry (rather than a node child such
> as my NOR entry with the GPMC device entry).
>
> So I need to have any extra entry in the DT file as follows:-
>
> nor-flash@08000000 {
> compatible = "spansion,s29gl064n90t", "cfi-flash";
> reg = <0x08000000 0x00800000>;
> bank-width = <2>;
> };
>
> So the GPMC entry handles all the chip select and timing setup, but the 2nd entry is the only one
> the physmap driver can see.
>
> Would it be acceptable to re-code of_flash_probe() to allow either a child device_node to be passed
> or a platform_device ?
Or is it acceptable to simply state the gpmc portion is for setting up the chip access, and you *do*
need a separate physmap section ?
That's certainly easier, and it works without any changes to the physmap driver.
Regards
Mark J.
next prev parent reply other threads:[~2013-02-07 10:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 16:56 DT GPMC SRAM and NOR flash support ? Mark Jackson
2013-02-01 17:12 ` Jon Hunter
2013-02-01 19:39 ` Mark Jackson
2013-02-05 16:16 ` Mark Jackson
2013-02-05 16:35 ` Jon Hunter
2013-02-05 16:48 ` Mark Jackson
2013-02-05 17:08 ` Jon Hunter
2013-02-07 9:51 ` Mark Jackson
2013-02-07 10:34 ` Mark Jackson [this message]
2013-02-09 0:43 ` Jon Hunter
2013-02-09 13:27 ` Ezequiel Garcia
2013-02-11 22:21 ` Jon Hunter
2013-02-12 14:36 ` Ezequiel Garcia
2013-02-13 21:07 ` Jon Hunter
2013-02-14 10:18 ` Ezequiel Garcia
2013-02-15 7:42 ` Jon Hunter
2013-03-01 21:08 ` Ezequiel Garcia
2013-03-01 21:42 ` Ezequiel Garcia
2013-03-01 22:23 ` Jon Hunter
2013-02-06 5:07 ` Mohammed, Afzal
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=51138320.8040706@mimc.co.uk \
--to=mpfj-list@mimc.co.uk \
--cc=afzal@ti.com \
--cc=jon-hunter@ti.com \
--cc=linux-omap@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).