Re: irq consolidation

Andrey Panin (pazke@donpac.ru)
Mon, 16 Jun 2003 16:09:12 +0400


This is a MIME-formatted message. If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--=_courier-26729-1055765411-0001-2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 163, 06 12, 2003 at 09:34:06PM +1000, Anton Blanchard wrote:
>=20
> > I believe Andrey's IRQ consolidation provides a single flat IRQ
> > structure. Unfortunately, this doesn't reflect the reality that we
> > have on many ARM platforms - it remains the case that we need to
> > decode IRQs on a multi-level basis.
>=20
> Yes its still a flat structure. On ppc32/64 we offset the interrupts on
> the main controller to provide a space for ISA interrupts to go. Not
> great but it works for us.

May be I missed the point, but it isn't flat.

You can define HAVE_ARCH_IRQ_DESC and provide your own irq_desc(irq)
function which will translate irq number to the corresponding=20
irq_desc_t structure. You are free to implement any irq mappings
behind the irq_desc(). NR_IRQS is used only as maximal irq number.
So what is the problem ?
=20
> One thing Paul suggested was to have a flag to mark an interrupt as a
> cascade in the irq descriptor. If its set then we also provide a
> get_irq() method (perhaps stashed away in the ->action field). That gives
> us nested interrupt handling in generic code. (assuming you can
> partition your irq numbers somehow)
>=20
> Anton

--=20
Andrey Panin | Linux and UNIX system administrator
pazke@donpac.ru | PGP key: wwwkeys.pgp.net

--=_courier-26729-1055765411-0001-2
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE+7bNoby9O0+A2ZecRAsA5AKCA4rJBVWpl/AaDcBfCtarpmsMsWACfQgPP
1HAQ/x5TKmDhxbN+Nzbm9r8=
=Z0Wk
-----END PGP SIGNATURE-----

--=_courier-26729-1055765411-0001-2--