Re: [Kernel-discuss] RFC - platform device, IRQs and SoC devices

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

 



On Sat, Nov 25, 2006 at 12:51:17PM +0000, Ian Molton wrote:
> Russell King wrote:
> >It's quite possible to have:
> >
> >IRQ	chip
> >0	irqchip_0
> >1	irqchip_0
> >2	irqchip_1
> >3	irqchip_0
> >4	irqchip_0
> >5	irqchip_1
> >6	irqchip_2
> >7	irqchip_2
> >8	irqchip_2
> >9	irqchip_1
> >
> >Where do you start '0' for each irqchip?  How do you split the irq_desc
> >array between the irqchips?
> 
> I see no reason why this couldnt continue to work 'as is' with the new 
> behaviour only applying to irqchips with their own non-NULL irq_desc array.

That creates a multi-class system.  Not nice from the maintainability
aspect.

Nevertheless, please produce patches to demonstrate this idea in detail.

> The other problem is integration with /proc, specifically the irq usage 
> counter.

There's interrupt numbers elsewhere in procfs other than /proc/interrupts -
eg, the /proc/stat "intr" line is just one example.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux