From: akuster <akuster@dslextreme.com>
To: ppc_devel <linuxppc-dev@lists.linuxppc.org>
Subject: [RFC/Patch] ppc4xx_pic
Date: Sun, 14 Jul 2002 15:09:54 -0700 [thread overview]
Message-ID: <3D31F6B2.3010900@dslextreme.com> (raw)
Hello;
While farting around with some 4xx drivers, I came accross a few that
changed the level and polarity of their irq before calling request_irq().
So I am thinking of adopting how openpic defines and gets irq level and
polarity information and use it to define external irqs in the board.c
files.
Basicaly I check to see if a table exists and if so, update the
interrupt controller during ppc4xx_pic_init with the proper values.
Since the on-chip devices are all ready setup by the bootrom or at
least we have been assuming this is the case , I am not going to worry
about them.
Since I plan on updating the ppc4xx_pic , I have also added the ability
to properly report the level of the interrupt to irq_desc[] so that
proc/intrrupts will correct.
what do you think?
armin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-07-14 22:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-14 22:09 akuster [this message]
2002-07-15 2:52 ` [RFC/Patch] ppc4xx_pic Dan Malek
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=3D31F6B2.3010900@dslextreme.com \
--to=akuster@dslextreme.com \
--cc=linuxppc-dev@lists.linuxppc.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).