Message-ID: <1260333801.26900.37.camel@kenjo-laptop>
Date:	Wed, 09 Dec 2009 05:43:21 +0100
From:	Kenneth Johansson <kenneth@...thpole.se>
To:	David Brownell <david-b@...bell.net>
Cc:	linux-kernel@...r.kernel.org, alek.du@...el.com, tglx@...utronix.de
Subject: Re: gpio gpio_to_irq

On Tue, 2009-12-08 at 14:22 -0800, David Brownell wrote:
> On Monday 07 December 2009, Kenneth Johansson wrote:
> > But doing so on a shared pci 
> > interrupt do not look like a good idea. 
> > 
> > Under what circumstance is set_irq_chained_handler allowed ? 
> 
> That's an IRQ question not a GPIO question.  I think the answer
> to that question has likely been evolving over time... and that
> you may be right about doing this over PCI.

yes the irq thing is the only part of the gpio abstraction I have issue
with so this is basically all about that part. It all originates from
the gpio_to_irq function and what that one is supposed to return. 

> > The next thing is that the drivers then registers a "fake" interrupt
> > chip to make it possible for the gpio client to call request_irq with
> > the irq number returned from gpio_to_irq().
> 
> Not that I've ever seen.  It's a real irq_chip.

I had it in quotes as I have a mental block on thinking of it as an
interrupt controller but you are right it can be view as a simple
controller. 

> > While using this interface is neat it do require that the gpio driver
> > somehow can just take over a few irq numbers from the system. 
> > 
> > How is this supposed to be done??
> 
> Last I looked, IRQ numbering was a global system-wide policy.
> 
> So plug'n'play of IRQ controllers was ... awkward, along with
> dynamic assignment of IRQ numbers.  True for all PCI-based IRQ
> controllers.  Southbridge IRQs are often wrapped up in ACPI,
> so those issues don't surface in most PCs.
> 
> Again, not a GPIO question, but an IRQ question.  (Or maybe an
> x86 arch question.)

Yes I has hoped that the "overlord of low level hacking on
x86" (Gleixner) would bite but no such luck.

> 
> > the langwell driver reads a number 
> > located at BAR1 and simply use that as the first irq number, hu?
> > 
> > others start to allocate from the top and so on. what is the correct way
> > to do this on a x86 with a gpio device on the pci bus ?? 
> 
> Embedded platforms have typically done things like pre-allocate
> a bunch of extra IRQ numbers, and then arrange to have each new
> IRQ controller land in a board-assigned slot.  It can waste RAM,
> but is mostly painless.
> 
> That's fine so long as you have a sane level of control over
> system bootup, where board-specific logic can for example know
> which external chips (and thus irq_chip controllers) exist.
> (And maybe even arrange via Kconfig to alloc extra IRQ numbers
> only as needed.)
> 
> When you don't have such a notion of "board" -- maybe punting
> everything to ACPI or some other "hide the hardware from the
> OS" abstraction -- I'm not clear on a good solution.

I wish the genirq had an allocation strategy for the irq numbers Then
that could basically be used by any gpio driver on any arch. basically
irq_get_free() would solve it. 

Well I have to investigate more how msi interrupts is done as they also
need to allocate a new irq number whenever a pci device turns it on.

I just hoped I had missed something that would make this problem go
away. 




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