From: Stephen Warren <swarren@wwwdotorg.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Tomasz Figa <tomasz.figa@gmail.com>,
Lars Poeschel <larsi@wh2.tu-dresden.de>,
Lars Poeschel <poeschel@lemonage.de>,
Grant Likely <grant.likely@linaro.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ian.campbell@citrix.com>,
galak@codeaurora.org, Pawel Moll <pawel.moll@arm.com>,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
Enric Balletbo i Serra <eballetbo@gmail.com>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Kevin Hilman <khilman@linaro.org>, Balaji T K <balajitk@ti.com>,
Tony Lindgren <tony@atomide.com>,
Jon Hunter <jgchunter@gmail.com>
Subject: Re: [PATCH v2] gpio: interrupt consistency check for OF GPIO IRQs
Date: Thu, 22 Aug 2013 14:53:09 -0600 [thread overview]
Message-ID: <52167A35.2010109@wwwdotorg.org> (raw)
In-Reply-To: <CACRpkdbVYfBS5L+0ejfbTBwPbD9HFB1kV8qnS7DdSydRccxDmg@mail.gmail.com>
On 08/21/2013 05:27 PM, Linus Walleij wrote:
> On Thu, Aug 22, 2013 at 1:10 AM, Stephen Warren <swarren@wwwdotorg.org> wrote:
>>> On Wednesday 21 of August 2013 15:38:54 Lars Poeschel wrote:
>
>>>> To solve this dilemma, perform an interrupt consistency check
>>>> when adding a GPIO chip: if the chip is both gpio-controller and
>>>> interrupt-controller, walk all children of the device tree,
>>
>> It seems a little odd to solve this only for DT. What about the non-DT case?
>
> DT is the hardware configuration system that lets you request
> the same resource in two ways, i.e. it allows one and the same
> node to be both gpio-controller and interrupt-controller, and
> start handing out the same line as both GPIO and IRQ
> independently.
Huh? What stops systems using board files and platform data from having
this issue?
next prev parent reply other threads:[~2013-08-22 20:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 13:38 [PATCH v2] gpio: interrupt consistency check for OF GPIO IRQs Lars Poeschel
2013-08-21 21:49 ` Tomasz Figa
2013-08-21 23:10 ` Stephen Warren
2013-08-21 23:27 ` Linus Walleij
2013-08-22 20:53 ` Stephen Warren [this message]
2013-08-23 9:51 ` Lars Poeschel
2013-08-23 18:38 ` Linus Walleij
2013-08-23 19:49 ` Stephen Warren
2013-08-29 18:51 ` Linus Walleij
2013-08-21 23:36 ` Linus Walleij
2013-08-22 21:10 ` Stephen Warren
2013-08-23 9:40 ` Lars Poeschel
2013-08-23 19:48 ` Stephen Warren
2013-08-26 10:30 ` Lars Poeschel
2013-08-23 18:45 ` Linus Walleij
2013-08-23 19:52 ` Stephen Warren
2013-08-23 19:55 ` Tomasz Figa
2013-08-23 20:55 ` Stephen Warren
2013-08-26 10:45 ` Lars Poeschel
2013-08-27 20:05 ` Stephen Warren
2013-08-29 19:00 ` Linus Walleij
2013-08-30 20:08 ` Stephen Warren
2013-09-02 9:43 ` Lars Poeschel
2013-09-03 12:28 ` Linus Walleij
2013-08-22 9:01 ` Lars Poeschel
2013-08-22 21:08 ` Stephen Warren
2013-08-22 22:30 ` Tomasz Figa
2013-08-22 13:16 ` Andreas Larsson
2013-08-26 10:56 ` Lars Poeschel
2013-08-26 11:29 ` Andreas Larsson
2013-08-26 14:04 ` Lars Poeschel
2013-08-27 6:06 ` Andreas Larsson
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=52167A35.2010109@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=balajitk@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=eballetbo@gmail.com \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=javier.martinez@collabora.co.uk \
--cc=jgchunter@gmail.com \
--cc=khilman@linaro.org \
--cc=larsi@wh2.tu-dresden.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=plagnioj@jcrosoft.com \
--cc=poeschel@lemonage.de \
--cc=santosh.shilimkar@ti.com \
--cc=tomasz.figa@gmail.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).