Re: [RFT/PATCH 05/10] cbus: retu: move to threaded IRQ and GENIRQ

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Tue, Jan 04, 2011 at 11:14:00AM -0800, Tony Lindgren wrote:
> I think there's been some patches related to this to get rid
> of NR_IRQS? Might be worth taking a look at those first as it's
> a generic solution.

Yeah, one way would be to use Sparse IRQ numbering scheme and define
different bases for different IRQ chips. We could use for example,
something like:

IRQ	|	Chip
=====================
0-299	|	INTC
300-499	|	TWL4030
500-599	|	MENELAUS
600-799	|	RETU
800-999	|	TAHVO

and so on. But I'm not sure that's good enough (numbers are just from
the top of my head, didn't really check how many IRQs each one have).

The only problem I see is with INTC, what happens if we give it an
interval which ends up not being big enough for next OMAP versions ?

-- 
balbi
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux