[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86909e66-32a9-8f61-3d17-8356b5552597@quicinc.com>
Date: Tue, 20 Sep 2022 15:00:38 -0700
From: Jeff Johnson <quic_jjohnson@...cinc.com>
To: Krishna chaitanya chundru <quic_krichai@...cinc.com>,
<helgaas@...nel.org>
CC: <linux-pci@...r.kernel.org>, <linux-arm-msm@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <mka@...omium.org>,
<quic_vbadigan@...cinc.com>, <quic_hemantk@...cinc.com>,
<quic_nitegupt@...cinc.com>, <quic_skananth@...cinc.com>,
<quic_ramkri@...cinc.com>, <manivannan.sadhasivam@...aro.org>,
<swboyd@...omium.org>, <dmitry.baryshkov@...aro.org>,
<svarbanov@...sol.com>, <agross@...nel.org>,
<andersson@...nel.org>, <konrad.dybcio@...ainline.org>,
<lpieralisi@...nel.org>, <robh@...nel.org>, <kw@...ux.com>,
<bhelgaas@...gle.com>, <linux-phy@...ts.infradead.org>,
<vkoul@...nel.org>, <kishon@...com>, <mturquette@...libre.com>,
<linux-clk@...r.kernel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>
Subject: Re: [PATCH v7 2/5] PCI: qcom: Add retry logic for link to be stable
in either L1.1 or L1.2
On 9/20/2022 3:22 AM, Krishna chaitanya chundru wrote:
> When link is in L1ss(L1.1 or L1.2), all the clocks will gate off and there
> will be no activity on the link. At that point clocks and phy
> can be turned off. If clocks got disabled before link enters
> L1ss the PCIe link goes down.
>
> Few endpoints are taking time more time to settle the link in L1 substates.
"time more time" does not parse
> When we check the traffic in protocol analyzer, we see some DLLP packets
> going on still. So Wait for max time of 200ms for the link to be stable in
s/Wait/wait/
> L1 substates.
>
> Signed-off-by: Krishna chaitanya chundru <quic_krichai@...cinc.com>
> ---
> changes since v6:
> - updated comments.
> ---
> drivers/pci/controller/dwc/pcie-qcom.c | 46 ++++++++++++++++++++++++++--------
> 1 file changed, 35 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/pci/controller/dwc/pcie-qcom.c b/drivers/pci/controller/dwc/pcie-qcom.c
> index 3f5424a..7a6f69e 100644
> --- a/drivers/pci/controller/dwc/pcie-qcom.c
> +++ b/drivers/pci/controller/dwc/pcie-qcom.c
> @@ -1809,23 +1809,47 @@ static int qcom_pcie_probe(struct platform_device *pdev)
> static int __maybe_unused qcom_pcie_pm_suspend(struct qcom_pcie *pcie)
> {
> u32 val;
> + ktime_t timeout, start;
> struct dw_pcie *pci = pcie->pci;
> struct device *dev = pci->dev;
>
> - /* if the link is not active turn off clocks */
> - if (!dw_pcie_link_up(pci)) {
> - dev_dbg(dev, "Link is not active\n");
> - goto suspend;
> - }
> + /*
> + * When link is in L1ss, all the clocks will gate off and
> + * there will be no activity on the link. At that point clocks
> + * and phy can be turned off. If clocks got disabled before
> + * link enters L1ss the PCIe link goes down.
> + *
> + * Few endpoints are taking time more time to settle the link
"time more time" does not parse
> + * in L1ss. Wait for max of 200ms for the link to be stable in
> + * L1ss.
> + */
> + start = ktime_get();
> + /* Wait max 200 ms */
> + timeout = ktime_add_ms(start, 200);
> +
> + while (1) {
> + /* if the liink is not active turn off clocks */
> + if (!dw_pcie_link_up(pci)) {
> + dev_dbg(dev, "Link is not active\n");
> + break;
> + }
>
> - /* if the link is not in l1ss don't turn off clocks */
> - val = readl(pcie->parf + PCIE20_PARF_PM_STTS);
> - if (!(val & PCIE20_PARF_PM_STTS_LINKST_IN_L1SUB)) {
> - dev_warn(dev, "Link is not in L1ss\n");
> - return 0;
> + /* if the link is not in l1ss don't turn off clocks */
> + val = readl(pcie->parf + PCIE20_PARF_PM_STTS);
> + if ((val & PCIE20_PARF_PM_STTS_LINKST_IN_L1SUB)) {
> + dev_dbg(dev, "Link enters L1ss after %lld ms\n",
> + ktime_to_ms(ktime_get() - start));
> + break;
> + }
> +
> + if (ktime_after(ktime_get(), timeout)) {
> + dev_warn(dev, "Link is not in L1ss\n");
> + return 0;
> + }
> +
> + udelay(1000);
> }
>
> -suspend:
> if (pcie->cfg->ops->suspend)
> pcie->cfg->ops->suspend(pcie);
>
Powered by blists - more mailing lists