linux-kernel - Re: [Kernel-discuss] RFC - platform device, IRQs and SoC devices

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <45682B0E.4060202@f2s.com>
Date:	Sat, 25 Nov 2006 11:37:50 +0000
From:	Ian Molton <spyro@....com>
To:	linux-kernel@...r.kernel.org
Subject: Re: [Kernel-discuss] RFC - platform device, IRQs and SoC devices

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...
-
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/