[PATCH RFC 7/7] irqchip: [Example] dummy wired interrupt/MSI bridge driver
gabriele.paoloni at huawei.com
Thu Nov 5 01:43:12 PST 2015
> -----Original Message-----
> From: Marc Zyngier [mailto:marc.zyngier at arm.com]
> Sent: Thursday, November 05, 2015 9:36 AM
> To: Gabriele Paoloni; majun (F); Thomas Gleixner; Jiang Liu; Jason
> Cc: linux-arm-kernel at lists.infradead.org; linux-pci at vger.kernel.org;
> linux-kernel at vger.kernel.org
> Subject: Re: [PATCH RFC 7/7] irqchip: [Example] dummy wired
> interrupt/MSI bridge driver
> On 05/11/15 08:25, Gabriele Paoloni wrote:
> > Hi Marc
> >> -----Original Message-----
> >> From: linux-pci-owner at vger.kernel.org [mailto:linux-pci-
> owner at vger.kernel.org]
> >> On Behalf Of Marc Zyngier
> >> Sent: 04 November 2015 09:04
> >> To: majun (F); Thomas Gleixner; Jiang Liu; Jason Cooper
> >> Cc: linux-arm-kernel at lists.infradead.org; linux-pci at vger.kernel.org;
> >> kernel at vger.kernel.org
> >> Subject: Re: [PATCH RFC 7/7] irqchip: [Example] dummy wired
> >> bridge driver
> >> On 04/11/15 08:00, majun (F) wrote:
> >>> I think,for a interrupt controller, msichip driver initialization
> maybe is
> >> too late
> >>> for some devices which connect to this irqchip if we use
> >> module_platform_driver.
> >> That's a consequence of this design. This is why I insisted on the
> >> that this is currently avoided by using deferred probe in drivers,
> > Mmm using te deferred probe would mean to rework all the drivers of
> > potential devices connected to mbi-gen...would that be
> I'm tempted to reply "Not my problem". Or rather, not a problem I'm
> trying to solve right now (or any time soon).
> I'm pretty sure that sprinkling -EPROBE_DEFER on all possible drivers
> will result in a resounding NAK, which is is why I suggested that
> someone with a vested interest dedicates some quality time helping
> who are trying to solve this issue for good.
Yes you're right, makes perfect sense
> >> that it should be solved by having a probe order. Either way, this
> >> not something that we can solve at that level (see the multiple
> >> for this on the various lists).
> > Could you point me to the relevant discussions for this...?
> Google is, as always, your dearest friend. But here you go:
> - LWN has some quality coverage of the KS discussions (assuming you're
> subscriber, otherwise you'll have to wait for another week):
> - There is also Tomeu Vizoso's series, which itself builds upon other
> previous attempts at solving this: https://lwn.net/Articles/658690/
Great, many thanks for pointing them out.
I'll look into these.
> Jazz is not dead. It just smells funny...
More information about the linux-arm-kernel