On Mon, Jan 28, 2019 at 03:01:35PM +0100, Thomas Bogendoerfer wrote: > On Mon, 28 Jan 2019 05:33:17 -0800 > Christoph Hellwig <[email protected]> wrote: > > > Shouldnt this just use chained irqchip drivers instead? > > you mean using irq_set_chained_handler() ? If yes, this IMHO doesn't look > usefull > because it's used for adding a secondary interrupt controller. But what I need > is telling bridge ASIC to direct the xtalk IRQ packet to a specific > HUB/HEART/BEDROCK > from the HUB/HEART/BEDROCK specific code. And want to avoid dragging in > bridge details > to that specific code.
Yes, but don't we have nested interrupt controllers here? Even if they don't really do much in the fast path the setup does look chained to me. Then again I'm not really an expert in the irq handling code nor in this hardware, so maybe Thomas or Marc might have a better idea.
