From: Bjorn Helgaas <helgaas@kernel.org>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
"Richard Zhu" <hongxing.zhu@nxp.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"NXP Linux Team" <linux-imx@nxp.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>
Subject: Re: [PATCH] PCI: imx6: Fix link initialisation when the phy is ref clk provider
Date: Thu, 13 Oct 2022 09:04:50 -0500 [thread overview]
Message-ID: <20221013140450.GA3244741@bhelgaas> (raw)
In-Reply-To: <20221012132634.267970-1-s.hauer@pengutronix.de>
Would you mind rewording the subject so it says something more
specific about what the patch does? E.g.,
PCI: imx6: Initialize PHY before deasserting core reset
It may be that this ordering is only *required* when the PHY is the
ref clk provider, but the patch doesn't test for that; it *always*
initializes the PHY first.
On Wed, Oct 12, 2022 at 03:26:34PM +0200, Sascha Hauer wrote:
> When the phy is the reference clock provider then it must be initialised
> and powered on before the reset on the client is deasserted, otherwise
> the link will never come up. The order was changed in cf236e0c0d59.
> Restore the correct order to make the driver work again on boards where
> the phy provides the reference clock.
s/phy/PHY/ several places above
> Fixes: cf236e0c0d59 ("PCI: imx6: Do not hide PHY driver callbacks and refine the error handling")
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> ---
> drivers/pci/controller/dwc/pci-imx6.c | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/pci/controller/dwc/pci-imx6.c b/drivers/pci/controller/dwc/pci-imx6.c
> index b5f0de455a7bd..211eb55d6d34b 100644
> --- a/drivers/pci/controller/dwc/pci-imx6.c
> +++ b/drivers/pci/controller/dwc/pci-imx6.c
> @@ -942,12 +942,6 @@ static int imx6_pcie_host_init(struct dw_pcie_rp *pp)
> }
> }
>
> - ret = imx6_pcie_deassert_core_reset(imx6_pcie);
> - if (ret < 0) {
> - dev_err(dev, "pcie deassert core reset failed: %d\n", ret);
> - goto err_phy_off;
> - }
> -
> if (imx6_pcie->phy) {
> ret = phy_power_on(imx6_pcie->phy);
> if (ret) {
> @@ -955,6 +949,13 @@ static int imx6_pcie_host_init(struct dw_pcie_rp *pp)
> goto err_phy_off;
> }
> }
> +
> + ret = imx6_pcie_deassert_core_reset(imx6_pcie);
> + if (ret < 0) {
> + dev_err(dev, "pcie deassert core reset failed: %d\n", ret);
> + goto err_phy_off;
> + }
> +
> imx6_setup_phy_mpll(imx6_pcie);
>
> return 0;
> --
> 2.30.2
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-10-13 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 13:26 [PATCH] PCI: imx6: Fix link initialisation when the phy is ref clk provider Sascha Hauer
2022-10-13 4:50 ` Hongxing Zhu
2022-10-13 14:04 ` Bjorn Helgaas [this message]
2022-10-24 11:14 ` Sascha Hauer
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=20221013140450.GA3244741@bhelgaas \
--to=helgaas@kernel.org \
--cc=hongxing.zhu@nxp.com \
--cc=kernel@pengutronix.de \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
/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).