public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Ian Molton <spyro@f2s.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Kernel-discuss] RFC - platform device, IRQs and SoC devices
Date: Sat, 25 Nov 2006 12:29:10 +0000	[thread overview]
Message-ID: <20061125122910.GA12104@flint.arm.linux.org.uk> (raw)
In-Reply-To: <45682B0E.4060202@f2s.com>

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:

  reply	other threads:[~2006-11-25 12:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-21 16:07 RFC - platform device, IRQs and SoC devices Ian Molton
2006-11-25 11:37 ` [Kernel-discuss] " Ian Molton
2006-11-25 12:29   ` Russell King [this message]
2006-11-25 12:51     ` Ian Molton
2006-11-25 13:02       ` Russell King

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=20061125122910.GA12104@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spyro@f2s.com \
    /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