From: Felix Radensky <felix@embedded-sol.com>
To: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
"jacmet@sunsite.dk" <jacmet@sunsite.dk>,
grant.likely@secretlab.ca
Subject: Handling multiple GPIO controllers in 8xxx GPIO driver
Date: Tue, 27 Sep 2011 16:59:28 +0300 [thread overview]
Message-ID: <4E81D6C0.3010201@embedded-sol.com> (raw)
Hi,
Looks like 8xxx GPIO driver cannot properly handle interrupts
when multiple GPIO controllers exist in the system.
On Freescale P1022 there are 3 GPIO controllers. All 3 use
the same interrupt line, internal interrupt 31. If all controllers
are defined in device tree set_irq_chained_handler() is invoked
3 times with same hardware irq number. The result is interrupt
storm, mpc8xxx_gpio_irq_cascade() is invoked indefinitely.
What would be the best way to fix the problem ?
Thanks.
Felix Radensky.
next reply other threads:[~2011-09-27 15:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 13:59 Felix Radensky [this message]
2011-09-27 18:29 ` Handling multiple GPIO controllers in 8xxx GPIO driver 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
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=4E81D6C0.3010201@embedded-sol.com \
--to=felix@embedded-sol.com \
--cc=grant.likely@secretlab.ca \
--cc=jacmet@sunsite.dk \
--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 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.