From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Dilip Kota <eswara.kota@linux.intel.com>
Cc: robh@kernel.org, linux-pci@vger.kernel.org, bhelgaas@google.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: dwc/intel-gw: Fix enabling the legacy PCI interrupt lines
Date: Tue, 23 Mar 2021 11:35:59 +0000 [thread overview]
Message-ID: <20210323113559.GE29286@e121166-lin.cambridge.arm.com> (raw)
In-Reply-To: <20210106135540.48420-1-martin.blumenstingl@googlemail.com>
On Wed, Jan 06, 2021 at 02:55:40PM +0100, Martin Blumenstingl wrote:
> The legacy PCI interrupt lines need to be enabled using PCIE_APP_IRNEN
> bits 13 (INTA), 14 (INTB), 15 (INTC) and 16 (INTD). The old code however
> was taking (for example) "13" as raw value instead of taking BIT(13).
> Define the legacy PCI interrupt bits using the BIT() macro and then use
> these in PCIE_APP_IRN_INT.
>
> Fixes: ed22aaaede44 ("PCI: dwc: intel: PCIe RC controller driver")
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> ---
> drivers/pci/controller/dwc/pcie-intel-gw.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/pci/controller/dwc/pcie-intel-gw.c b/drivers/pci/controller/dwc/pcie-intel-gw.c
> index 0cedd1f95f37..ae96bfbb6c83 100644
> --- a/drivers/pci/controller/dwc/pcie-intel-gw.c
> +++ b/drivers/pci/controller/dwc/pcie-intel-gw.c
> @@ -39,6 +39,10 @@
> #define PCIE_APP_IRN_PM_TO_ACK BIT(9)
> #define PCIE_APP_IRN_LINK_AUTO_BW_STAT BIT(11)
> #define PCIE_APP_IRN_BW_MGT BIT(12)
> +#define PCIE_APP_IRN_INTA BIT(13)
> +#define PCIE_APP_IRN_INTB BIT(14)
> +#define PCIE_APP_IRN_INTC BIT(15)
> +#define PCIE_APP_IRN_INTD BIT(16)
> #define PCIE_APP_IRN_MSG_LTR BIT(18)
> #define PCIE_APP_IRN_SYS_ERR_RC BIT(29)
> #define PCIE_APP_INTX_OFST 12
> @@ -48,10 +52,8 @@
> PCIE_APP_IRN_RX_VDM_MSG | PCIE_APP_IRN_SYS_ERR_RC | \
> PCIE_APP_IRN_PM_TO_ACK | PCIE_APP_IRN_MSG_LTR | \
> PCIE_APP_IRN_BW_MGT | PCIE_APP_IRN_LINK_AUTO_BW_STAT | \
> - (PCIE_APP_INTX_OFST + PCI_INTERRUPT_INTA) | \
> - (PCIE_APP_INTX_OFST + PCI_INTERRUPT_INTB) | \
> - (PCIE_APP_INTX_OFST + PCI_INTERRUPT_INTC) | \
> - (PCIE_APP_INTX_OFST + PCI_INTERRUPT_INTD))
> + PCIE_APP_IRN_INTA | PCIE_APP_IRN_INTB | \
> + PCIE_APP_IRN_INTC | PCIE_APP_IRN_INTD)
>
> #define BUS_IATU_OFFSET SZ_256M
> #define RESET_INTERVAL_MS 100
This looks like a significant bug - which in turn raises the question
on how well this driver has been tested.
Dilip, can you review and ACK asap please ?
Thanks,
Lorenzo
next prev parent reply other threads:[~2021-03-23 11:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 13:55 [PATCH] PCI: dwc/intel-gw: Fix enabling the legacy PCI interrupt lines Martin Blumenstingl
2021-03-23 11:35 ` Lorenzo Pieralisi [this message]
2021-04-08 20:39 ` Martin Blumenstingl
2021-04-09 10:17 ` Rahul Tanwar
2021-04-09 10:29 ` Lorenzo Pieralisi
2021-06-23 13:54 ` Lorenzo Pieralisi
2021-06-23 14:10 ` Lorenzo Pieralisi
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=20210323113559.GE29286@e121166-lin.cambridge.arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=bhelgaas@google.com \
--cc=eswara.kota@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=robh@kernel.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