From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: lpieralisi@kernel.org, kw@linux.com, robh@kernel.org,
bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: qcom-ep: Treat unknown irq events as an error
Date: Wed, 2 Aug 2023 11:19:55 +0530 [thread overview]
Message-ID: <20230802054955.GG2370@thinkpad> (raw)
In-Reply-To: <20230731165738.GA14380@bhelgaas>
On Mon, Jul 31, 2023 at 11:57:38AM -0500, Bjorn Helgaas wrote:
> On Wed, Jul 26, 2023 at 08:59:31PM +0530, Manivannan Sadhasivam wrote:
> > Sometimes, the Qcom PCIe EP controller can receive some interrupts that are
> > not known to the driver like safety interrupts in newer SoCs. In those
> > cases, if the driver doesn't clear the interrupts, then it will end up in
> > interrupt storm. But the users won't have any idea about it due to the log
> > being treated as a debug message.
> >
> > So let's treat the unknown event log as an error, so that it at least makes
> > the user aware, thereby getting fixed eventually.
>
> Would it be practical to log the error message, then clear the
> interrupt to avoid the interrupt storm?
Just to make it clear that we are already clearing the IRQs in
PARF_INT_ALL_CLEAR. But the issue is, on newer platforms there are a couple more
of these registers that the driver should mask and clear.
Qcom faced an interrupt storm issue while bringing up PCIe EP on a new
platform. On that platform, several interrupts were added for some specific
usecases. Since we do not mask/clear those interrupts, it resulted in an
interrupt storm. Moreover, the absence of error message made it difficult to
debug the issue as there were no logs from the driver (they didn't enable DEBUG
unfortunately during bringup as I thought one would do).
So to catch these kind of issues in the future, I just want to promote the log
to dev_err().
- Mani
>
> > Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> > ---
> > drivers/pci/controller/dwc/pcie-qcom-ep.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/pci/controller/dwc/pcie-qcom-ep.c b/drivers/pci/controller/dwc/pcie-qcom-ep.c
> > index 267e1247d548..802dedcc929c 100644
> > --- a/drivers/pci/controller/dwc/pcie-qcom-ep.c
> > +++ b/drivers/pci/controller/dwc/pcie-qcom-ep.c
> > @@ -593,7 +593,7 @@ static irqreturn_t qcom_pcie_ep_global_irq_thread(int irq, void *data)
> > dw_pcie_ep_linkup(&pci->ep);
> > pcie_ep->link_status = QCOM_PCIE_EP_LINK_UP;
> > } else {
> > - dev_dbg(dev, "Received unknown event: %d\n", status);
> > + dev_err(dev, "Received unknown event: %d\n", status);
> > }
> >
> > return IRQ_HANDLED;
> > --
> > 2.25.1
> >
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2023-08-02 5:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 15:29 [PATCH] PCI: qcom-ep: Treat unknown irq events as an error Manivannan Sadhasivam
2023-07-31 16:57 ` Bjorn Helgaas
2023-08-02 5:49 ` Manivannan Sadhasivam [this message]
2023-08-25 16:36 ` Krzysztof Wilczyński
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=20230802054955.GG2370@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).