Re: [RFC PATCH] irq: handle private interrupt registration

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Felipe Balbi
Date: Tuesday, June 1, 2010 - 10:41 pm

Hi,

On Wed, Jun 02, 2010 at 01:14:32AM +0200, ext Thomas Gleixner wrote:

FWIW, I think (1) is a better approach as the problem will vanish 
altogether and to me it sounds like the simpler approach as well. Archs 
which have more than one IRQ chip (like OMAP with the twl4030 family) 
will already use sequencial numbering anyway, so using the same approach 
for N cpus, to me, sounds like a good deal.

While at that, a question from my side: do we have a generic way of 
fetching the last IRQ number so we can easily use that to calculate the 
physical number of the IRQ line on the chip ?

On OMAP, we have been passing that number down to twl4030 via 
platform_data, but it would be better to ask genirq to tell us which was 
the last irq number "claimed".

-- 
balbi

DefectiveByDesign.org
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [RFC PATCH] irq: handle private interrupt registration, Thomas Gleixner, (Tue Jun 1, 4:14 pm)
Re: [RFC PATCH] irq: handle private interrupt registration, Felipe Balbi, (Tue Jun 1, 10:41 pm)
Re: [RFC PATCH] irq: handle private interrupt registration, Thomas Gleixner, (Wed Jun 2, 6:06 am)