linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	lpieralisi@kernel.org, kw@linux.com, bhelgaas@google.com
Cc: robh@kernel.org, andersson@kernel.org, linux-pci@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	steev@kali.org, quic_srichara@quicinc.com
Subject: Re: [PATCH 5/8] PCI: qcom: Do not advertise hotplug capability for IP v2.3.2
Date: Sat, 6 May 2023 16:01:43 +0200	[thread overview]
Message-ID: <0e5f9f6b-eb67-38f8-2719-06aa8fe296bd@linaro.org> (raw)
In-Reply-To: <bc3ce44f-745a-bbad-32ac-67f8baa49483@linaro.org>



On 6.05.2023 14:04, Dmitry Baryshkov wrote:
> On 06/05/2023 10:31, Manivannan Sadhasivam wrote:
>> SoCs making use of Qcom PCIe controller IP v2.3.2 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 clear 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 | 10 ++++++++++
>>   1 file changed, 10 insertions(+)
>>
>> diff --git a/drivers/pci/controller/dwc/pcie-qcom.c b/drivers/pci/controller/dwc/pcie-qcom.c
>> index 3d5b3ce9e2da..33353be396ec 100644
>> --- a/drivers/pci/controller/dwc/pcie-qcom.c
>> +++ b/drivers/pci/controller/dwc/pcie-qcom.c
>> @@ -579,6 +579,8 @@ static int qcom_pcie_init_2_3_2(struct qcom_pcie *pcie)
>>     static int qcom_pcie_post_init_2_3_2(struct qcom_pcie *pcie)
>>   {
>> +    struct dw_pcie *pci = pcie->pci;
>> +    u16 offset = dw_pcie_find_capability(pci, PCI_CAP_ID_EXP);
>>       u32 val;
>>         /* enable PCIe clocks and resets */
>> @@ -602,6 +604,14 @@ static int qcom_pcie_post_init_2_3_2(struct qcom_pcie *pcie)
>>       val |= EN;
>>       writel(val, pcie->parf + PARF_AXI_MSTR_WR_ADDR_HALT_V2);
>>   +    dw_pcie_dbi_ro_wr_en(pci);
>> +
>> +    val = readl(pci->dbi_base + offset + PCI_EXP_SLTCAP);
>> +    val &= ~PCI_EXP_SLTCAP_HPC;
>> +    writel(val, pci->dbi_base + offset + PCI_EXP_SLTCAP);
>> +
>> +    dw_pcie_dbi_ro_wr_dis(pci);
>> +
> 
> Seeing this code again and again makes me wonder if we should have a separate function for this.
Moreover, is there no generic rmw type function for readl+writel?

Konrad
> 

  reply	other threads:[~2023-05-06 14:01 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
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 [this message]
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=0e5f9f6b-eb67-38f8-2719-06aa8fe296bd@linaro.org \
    --to=konrad.dybcio@linaro.org \
    --cc=andersson@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=dmitry.baryshkov@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=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;
as well as URLs for NNTP newsgroup(s).