From: Rob Herring <robherring2@gmail.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>,
linux-samsung-soc@vger.kernel.org, l.krishna@samsung.com,
devicetree-discuss@lists.ozlabs.org, joshi@samsung.com,
inki.dae@samsung.com, kgene.kim@samsung.com,
Vikas Sajjan <vikas.sajjan@linaro.org>,
linaro-kernel@lists.linaro.org,
Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [PATCH] ARM: dts: add interrupt-names property to get interrupt resource by name
Date: Mon, 18 Mar 2013 17:27:35 -0500 [thread overview]
Message-ID: <514794D7.3060903@gmail.com> (raw)
In-Reply-To: <514758C3.7070601@wwwdotorg.org>
On 03/18/2013 01:11 PM, Stephen Warren wrote:
> On 03/18/2013 09:50 AM, Rob Herring wrote:
>> On 03/13/2013 05:42 PM, Sylwester Nawrocki wrote:
>>> Rob,
>>>
>>> On 03/13/2013 03:39 PM, Rob Herring wrote:
>>>> I fail to see what the hack is. The order of interrupt properties must
>>>> be defined by the binding. interrupt-names is auxiliary data and must
>>>> not be required by an OS.
>
> Is that true for all foo-names properties, or only for interrupt-names?
> I was under the impression that foo-names was specifically invented so
> that the order of the entries didn't matter, and instead they could be
> requested by name.
I think it depends on the specific name the property is tied too. For
interrupt and reg properties which have a long history and convention,
the order should be defined. IIRC, this was Grant's position too. For
new bindings, perhaps we can be more lenient.
Rob
next prev parent reply other threads:[~2013-03-18 22:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 11:26 [PATCH] ARM: dts: add interrupt-names property to get interrupt resource by name Vikas Sajjan
2013-03-13 14:39 ` Rob Herring
2013-03-13 22:42 ` Sylwester Nawrocki
2013-03-18 15:50 ` Rob Herring
2013-03-18 18:11 ` Stephen Warren
2013-03-18 22:27 ` Rob Herring [this message]
2013-03-18 23:00 ` Arnd Bergmann
2013-03-18 23:05 ` Stephen Warren
2013-03-19 22:31 ` Sylwester Nawrocki
2013-03-19 21:40 ` Sylwester Nawrocki
2013-03-20 3:22 ` Vikas Sajjan
2013-03-15 4:04 ` Vikas Sajjan
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=514794D7.3060903@gmail.com \
--to=robherring2@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=inki.dae@samsung.com \
--cc=joshi@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=l.krishna@samsung.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=sylvester.nawrocki@gmail.com \
--cc=vikas.sajjan@linaro.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).