| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Sat, 25 Nov 2006 12:29:10 +0000 From: Russell King <rmk+lkml@....linux.org.uk> To: Ian Molton <spyro@....com> Cc: linux-kernel@...r.kernel.org Subject: Re: [Kernel-discuss] RFC - platform device, IRQs and SoC devices On Sat, Nov 25, 2006 at 11:37:50AM +0000, Ian Molton wrote: > Ian Molton wrote: > >Hi there. > > > >Im working on some SoC type devices attached to the system bus of my ARM > >devboard in an isa-like way. > > > >The devices are small SoC (System On Chip) types, with one IRQ routed to > >the half dozen (sub)devices on board the SoC. > > I just thought of a 'third way'. > > let IRQchips have their own struct irq_desc and have subdevice IRQs > start from 0. > > since those IRQs can only be raised by the parent chip I think this > ought to work, and would eliminated the problem of a fixed size irq array... It's quite possible to have: IRQ chip 0 irqchip_0 1 irqchip_0 2 irqchip_1 3 irqchip_0 4 irqchip_0 5 irqchip_1 6 irqchip_2 7 irqchip_2 8 irqchip_2 9 irqchip_1 Where do you start '0' for each irqchip? How do you split the irq_desc array between the irqchips? (and yes there are platforms merged which do this.) -- Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists