From: "Pali Rohár" <pali@kernel.org>
To: Stefan Roese <sr@denx.de>
Cc: linux-pci@vger.kernel.org,
Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com>,
Bjorn Helgaas <helgaas@kernel.org>,
Michal Simek <michal.simek@xilinx.com>
Subject: Re: [PATCH v3 1/2] PCI/portdrv: Add option to setup IRQs for platform-specific Service Errors
Date: Thu, 13 Jan 2022 12:14:50 +0100 [thread overview]
Message-ID: <20220113111450.pgacviso7sn627ln@pali> (raw)
In-Reply-To: <20220113104939.1635398-2-sr@denx.de>
On Thursday 13 January 2022 11:49:38 Stefan Roese wrote:
> From: Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com>
>
> As per section 6.2.4.1.2, 6.2.6 in PCIe r4.0 (and later versions),
> platform-specific System Errors like AER can be delivered via platform-
> specific interrupt lines.
>
> This patch adds the init_platform_service_irqs() hook to struct
> pci_host_bridge, making it possible that platforms may implement this
> function to hook IRQs for these platform-specific System Errors, like
> AER.
>
> If these platform-specific service IRQs have been successfully
> installed via pcie_init_platform_service_irqs(),
> pcie_init_service_irqs() is skipped.
>
> Signed-off-by: Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com>
> Signed-off-by: Stefan Roese <sr@denx.de>
> Cc: Bjorn Helgaas <helgaas@kernel.org>
> Cc: Pali Rohár <pali@kernel.org>
> Cc: Michal Simek <michal.simek@xilinx.com>
> ---
> drivers/pci/pcie/portdrv_core.c | 43 ++++++++++++++++++++++++++++++++-
> include/linux/pci.h | 2 ++
> 2 files changed, 44 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/pci/pcie/portdrv_core.c b/drivers/pci/pcie/portdrv_core.c
> index bda630889f95..4dab74ff4368 100644
> --- a/drivers/pci/pcie/portdrv_core.c
> +++ b/drivers/pci/pcie/portdrv_core.c
> @@ -190,6 +190,31 @@ static int pcie_init_service_irqs(struct pci_dev *dev, int *irqs, int mask)
> return 0;
> }
>
> +/**
> + * pcie_init_platform_service_irqs - initialize platform service irqs for
> + * platform-specific System Errors
> + * @dev: PCI Express port to handle
> + * @irqs: Array of irqs to populate
> + * @mask: Bitmask of capabilities
> + *
> + * Return value: true/false for platforms service irqs installed or not
> + */
> +static bool pcie_init_platform_service_irqs(struct pci_dev *dev,
> + int *irqs, int mask)
> +{
> + struct pci_host_bridge *bridge;
> +
> + if (pci_pcie_type(dev) == PCI_EXP_TYPE_ROOT_PORT) {
I think that this check is not needed as it is done before calling
pcie_init_platform_service_irqs() function.
> + bridge = pci_find_host_bridge(dev->bus);
> + if (bridge && bridge->init_platform_service_irqs) {
> + bridge->init_platform_service_irqs(dev, irqs, mask);
> + return true;
Suggestion: What about "return bridge->init_platform_service_irqs(...);" ?
This could allow callback function to fail...
> + }
> + }
> +
> + return false;
> +}
> +
> /**
> * get_port_device_capability - discover capabilities of a PCI Express port
> * @dev: PCI Express port to examine
> @@ -318,6 +343,7 @@ int pcie_port_device_register(struct pci_dev *dev)
> int irqs[PCIE_PORT_DEVICE_MAXSERVICES] = {
> [0 ... PCIE_PORT_DEVICE_MAXSERVICES-1] = -1
> };
> + bool plat_irqs;
>
> /* Enable PCI Express port device */
> status = pci_enable_device(dev);
> @@ -342,7 +368,22 @@ int pcie_port_device_register(struct pci_dev *dev)
> irq_services |= PCIE_PORT_SERVICE_DPC;
> irq_services &= capabilities;
>
> - if (irq_services) {
> + /*
> + * Some platforms have dedicated interrupts from root complex to
> + * interrupt controller for PCIe platform-specific System Errors
> + * like AER/PME etc., check if the platform registered with any such
> + * IRQ.
> + */
> + if (pci_pcie_type(dev) == PCI_EXP_TYPE_ROOT_PORT) {
> + plat_irqs = pcie_init_platform_service_irqs(dev, irqs,
> + capabilities);
> + }
> +
> + /*
> + * Only install service irqs, when the platform-specific hook was
> + * unsuccessful
> + */
> + if (irq_services && !plat_irqs) {
> /*
> * Initialize service IRQs. Don't use service devices that
> * require interrupts if there is no way to generate them.
> diff --git a/include/linux/pci.h b/include/linux/pci.h
> index 18a75c8e615c..a0bcc8062b91 100644
> --- a/include/linux/pci.h
> +++ b/include/linux/pci.h
> @@ -554,6 +554,8 @@ struct pci_host_bridge {
> u8 (*swizzle_irq)(struct pci_dev *, u8 *); /* Platform IRQ swizzler */
> int (*map_irq)(const struct pci_dev *, u8, u8);
> void (*release_fn)(struct pci_host_bridge *);
> + void (*init_platform_service_irqs)(struct pci_dev *dev, int *irqs,
> + int plat_mask);
> void *release_data;
> unsigned int ignore_reset_delay:1; /* For entire hierarchy */
> unsigned int no_ext_tags:1; /* No Extended Tags */
> --
> 2.34.1
>
next prev parent reply other threads:[~2022-01-13 11:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 10:49 [PATCH v3 0/2] Add support to register platform service IRQ Stefan Roese
2022-01-13 10:49 ` [PATCH v3 1/2] PCI/portdrv: Add option to setup IRQs for platform-specific Service Errors Stefan Roese
2022-01-13 11:14 ` Pali Rohár [this message]
2022-01-13 11:45 ` Stefan Roese
2022-01-13 10:49 ` [PATCH v3 2/2] PCI: xilinx-nwl: Add method to init_platform_service_irqs hook Stefan Roese
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=20220113111450.pgacviso7sn627ln@pali \
--to=pali@kernel.org \
--cc=bharat.kumar.gogada@xilinx.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=sr@denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox