From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: kw@linux.com, bhelgaas@google.com, 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,
quic_srichara@quicinc.com, dmitry.baryshkov@linaro.org
Subject: Re: [PATCH v2 0/8] PCI: qcom: Do not advertise hotplug capability
Date: Mon, 22 May 2023 11:01:17 +0200 [thread overview]
Message-ID: <ZGsvXbiWK383zoaQ@lpieralisi> (raw)
In-Reply-To: <20230519143117.23875-1-manivannan.sadhasivam@linaro.org>
On Fri, May 19, 2023 at 08:01:09PM +0530, Manivannan Sadhasivam wrote:
> Hi,
>
> The SoCs making use of Qualcomm PCIe controllers do not support the PCIe 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, this series clears the HPC bit in PCI_EXP_SLTCAP
> register as a part of the post init sequence for all IP versions to not
> advertise the hotplug capability for the controller.
>
> Testing
> =======
>
> This series has been tested on DB845c (SDM845 SoC) and Lenovo Thinkpad X13s
> (SC8280XP SoC).
>
> Thanks,
> Mani
>
> Changes in v2:
>
> * Collected tags
> * Moved the HPC clearing to a separate function and reused across different
> configs
>
> Manivannan Sadhasivam (8):
> PCI: qcom: Use DWC helpers for modifying the read-only DBI registers
> PCI: qcom: Disable write access to read only registers for IP v2.9.0
> PCI: qcom: Do not advertise hotplug capability for IPs v2.7.0 and
> v1.9.0
> PCI: qcom: Do not advertise hotplug capability for IPs v2.3.3 and
> v2.9.0
> PCI: qcom: Do not advertise hotplug capability for IP v2.3.2
> PCI: qcom: Use post init sequence of IP v2.3.2 for v2.4.0
> PCI: qcom: Do not advertise hotplug capability for IP v1.0.0
> PCI: qcom: Do not advertise hotplug capability for IP v2.1.0
>
> drivers/pci/controller/dwc/pcie-qcom.c | 73 ++++++++++++++------------
> 1 file changed, 38 insertions(+), 35 deletions(-)
>
Some patches are signed-off twice, FYI, I can fix that while
applying.
Lorenzo
> --
> 2.25.1
>
next prev parent reply other threads:[~2023-05-22 9:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 14:31 [PATCH v2 0/8] PCI: qcom: Do not advertise hotplug capability Manivannan Sadhasivam
2023-05-19 14:31 ` [PATCH v2 1/8] PCI: qcom: Use DWC helpers for modifying the read-only DBI registers Manivannan Sadhasivam
2023-05-19 14:31 ` [PATCH v2 2/8] PCI: qcom: Disable write access to read only registers for IP v2.9.0 Manivannan Sadhasivam
2023-05-22 8:56 ` Lorenzo Pieralisi
2023-05-29 8:55 ` Manivannan Sadhasivam
2023-05-22 13:00 ` Dmitry Baryshkov
2023-05-29 8:56 ` Manivannan Sadhasivam
2023-05-19 14:31 ` [PATCH v2 3/8] PCI: qcom: Do not advertise hotplug capability for IPs v2.7.0 and v1.9.0 Manivannan Sadhasivam
2023-05-19 14:31 ` [PATCH v2 4/8] PCI: qcom: Do not advertise hotplug capability for IPs v2.3.3 and v2.9.0 Manivannan Sadhasivam
2023-05-19 14:31 ` [PATCH v2 5/8] PCI: qcom: Do not advertise hotplug capability for IP v2.3.2 Manivannan Sadhasivam
2023-05-19 14:31 ` [PATCH v2 6/8] PCI: qcom: Use post init sequence of IP v2.3.2 for v2.4.0 Manivannan Sadhasivam
2023-05-19 14:31 ` [PATCH v2 7/8] PCI: qcom: Do not advertise hotplug capability for IP v1.0.0 Manivannan Sadhasivam
2023-05-19 14:31 ` [PATCH v2 8/8] PCI: qcom: Do not advertise hotplug capability for IP v2.1.0 Manivannan Sadhasivam
2023-05-22 9:01 ` Lorenzo Pieralisi [this message]
2023-05-29 8:58 ` [PATCH v2 0/8] PCI: qcom: Do not advertise hotplug capability 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=ZGsvXbiWK383zoaQ@lpieralisi \
--to=lpieralisi@kernel.org \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=dmitry.baryshkov@linaro.org \
--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=manivannan.sadhasivam@linaro.org \
--cc=quic_srichara@quicinc.com \
--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