From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 04/19] PCI/MSI: Add hooks to populate the msi_domain field
Date: Wed, 22 Jul 2015 18:42:11 +0100 [thread overview]
Message-ID: <55AFD5F3.3000705@arm.com> (raw)
In-Reply-To: <20150722165318.GA27197@google.com>
On 22/07/15 17:53, Bjorn Helgaas wrote:
> On Wed, Jul 22, 2015 at 03:54:14PM +0100, Marc Zyngier wrote:
>> On 22/07/15 15:48, Bjorn Helgaas wrote:
>>> On Wed, Jul 22, 2015 at 9:42 AM, Marc Zyngier <marc.zyngier@arm.com> wrote:
>>>> Hi Bjorn,
>>>>
>>>> On 21/07/15 22:26, Bjorn Helgaas wrote:
>>>>> On Wed, Jul 15, 2015 at 01:16:38PM +0100, Marc Zyngier wrote:
>>>>>> In order to be able to populate the device msi_domain field,
>>>>>> add the necesary hooks to propagate the host bridge msi_domain
>>>>>> across secondary busses to devices.
>>>>>>
>>>>>> So far, nobody populates the initial msi_domain.
>>>>>>
>>>>>> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
>>>>>> ---
>>>>>> drivers/pci/probe.c | 30 ++++++++++++++++++++++++++++++
>>>>>> include/linux/pci.h | 1 +
>>>>>> 2 files changed, 31 insertions(+)
>>>>>>
>>>>>> diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
>>>>>> index cefd636..376f6fa 100644
>>>>>> --- a/drivers/pci/probe.c
>>>>>> +++ b/drivers/pci/probe.c
>>>>>> @@ -661,6 +661,20 @@ static void pci_set_bus_speed(struct pci_bus *bus)
>>>>>> }
>>>>>> }
>>>>>>
>>>>>> +void __weak pcibios_set_host_bridge_msi_domain(struct pci_bus *bus)
>>>>>> +{
>>>>>> +}
>>>>>
>>>>> I don't think there's anything in this series that requires this to be a
>>>>> weak function, is there? This is the only definition I see.
>>>>
>>>> It looks like all the pcibios_* functions so far have a weak attribute,
>>>> and I've added it as a matter of consistency.
>>>
>>> We've used pcibios_* names where we might need an arch-specific
>>> implementation. I'm not sure that's the case here -- do you envision
>>> an implementation under arch/* someday? If not, maybe it should just
>>> be a pci_* function instead of pcibios_*.
>>
>> I could definitely see non-OF driven architectures wanting to override this.
>>
>> Or maybe we should turn it the other way around and make it call the
>> various firmware interfaces (OF, ACPI...) until one of them succeeds. In
>> which case your suggestion of making it a pci_* function makes a lot of
>> sense.
>
> Here's my advice, FWIW:
>
> - remove __weak
>
> - rename pcibios_set_host_bridge_msi_domain() to
> pci_host_bridge_msi_domain() and have it return a struct irq_domain *
>
> - pci_host_bridge_msi_domain() can call whatever firmware- or
> arch-specific code you need to look up the irq_domain
>
> - move the dev_set_msi_domain() call from pci_set_phb_of_msi_domain() to
> pci_set_bus_msi_domain()
>
Yes, seems to make sense. I end-up with something that looks much more
readable (pci_set_bus_msi_domain looks fairly neat now).
I'll post a new version shortly.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2015-07-22 17:42 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 12:16 [PATCH v4 00/19] Per-device MSI domain & platform MSI Marc Zyngier
2015-07-15 12:16 ` [PATCH v4 01/19] genirq: irqdomain: Allow irq domain aliasing Marc Zyngier
2015-07-15 12:16 ` [PATCH v4 02/19] PCI: MSI: Register irq domain with specific token Marc Zyngier
2015-07-15 12:16 ` [PATCH v4 03/19] device core: Introduce per-device MSI domain pointer Marc Zyngier
2015-07-15 12:16 ` [PATCH v4 04/19] PCI/MSI: Add hooks to populate the msi_domain field Marc Zyngier
2015-07-21 21:19 ` Bjorn Helgaas
2015-07-21 21:26 ` Bjorn Helgaas
2015-07-22 14:42 ` Marc Zyngier
2015-07-22 14:48 ` Bjorn Helgaas
2015-07-22 14:54 ` Marc Zyngier
2015-07-22 16:53 ` Bjorn Helgaas
2015-07-22 17:42 ` Marc Zyngier [this message]
2015-07-15 12:16 ` [PATCH v4 05/19] PCI/MSI: of: Add support for OF-provided msi_domain Marc Zyngier
2015-07-21 21:30 ` Bjorn Helgaas
2015-07-15 12:16 ` [PATCH v4 06/19] PCI/MSI: of: Allow msi_domain lookup using the host bridge node Marc Zyngier
2015-07-15 12:16 ` [PATCH v4 07/19] PCI/MSI: Let pci_msi_get_domain use struct device's msi_domain Marc Zyngier
2015-07-21 21:17 ` Bjorn Helgaas
2015-07-22 15:19 ` Marc Zyngier
2015-07-15 12:16 ` [PATCH v4 08/19] platform: of: Assign MSI domain to platform device Marc Zyngier
2015-07-15 12:16 ` [PATCH v4 09/19] drivers: base: Add MSI domain support for non-PCI devices Marc Zyngier
2015-07-20 2:33 ` majun (F)
2015-07-20 7:54 ` Marc Zyngier
2015-07-15 12:16 ` [PATCH v4 10/19] genirq: Add DOMAIN_BUS_NEXUS irqdomain property Marc Zyngier
2015-07-15 12:16 ` [PATCH v4 11/19] irqchip: gicv3-its: Split PCI/MSI code from the core ITS driver Marc Zyngier
2015-07-15 12:16 ` [PATCH v4 12/19] irqchip: gicv3-its: Register irq domain with NEXUS token Marc Zyngier
2015-07-15 12:16 ` [PATCH v4 13/19] irqchip: gicv3-its: Get rid of struct msi_controller Marc Zyngier
2015-07-15 12:16 ` [PATCH v4 14/19] irqchip: gicv3-its: Make the PCI/MSI code standalone Marc Zyngier
2015-07-15 12:16 ` [PATCH v4 15/19] irqchip: gicv3-its: Add platform MSI support Marc Zyngier
2015-07-15 12:16 ` [PATCH v4 16/19] irqchip: GICv2m: Get rid of struct msi_controller Marc Zyngier
2015-07-15 12:16 ` [PATCH v4 17/19] irqchip: GICv2m: Add platform MSI support Marc Zyngier
2015-07-15 12:16 ` [PATCH v4 18/19] PCI/MSI: pci-xgene-msi: Get rid of struct msi_controller Marc Zyngier
2015-07-15 12:16 ` [PATCH v4 19/19] PCI/MSI: Drop domain field from msi_controller Marc Zyngier
2015-07-21 21:37 ` Bjorn Helgaas
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=55AFD5F3.3000705@arm.com \
--to=marc.zyngier@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).