From: Andrew Lunn <andrew@lunn.ch>
To: Gregory CLEMENT <gregory.clement@free-electrons.com>
Cc: Jason Cooper <jason@lakedaemon.net>,
Rafa?? Mi??ecki <zajec5@gmail.com>,
linux-mtd@lists.infradead.org,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Simon Guinot <simon.guinot@sequanux.org>
Subject: Re: [PATCH] ARM: dts: kirkwood: add "nor-jedec" flash compatible binding
Date: Mon, 11 May 2015 15:25:04 +0200 [thread overview]
Message-ID: <20150511132504.GR18496@lunn.ch> (raw)
In-Reply-To: <5550AA08.5060001@free-electrons.com>
On Mon, May 11, 2015 at 03:09:28PM +0200, Gregory CLEMENT wrote:
> Hi Rafa??,
>
> On 08/05/2015 08:21, Rafa?? Mi??ecki wrote:
> > Starting with commits
> > 8ff16cf ("Documentation: devicetree: m25p80: add "nor-jedec" binding")
> > 1103b85 ("mtd: m25p80: bind to "nor-jedec" ID, for auto-detection")
> > we have "nor-jedec" binding indicating support for JEDEC identification.
>
> I have the same question that for mvebu: did you actually check that all
> the NOR flash referenced in the dts supports the JEDEC identification?
Hi Gregory
That is a good question, but i've no knowledge in this area.
Rafa??, what is the long term plan? Will the device specific property
be removed sometime in the future, and nor-jedec probing be used to
identify the device? Is this already the actual behaviour? I've seen
warnings when the DT entry specified the wrong device, something like:
Found ABC, Expected XYZ.
Andrew
next prev parent reply other threads:[~2015-05-11 13:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 6:21 [PATCH] ARM: dts: kirkwood: add "nor-jedec" flash compatible binding Rafał Miłecki
2015-05-11 13:09 ` Gregory CLEMENT
2015-05-11 13:25 ` Andrew Lunn [this message]
2015-05-12 5:15 ` Rafał Miłecki
2015-05-12 5:07 ` Rafał Miłecki
2015-05-15 12:45 ` Gregory CLEMENT
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=20150511132504.GR18496@lunn.ch \
--to=andrew@lunn.ch \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=simon.guinot@sequanux.org \
--cc=zajec5@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox