From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>, Jason Cooper <jason@lakedaemon.net>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<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: Fri, 15 May 2015 14:45:46 +0200 [thread overview]
Message-ID: <5555EA7A.6090809@free-electrons.com> (raw)
In-Reply-To: <CACna6rzSPzdCYLPBGYNZB4QKoU_kgPan7aS9p0KWwj0e78JcKg@mail.gmail.com>
Hi Rafał,
On 12/05/2015 07:07, Rafał Miłecki wrote:
> On 11 May 2015 at 15:09, Gregory CLEMENT
> <gregory.clement@free-electrons.com> wrote:
>> 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?
>
> Yes, I checked *all* of them.
>
>
>> Then again, if it id the case I will add it in mvebu/dt soon, unless Andrew,
>> Jason or any other developer who has submitted the dts is aware of a restriction
>> about applying it.
>
> Please wait to see if the binding will be changed or not (tegre patch
> thread discussion).
>
OK I won't take them, and I am waiting for a v2.
Thanks,
Gregory
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: kirkwood: add "nor-jedec" flash compatible binding
Date: Fri, 15 May 2015 14:45:46 +0200 [thread overview]
Message-ID: <5555EA7A.6090809@free-electrons.com> (raw)
In-Reply-To: <CACna6rzSPzdCYLPBGYNZB4QKoU_kgPan7aS9p0KWwj0e78JcKg@mail.gmail.com>
Hi Rafa?,
On 12/05/2015 07:07, Rafa? Mi?ecki wrote:
> On 11 May 2015 at 15:09, Gregory CLEMENT
> <gregory.clement@free-electrons.com> wrote:
>> 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?
>
> Yes, I checked *all* of them.
>
>
>> Then again, if it id the case I will add it in mvebu/dt soon, unless Andrew,
>> Jason or any other developer who has submitted the dts is aware of a restriction
>> about applying it.
>
> Please wait to see if the binding will be changed or not (tegre patch
> thread discussion).
>
OK I won't take them, and I am waiting for a v2.
Thanks,
Gregory
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2015-05-15 12:45 UTC|newest]
Thread overview: 12+ 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-08 6:21 ` Rafał Miłecki
2015-05-11 13:09 ` Gregory CLEMENT
2015-05-11 13:09 ` Gregory CLEMENT
2015-05-11 13:25 ` Andrew Lunn
2015-05-11 13:25 ` Andrew Lunn
2015-05-12 5:15 ` Rafał Miłecki
2015-05-12 5:15 ` Rafał Miłecki
2015-05-12 5:07 ` Rafał Miłecki
2015-05-12 5:07 ` Rafał Miłecki
2015-05-15 12:45 ` Gregory CLEMENT [this message]
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=5555EA7A.6090809@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=andrew@lunn.ch \
--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 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.