From: Sricharan Ramabadhran <quic_srichara@quicinc.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
<lpieralisi@kernel.org>, <kw@linux.com>, <bhelgaas@google.com>
Cc: <robh@kernel.org>, <andersson@kernel.org>,
<konrad.dybcio@linaro.org>, <linux-pci@vger.kernel.org>,
<linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<steev@kali.org>
Subject: Re: [PATCH 4/8] PCI: qcom: Do not advertise hotplug capability for IPs v2.3.3 and v2.9.0
Date: Fri, 19 May 2023 18:13:43 +0530 [thread overview]
Message-ID: <36fd2413-8a2a-5b7e-c4a0-64e0ac4622ed@quicinc.com> (raw)
In-Reply-To: <20230506073139.8789-5-manivannan.sadhasivam@linaro.org>
On 5/6/2023 1:01 PM, Manivannan Sadhasivam wrote:
> SoCs making use of Qcom PCIe controller IPs v2.3.3 and v2.9.0 do not
> support hotplug functionality. But the hotplug capability bit is set by
> default in the hardware. This causes the kernel PCI core to register
> hotplug service for the controller and send hotplug commands to it. But
> those commands will timeout generating messages as below during boot
> and suspend/resume.
>
> [ 5.782159] pcieport 0001:00:00.0: pciehp: Timeout on hotplug command 0x03c0 (issued 2020 msec ago)
> [ 5.810161] pcieport 0001:00:00.0: pciehp: Timeout on hotplug command 0x03c0 (issued 2048 msec ago)
> [ 7.838162] pcieport 0001:00:00.0: pciehp: Timeout on hotplug command 0x07c0 (issued 2020 msec ago)
> [ 7.870159] pcieport 0001:00:00.0: pciehp: Timeout on hotplug command 0x07c0 (issued 2052 msec ago)
>
> This not only spams the console output but also induces a delay of a
> couple of seconds. To fix this issue, let's not set the HPC bit in
> PCI_EXP_SLTCAP register as a part of the post init sequence to not
> advertise the hotplug capability for the controller.
>
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> ---
> drivers/pci/controller/dwc/pcie-qcom.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/pci/controller/dwc/pcie-qcom.c b/drivers/pci/controller/dwc/pcie-qcom.c
> index 00246726c21d..3d5b3ce9e2da 100644
> --- a/drivers/pci/controller/dwc/pcie-qcom.c
> +++ b/drivers/pci/controller/dwc/pcie-qcom.c
> @@ -140,7 +140,6 @@
> PCI_EXP_SLTCAP_AIP | \
> PCI_EXP_SLTCAP_PIP | \
> PCI_EXP_SLTCAP_HPS | \
> - PCI_EXP_SLTCAP_HPC | \
> PCI_EXP_SLTCAP_EIP | \
> PCIE_CAP_SLOT_POWER_LIMIT_VAL | \
> PCIE_CAP_SLOT_POWER_LIMIT_SCALE)
Tested this in ipq9574 board and the 'timeout' messages go away with
this.
Tested-by: Sricharan Ramabadhran <quic_srichara@quicinc.com>
Regards,
Sricharan
next prev parent reply other threads:[~2023-05-19 12:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-06 7:31 [PATCH 0/8] PCI: qcom: Do not advertise hotplug capability Manivannan Sadhasivam
2023-05-06 7:31 ` [PATCH 1/8] PCI: qcom: Use DWC helpers for modifying the read-only DBI registers Manivannan Sadhasivam
2023-05-06 11:43 ` Dmitry Baryshkov
2023-05-06 12:03 ` Dmitry Baryshkov
2023-05-06 7:31 ` [PATCH 2/8] PCI: qcom: Disable write access to read only registers for IP v2.9.0 Manivannan Sadhasivam
2023-05-06 11:44 ` Dmitry Baryshkov
2023-05-06 12:03 ` Dmitry Baryshkov
2023-05-06 7:31 ` [PATCH 3/8] PCI: qcom: Do not advertise hotplug capability for IPs v2.7.0 and v1.9.0 Manivannan Sadhasivam
2023-05-06 12:01 ` Dmitry Baryshkov
2023-05-06 12:03 ` Dmitry Baryshkov
2023-05-06 7:31 ` [PATCH 4/8] PCI: qcom: Do not advertise hotplug capability for IPs v2.3.3 and v2.9.0 Manivannan Sadhasivam
2023-05-06 12:01 ` Dmitry Baryshkov
2023-05-06 12:07 ` Dmitry Baryshkov
2023-05-19 12:43 ` Sricharan Ramabadhran [this message]
2023-05-06 7:31 ` [PATCH 5/8] PCI: qcom: Do not advertise hotplug capability for IP v2.3.2 Manivannan Sadhasivam
2023-05-06 12:04 ` Dmitry Baryshkov
2023-05-06 14:01 ` Konrad Dybcio
2023-05-08 10:41 ` Manivannan Sadhasivam
2023-05-08 10:25 ` Manivannan Sadhasivam
2023-05-06 7:31 ` [PATCH 6/8] PCI: qcom: Use post init sequence of IP v2.3.2 for v2.4.0 Manivannan Sadhasivam
2023-05-06 12:08 ` Dmitry Baryshkov
2023-05-06 7:31 ` [PATCH 7/8] PCI: qcom: Do not advertise hotplug capability for IP v1.0.0 Manivannan Sadhasivam
2023-05-06 7:31 ` [PATCH 8/8] PCI: qcom: Do not advertise hotplug capability for IP v2.1.0 Manivannan Sadhasivam
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=36fd2413-8a2a-5b7e-c4a0-64e0ac4622ed@quicinc.com \
--to=quic_srichara@quicinc.com \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=konrad.dybcio@linaro.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=manivannan.sadhasivam@linaro.org \
--cc=robh@kernel.org \
--cc=steev@kali.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
all inboxes | Powered by JetHome®