Thread (1 message) read the whole thread 1 message, 1 author, 2012-07-05

Re: [PATCH v2 01/12] ARM: Orion: DT support for IRQ and GPIO Controllers

From: Thomas Petazzoni <hidden>
Date: 2012-07-05 13:28:40
Also in: linux-arm-kernel, linux-devicetree, linux-spi

Le Thu, 5 Jul 2012 15:15:22 +0200,
Andrew Lunn [off-list ref] a écrit :
quoted
quoted
The biggest problem i had, is the interaction between generic chip
interrupts and irqdomain. There has been work to integrate the two,
but its stalled. Either the work needs restarting and completing, or
you need to throw away the use of generic interrupt so that you can
use irqdomain linear. IMHO, throwing away generic interrupt is the
wrong way.
Can you expand on why you think it would be wrong to throw away the
usage of irq_chip_generic, compared to implementing directly an
irq_chip?
Basically you are asking, why should i use the framework when i can do
it by hand.
Agreed :)
What are the advantages if ignoring the framework and doing it by
hand?
Many GPIO drivers directly use irq_chip (though it's true some of them
use irq_chip_generic), and the irq_chip_generic framework doesn't have
really proper support for the other new irqdomain framework, so I was
wondering what the best solution was.

I found the proposal from Rob Herring to improve that situation, but
apparently the conclusion from Grant Likely was "Let's discuss this at
the next Connect". That patch set was posted in January, so two Linaro
Connects happened since them, I don't know if progress has been made
here.

I guess I'll just stick to irq_chip_generic + irqdomain_legacy for now.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help