From: tn@semihalf.com (Tomasz Nowicki)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 2/6] acpi: pci: Setup MSI domain for ACPI based pci devices
Date: Sun, 6 Dec 2015 19:03:18 +0100 [thread overview]
Message-ID: <56647866.8080802@semihalf.com> (raw)
In-Reply-To: <20151122113553.4fd81185@arm.com>
Hi Marc,
On 11/22/2015 12:35 PM, Marc Zyngier wrote:
> On Sat, 21 Nov 2015 15:18:45 -0600
> Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com> wrote:
>
>> Hi Marc,
>>
>> On 11/19/15 06:08, Marc Zyngier wrote:
>>> On Wed, 21 Oct 2015 11:47:25 -0700
>>> Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com> wrote:
>>>
>>> Hi Suravee,
>>>
>>> Sorry it took so long to get to this series. Comments below.
>> No worry.
>>
>>>> This patch introduces pci_host_bridge_acpi_msi_domain(), which returns
>>>> the MSI domain of the specified PCI host bridge with DOMAIN_BUS_PCI_MSI
>>>> bus token. Then, it is assigned to pci device.
>>>>
>>>> Signed-off-by: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
>>>> ---
>>>> drivers/pci/pci-acpi.c | 13 +++++++++++++
>>>> drivers/pci/probe.c | 2 ++
>>>> include/linux/pci.h | 7 +++++++
>>>> 3 files changed, 22 insertions(+)
>>>>
>>>> diff --git a/drivers/pci/pci-acpi.c b/drivers/pci/pci-acpi.c
>>>> index a32ba75..0e21ef4 100644
>>>> --- a/drivers/pci/pci-acpi.c
>>>> +++ b/drivers/pci/pci-acpi.c
>>>> @@ -9,7 +9,9 @@
>>>>
>>>> #include <linux/delay.h>
>>>> #include <linux/init.h>
>>>> +#include <linux/irqdomain.h>
>>>> #include <linux/pci.h>
>>>> +#include <linux/msi.h>
>>>> #include <linux/pci_hotplug.h>
>>>> #include <linux/module.h>
>>>> #include <linux/pci-aspm.h>
>>>> @@ -689,6 +691,17 @@ static struct acpi_bus_type acpi_pci_bus = {
>>>> .cleanup = pci_acpi_cleanup,
>>>> };
>>>>
>>>> +struct irq_domain *pci_host_bridge_acpi_msi_domain(struct pci_bus *bus)
>>>> +{
>>>> + struct irq_domain *dom = NULL;
>>>> + struct fwnode_handle *fwnode = pci_msi_get_fwnode(&bus->dev);
>>>> +
>>>> + if (fwnode)
>>>> + dom = irq_find_matching_fwnode(fwnode,
>>>> + DOMAIN_BUS_PCI_MSI);
>>>> + return dom;
>>>> +}
>>>> +
>>> Given this, I really question the need for what you define in patch #1
>>> to be standalone. It is only used by ACPI (DT has its own private
>>> helpers), and it is so far unlikely that it will be of any use for
>>> other firmware interfaces.
>>>
>>> My suggestion is to get rid of pci_msi_get_fwnode() and move the
>>> registration helper into this file. That'd be much simpler.
>>>
>>> Thanks,
>>>
>>> M.
>>>
>> Ok, I'll take care of this. I assume the rest of the patches looks ok.
> I still need to finish going through it (I have minor comments so far
> on some of the other patches), but I want to get the core ACPI stuff in
> shape before doing anything else.
I am trying to do similar thing for GICv3 & ITS, can you please have a look:
http://lkml.iu.edu/hypermail/linux/kernel/1510.1/06139.html
Can you please explain what ACPI core changes do you mean?
Regards,
Tomasz
next prev parent reply other threads:[~2015-12-06 18:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 18:47 [PATCH V3 0/6] gicv2m: acpi: Add ACPI support for GICv2m MSI Suravee Suthikulpanit
2015-10-21 18:47 ` [PATCH V3 1/6] pci: msi: Add support to query MSI domain for pci device Suravee Suthikulpanit
2015-10-21 18:47 ` [PATCH V3 2/6] acpi: pci: Setup MSI domain for ACPI based pci devices Suravee Suthikulpanit
2015-11-19 12:08 ` Marc Zyngier
2015-11-21 21:18 ` Suravee Suthikulpanit
2015-11-22 11:35 ` Marc Zyngier
2015-12-06 18:03 ` Tomasz Nowicki [this message]
2015-12-07 8:55 ` Marc Zyngier
2015-10-21 18:47 ` [PATCH V3 3/6] irqdomain: introduce is_fwnode_irqchip helper Suravee Suthikulpanit
2015-10-21 18:47 ` [PATCH V3 4/6] irqdomain: Introduce irq_domain_get_irqchip_fwnode_name helper function Suravee Suthikulpanit
2015-10-21 18:47 ` [PATCH V3 5/6] gicv2m: Refactor to prepare for ACPI support Suravee Suthikulpanit
2015-10-21 18:47 ` [PATCH V3 6/6] gicv2m: acpi: Introducing GICv2m " Suravee Suthikulpanit
2015-10-29 21:25 ` [PATCH V3 0/6] gicv2m: acpi: Add ACPI support for GICv2m MSI Duc Dang
2015-10-30 14:03 ` Suravee Suthikulpanit
2015-10-30 16:53 ` Duc Dang
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=56647866.8080802@semihalf.com \
--to=tn@semihalf.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).