All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: Gabriele Paoloni <gabriele.paoloni@huawei.com>,
	"majun (F)" <majun258@huawei.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Jiang Liu <jiang.liu@linux.intel.com>,
	Jason Cooper <jason@lakedaemon.net>
Cc: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC 7/7] irqchip: [Example] dummy wired interrupt/MSI bridge driver
Date: Thu, 05 Nov 2015 09:35:45 +0000	[thread overview]
Message-ID: <563B22F1.901@arm.com> (raw)
In-Reply-To: <EE11001F9E5DDD47B7634E2F8A612F2E1629D8DD@lhreml503-mbs>

On 05/11/15 08:25, Gabriele Paoloni wrote:
> Hi Marc
> 
>> -----Original Message-----
>> From: linux-pci-owner@vger.kernel.org [mailto:linux-pci-owner@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@lists.infradead.org; linux-pci@vger.kernel.org; linux-
>> kernel@vger.kernel.org
>> Subject: Re: [PATCH RFC 7/7] irqchip: [Example] dummy wired interrupt/MSI
>> 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 fact
>> that this is currently avoided by using deferred probe in drivers, and
> 
> Mmm using te deferred probe would mean to rework all the drivers of the
> potential devices connected to mbi-gen...would that be sustainable/acceptable?

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 those
who are trying to solve this issue for good.

>> that it should be solved by having a probe order. Either way, this is
>> not something that we can solve at that level (see the multiple proposal
>> 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 a
subscriber, otherwise you'll have to wait for another week):
http://lwn.net/Articles/662820/

- There is also Tomeu Vizoso's series, which itself builds upon other
previous attempts at solving this: https://lwn.net/Articles/658690/

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

WARNING: multiple messages have this Message-ID (diff)
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 7/7] irqchip: [Example] dummy wired interrupt/MSI bridge driver
Date: Thu, 05 Nov 2015 09:35:45 +0000	[thread overview]
Message-ID: <563B22F1.901@arm.com> (raw)
In-Reply-To: <EE11001F9E5DDD47B7634E2F8A612F2E1629D8DD@lhreml503-mbs>

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; linux-
>> kernel at vger.kernel.org
>> Subject: Re: [PATCH RFC 7/7] irqchip: [Example] dummy wired interrupt/MSI
>> 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 fact
>> that this is currently avoided by using deferred probe in drivers, and
> 
> Mmm using te deferred probe would mean to rework all the drivers of the
> potential devices connected to mbi-gen...would that be sustainable/acceptable?

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 those
who are trying to solve this issue for good.

>> that it should be solved by having a probe order. Either way, this is
>> not something that we can solve at that level (see the multiple proposal
>> 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 a
subscriber, otherwise you'll have to wait for another week):
http://lwn.net/Articles/662820/

- There is also Tomeu Vizoso's series, which itself builds upon other
previous attempts at solving this: https://lwn.net/Articles/658690/

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2015-11-05  9:35 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15 15:39 [PATCH RFC 0/7] Adding core support for wire-MSI bridges Marc Zyngier
2015-10-15 15:39 ` Marc Zyngier
2015-10-15 15:39 ` [PATCH RFC 1/7] platform-msi: Allow MSIs to be allocated in chunks Marc Zyngier
2015-10-15 15:39   ` Marc Zyngier
2015-10-15 15:39 ` [PATCH RFC 2/7] platform-msi: Factor out allocation/free of private data Marc Zyngier
2015-10-15 15:39   ` Marc Zyngier
2015-10-16  5:46   ` Jiang Liu
2015-10-16  5:46     ` Jiang Liu
2015-10-16  8:50     ` Marc Zyngier
2015-10-16  8:50       ` Marc Zyngier
2015-10-15 15:39 ` [PATCH RFC 3/7] irqdomain: Make irq_domain_alloc_irqs_recursive available Marc Zyngier
2015-10-15 15:39   ` Marc Zyngier
2015-10-15 15:39 ` [PATCH RFC 4/7] genirq/msi: Make the .prepare callback reusable Marc Zyngier
2015-10-15 15:39   ` Marc Zyngier
2015-10-15 17:24   ` Gabriele Paoloni
2015-10-15 17:24     ` Gabriele Paoloni
2015-10-15 17:24     ` Gabriele Paoloni
2015-10-15 17:39     ` Marc Zyngier
2015-10-15 17:39       ` Marc Zyngier
2015-10-16 13:07       ` Gabriele Paoloni
2015-10-16 13:07         ` Gabriele Paoloni
2015-10-16 13:07         ` Gabriele Paoloni
2015-10-16  5:45   ` Jiang Liu
2015-10-16  5:45     ` Jiang Liu
2015-10-16  8:48     ` Marc Zyngier
2015-10-16  8:48       ` Marc Zyngier
2015-10-15 15:39 ` [PATCH RFC 5/7] genirq/msi: Add msi_domain_populate_irqs Marc Zyngier
2015-10-15 15:39   ` Marc Zyngier
2015-10-15 15:39 ` [PATCH RFC 6/7] platform-msi: Allow creation of a MSI-based stacked irq domain Marc Zyngier
2015-10-15 15:39   ` Marc Zyngier
2015-10-15 15:39 ` [PATCH RFC 7/7] irqchip: [Example] dummy wired interrupt/MSI bridge driver Marc Zyngier
2015-10-15 15:39   ` Marc Zyngier
2015-11-04  8:00   ` majun (F)
2015-11-04  8:00     ` majun (F)
2015-11-04  9:03     ` Marc Zyngier
2015-11-04  9:03       ` Marc Zyngier
2015-11-05  8:25       ` Gabriele Paoloni
2015-11-05  8:25         ` Gabriele Paoloni
2015-11-05  8:25         ` Gabriele Paoloni
2015-11-05  9:35         ` Marc Zyngier [this message]
2015-11-05  9:35           ` Marc Zyngier
2015-11-05  9:43           ` Gabriele Paoloni
2015-11-05  9:43             ` Gabriele Paoloni
2015-11-05  9:43             ` Gabriele Paoloni
2015-10-15 15:46 ` [PATCH RFC 0/7] Adding core support for wire-MSI bridges Arnd Bergmann
2015-10-15 15:46   ` Arnd Bergmann
2015-10-15 16:01   ` Marc Zyngier
2015-10-15 16:01     ` Marc Zyngier
2015-10-15 19:16     ` Arnd Bergmann
2015-10-15 19:16       ` Arnd Bergmann
2015-10-16  8:03       ` Marc Zyngier
2015-10-16  8:03         ` Marc Zyngier
2015-10-16  8:45         ` Arnd Bergmann
2015-10-16  8:45           ` Arnd Bergmann
2015-10-16  1:55 ` Jiang Liu
2015-10-16  1:55   ` Jiang Liu
2015-10-16  8:48   ` Marc Zyngier
2015-10-16  8:48     ` Marc Zyngier
2015-11-04 13:34     ` Thomas Gleixner
2015-11-04 13:34       ` Thomas Gleixner
2015-11-05 12:22       ` Marc Zyngier
2015-11-05 12:22         ` Marc Zyngier
2015-11-05 12:25         ` Thomas Gleixner
2015-11-05 12:25           ` Thomas Gleixner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=563B22F1.901@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=gabriele.paoloni@huawei.com \
    --cc=jason@lakedaemon.net \
    --cc=jiang.liu@linux.intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=majun258@huawei.com \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.