From: Bjorn Helgaas <helgaas@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.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: Mon, 31 Jul 2023 11:57:38 -0500 [thread overview]
Message-ID: <20230731165738.GA14380@bhelgaas> (raw)
In-Reply-To: <20230726152931.18134-1-manivannan.sadhasivam@linaro.org>
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?
> 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-07-31 16:58 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 [this message]
2023-08-02 5:49 ` Manivannan Sadhasivam
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=20230731165738.GA14380@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--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=manivannan.sadhasivam@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.