All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: "David Müller" <d.mueller@elsoft.ch>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Additional IRQ handlers in ppc4xx_init_IRQ()
Date: Tue, 23 Oct 2001 14:32:56 -0400	[thread overview]
Message-ID: <3BD5B7D8.C060B6AF@mvista.com> (raw)
In-Reply-To: 3BD517E5.5090204@elsoft.ch


"David Müller (ELSOFT AG)" wrote:

> I have a question regarding the registration of additional IRQ handlers
> for a PPC405GP based board.

Where are Matt's changes for the Tivo?  It would address this and give
us another example of how this should be structured.


> extended ppc4xx_init_IRQ as follows:

This is not an appealing solution.  We should change ppc4xx_pic_init()
to initialize the internal interrupt controller irq descriptor, and then
create a standard board initialization call for board specific changes.


> static void __init
> ppc4xx_init_IRQ(void)
> {
>         int i;
>
>         ppc4xx_pic_init();
>
+	  ppc4xx_pic_board_init();
>         return;
> }
>

The '...board_init()' function can be empty for those boards that don't
require any additional controller initialization.


>         for (i = 0; i < NR_IRQS; i++)
>                 irq_desc[i].handler = ppc4xx_pic;

The NR_IRQS should represent the total number of interrupts across all
controllers.  The pic_init() should change this loop to initialize either
NR_AIC or NR_UIC depending upon a 403 or 405 interrupt controller.  No
#ifdefs necessary.

Thanks.


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-10-23 18:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-23  7:10 Additional IRQ handlers in ppc4xx_init_IRQ() David Müller (ELSOFT AG)
2001-10-23 18:32 ` Dan Malek [this message]
2001-10-24  9:26   ` David Müller (ELSOFT AG)

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=3BD5B7D8.C060B6AF@mvista.com \
    --to=dan@mvista.com \
    --cc=d.mueller@elsoft.ch \
    --cc=linuxppc-embedded@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 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.