From: Felix Radensky <felix@embedded-sol.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
Tabi Timur-B04825 <B04825@freescale.com>
Subject: Re: Handling multiple GPIO controllers in 8xxx GPIO driver
Date: Thu, 29 Sep 2011 23:44:08 +0300 [thread overview]
Message-ID: <4E84D898.3020006@embedded-sol.com> (raw)
In-Reply-To: <20110929172737.GF6800@ponder.secretlab.ca>
Hi Grant,
On 09/29/2011 08:27 PM, Grant Likely wrote:
> On Wed, Sep 28, 2011 at 08:52:30PM +0000, Tabi Timur-B04825 wrote:
>> On Tue, Sep 27, 2011 at 1:29 PM, Grant Likely<grant.likely@secretlab.ca> wrote:
>>
>>> The solution is to make the gpio driver register as a regular
>>> interrupt handler, and not as a chained handler.
>> I was wondering about that.
>>
>> What exactly is a chained handler? How is it different from a regular handler?
> A chained handler has an expedited path through the interrupt code for
> handling it (basically, it skips handling it at the parent controller
> and passes through to the child, but it cannot handle multiple chained
> children on a single irq input.
>
> g.
>
I may be missing something, but please see this discussion:
http://comments.gmane.org/gmane.linux.ports.arm.kernel/76025
Chained handler is suggested as the solution for very similar problem.
(several peripherals sharing the same hardware IRQ line. If it's possible
on ARM, it should be doable on powerpc, right ?
Felix.
prev parent reply other threads:[~2011-09-29 20:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 13:59 Handling multiple GPIO controllers in 8xxx GPIO driver Felix Radensky
2011-09-27 18:29 ` Grant Likely
2011-09-27 22:07 ` Felix Radensky
2011-09-28 20:52 ` Tabi Timur-B04825
2011-09-29 17:27 ` Grant Likely
2011-09-29 20:22 ` Tabi Timur-B04825
2011-09-29 21:36 ` Grant Likely
2011-09-29 20:44 ` Felix Radensky [this message]
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=4E84D898.3020006@embedded-sol.com \
--to=felix@embedded-sol.com \
--cc=B04825@freescale.com \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.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).