linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
* SPARSE_IRQ on Kirkwood
@ 2013-07-17 20:09 Gerlando Falauto
  2013-11-11 14:45 ` Gerlando Falauto
  0 siblings, 1 reply; 4+ messages in thread
From: Gerlando Falauto @ 2013-07-17 20:09 UTC (permalink / raw)
  To: linux-arm-kernel

Hi everyone,

newbie's question: are sparse IRQs [going to be] supported on Kirkwood?
I thought irq domains were pretty much the same thing...
So if I understand correctly, without sparse IRQs I still have to 
increase NR_IRQS within arch/arm/mach-kirkwood/include/mach/irqs.h in 
order to support additional PICs.

Thanks in advance!
Gerlando

^ permalink raw reply	[flat|nested] 4+ messages in thread

* SPARSE_IRQ on Kirkwood
  2013-07-17 20:09 SPARSE_IRQ on Kirkwood Gerlando Falauto
@ 2013-11-11 14:45 ` Gerlando Falauto
  2013-11-11 14:51   ` Andrew Lunn
  2013-11-11 14:57   ` Thomas Petazzoni
  0 siblings, 2 replies; 4+ messages in thread
From: Gerlando Falauto @ 2013-11-11 14:45 UTC (permalink / raw)
  To: linux-arm-kernel

Hi,

a few months later, my understanding has not changed much... could 
anyone please shed some light?

Thanks!
Gerlando

On 07/17/2013 10:09 PM, Gerlando Falauto wrote:
> Hi everyone,
>
> newbie's question: are sparse IRQs [going to be] supported on Kirkwood?
> I thought irq domains were pretty much the same thing...
> So if I understand correctly, without sparse IRQs I still have to
> increase NR_IRQS within arch/arm/mach-kirkwood/include/mach/irqs.h in
> order to support additional PICs.
>
> Thanks in advance!
> Gerlando
>

^ permalink raw reply	[flat|nested] 4+ messages in thread

* SPARSE_IRQ on Kirkwood
  2013-11-11 14:45 ` Gerlando Falauto
@ 2013-11-11 14:51   ` Andrew Lunn
  2013-11-11 14:57   ` Thomas Petazzoni
  1 sibling, 0 replies; 4+ messages in thread
From: Andrew Lunn @ 2013-11-11 14:51 UTC (permalink / raw)
  To: linux-arm-kernel

On Mon, Nov 11, 2013 at 03:45:31PM +0100, Gerlando Falauto wrote:
> Hi,
> 
> a few months later, my understanding has not changed much... could
> anyone please shed some light?

I _think_ sparse_IRQ is a pre-requisite for multiarch kernel. So it is
something we definitely want to do. I've no idea what is actually
required, but i do have it somewhere near the top of my TODO list.

	  Andrew

^ permalink raw reply	[flat|nested] 4+ messages in thread

* SPARSE_IRQ on Kirkwood
  2013-11-11 14:45 ` Gerlando Falauto
  2013-11-11 14:51   ` Andrew Lunn
@ 2013-11-11 14:57   ` Thomas Petazzoni
  1 sibling, 0 replies; 4+ messages in thread
From: Thomas Petazzoni @ 2013-11-11 14:57 UTC (permalink / raw)
  To: linux-arm-kernel

Dear Gerlando Falauto,

On Mon, 11 Nov 2013 15:45:31 +0100, Gerlando Falauto wrote:

> On 07/17/2013 10:09 PM, Gerlando Falauto wrote:
> > Hi everyone,
> >
> > newbie's question: are sparse IRQs [going to be] supported on Kirkwood?
> > I thought irq domains were pretty much the same thing...
> > So if I understand correctly, without sparse IRQs I still have to
> > increase NR_IRQS within arch/arm/mach-kirkwood/include/mach/irqs.h in
> > order to support additional PICs.

I believe all the Kirkwood boards that have been converted to the
Device Tree now use a driver in drivers/irqchip/ for IRQ handling, and
therefore use all the modern irqdomain stuff.

I do have a bunch of other patches to convert more Kirkwood boards to
DT (needs more work), and once that's done, we can throw away the
legacy IRQ handling for Kirkwood.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2013-11-11 14:57 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-07-17 20:09 SPARSE_IRQ on Kirkwood Gerlando Falauto
2013-11-11 14:45 ` Gerlando Falauto
2013-11-11 14:51   ` Andrew Lunn
2013-11-11 14:57   ` Thomas Petazzoni

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).