public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Marangi <ansuelsmth@gmail.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Stanimir Varbanov" <svarbanov@mm-sol.com>,
	"Andy Gross" <agross@kernel.org>,
	"Bjorn Andersson" <bjorn.andersson@linaro.org>,
	"Konrad Dybcio" <konrad.dybcio@somainline.org>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	linux-pci@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] PCI: qcom: Enable clocks only after PARF_PHY setup for rev 2.1.0
Date: Sat, 9 Jul 2022 03:03:34 +0200	[thread overview]
Message-ID: <62c8d3e8.1c69fb81.26eee.0249@mx.google.com> (raw)
In-Reply-To: <20220708230155.GA388993@bhelgaas>

On Fri, Jul 08, 2022 at 06:01:55PM -0500, Bjorn Helgaas wrote:
> On Sat, Jul 09, 2022 at 12:27:43AM +0200, Christian Marangi wrote:
> > We currently enable clocks BEFORE we write to PARF_PHY_CTRL reg to
> > enable clocks and resets. This case the driver to never set to a ready
> > state with the error 'Phy link never came up'.
> > 
> > This in fact is caused by the phy clock getting enabled before setting
> > the required bits in the PARF regs.
> > 
> > A workaround for this was set but with this new discovery we can drop
> > the workaround and use a proper solution to the problem by just enabling
> > the clock only AFTER the PARF_PHY_CTRL bit is set.
> > 
> > This correctly setup the pcie line and makes it usable even when a
> > bootloader leave the pcie line to a underfined state.
> 
> Is "pcie" here a signal name?  Maybe this refers to the "PCIe link"?
>

Hi,
no i was referring to PCIe link. Fell free to fix it if it's not a
problem (or if you want i can just resend)

> > Fixes: 82a823833f4e ("PCI: qcom: Add Qualcomm PCIe controller driver")
> > Cc: stable@vger.kernel.org # v5.4+
> > Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> 
> Thanks, I put this on
> https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git,
> pci/ctrl/qcom-pending branch (head 47b4ec9d2e60).
> 
> Can you take a look and make sure I didn't mess up the conflict
> resolution with the rest of the series?

Think something went wrong in the rebase as the patch fixup is reverted.

11946f8b6e77a6794c111aafef7772e9967d9a54 is still wrong.

clk_bulk_prepare_enable must be after 
writel(val, pcie->parf + PCIE20_PARF_PHY_CTRL);
so in the post init.

> 
> > ---
> >  drivers/pci/controller/dwc/pcie-qcom.c | 10 ++++------
> >  1 file changed, 4 insertions(+), 6 deletions(-)
> > 
> > diff --git a/drivers/pci/controller/dwc/pcie-qcom.c b/drivers/pci/controller/dwc/pcie-qcom.c
> > index 2ea13750b492..da13a66ced14 100644
> > --- a/drivers/pci/controller/dwc/pcie-qcom.c
> > +++ b/drivers/pci/controller/dwc/pcie-qcom.c
> > @@ -337,8 +337,6 @@ static int qcom_pcie_init_2_1_0(struct qcom_pcie *pcie)
> >  	reset_control_assert(res->ext_reset);
> >  	reset_control_assert(res->phy_reset);
> >  
> > -	writel(1, pcie->parf + PCIE20_PARF_PHY_CTRL);
> > -
> >  	ret = regulator_bulk_enable(ARRAY_SIZE(res->supplies), res->supplies);
> >  	if (ret < 0) {
> >  		dev_err(dev, "cannot enable regulators\n");
> > @@ -381,15 +379,15 @@ static int qcom_pcie_init_2_1_0(struct qcom_pcie *pcie)
> >  		goto err_deassert_axi;
> >  	}
> >  
> > -	ret = clk_bulk_prepare_enable(ARRAY_SIZE(res->clks), res->clks);
> > -	if (ret)
> > -		goto err_clks;
> > -
> >  	/* enable PCIe clocks and resets */
> >  	val = readl(pcie->parf + PCIE20_PARF_PHY_CTRL);
> >  	val &= ~BIT(0);
> >  	writel(val, pcie->parf + PCIE20_PARF_PHY_CTRL);
> >  
> > +	ret = clk_bulk_prepare_enable(ARRAY_SIZE(res->clks), res->clks);
> > +	if (ret)
> > +		goto err_clks;
> > +
> >  	if (of_device_is_compatible(node, "qcom,pcie-ipq8064") ||
> >  	    of_device_is_compatible(node, "qcom,pcie-ipq8064-v2")) {
> >  		writel(PCS_DEEMPH_TX_DEEMPH_GEN1(24) |
> > -- 
> > 2.36.1
> > 

-- 
	Ansuel

      reply	other threads:[~2022-07-09  1:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08 22:27 [PATCH] PCI: qcom: Enable clocks only after PARF_PHY setup for rev 2.1.0 Christian Marangi
2022-07-08 23:01 ` Bjorn Helgaas
2022-07-09  1:03   ` Christian Marangi [this message]

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=62c8d3e8.1c69fb81.26eee.0249@mx.google.com \
    --to=ansuelsmth@gmail.com \
    --cc=agross@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=helgaas@kernel.org \
    --cc=konrad.dybcio@somainline.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=robh@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=svarbanov@mm-sol.com \
    /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