From: Lucas Stach <l.stach@pengutronix.de>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Tim Harvey <tharvey@gateworks.com>,
Fabio Estevam <festevam@gmail.com>,
shawn.guo@freescale.com, marex@denx.de,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: imx6: fix occasional link failure
Date: Mon, 08 Sep 2014 20:27:56 +0200 [thread overview]
Message-ID: <1410200876.3945.2.camel@pengutronix.de> (raw)
In-Reply-To: <20140905173216.GB8080@google.com>
Am Freitag, den 05.09.2014, 11:32 -0600 schrieb Bjorn Helgaas:
> On Tue, Sep 02, 2014 at 09:04:37PM -0700, Tim Harvey wrote:
> > According to the IMX6 reference manuals, REF_SSP_EN (Reference clock enable
> > for SS function) must remain deasserted until the reference clock is running
> > at the appropriate frequency.
> >
> > Without this patch we find a high link failure rate (>5%) on certain
> > IMX6 boards at various temperatures.
> >
> > Signed-off-by: Tim Harvey <tharvey@gateworks.com>
> > Tested-by: Fabio Estevam <festevam@gmail.com>
> > Acked-by: Marek Vasut <marex@denx.de>
>
> I'm looking for the comment update requested by Richard, and an ack from
> Richard and/or Lucas. Also, please add the stable tag if you want it
> (see Documentation/stable_kernel_rules.txt for details).
>
We already have a comment some line above regarding clock stabilization,
so I don't think another one is strictly needed. Especially as this
initialization order is clearly defined by the reference manual.
So with or without the comment added:
Acked-by: Lucas Stach <l.stach@pengutronix.de>
> Bjorn
>
> > ---
> >
> > v2:
> > - added Tested-by Fabio Estevam
> > - added Acked-by Marek Vasut
> >
> > ---
> > drivers/pci/host/pci-imx6.c | 11 ++++++-----
> > 1 file changed, 6 insertions(+), 5 deletions(-)
> >
> > diff --git a/drivers/pci/host/pci-imx6.c b/drivers/pci/host/pci-imx6.c
> > index 1be6073..9b6bab9 100644
> > --- a/drivers/pci/host/pci-imx6.c
> > +++ b/drivers/pci/host/pci-imx6.c
> > @@ -256,11 +256,6 @@ static int imx6_pcie_deassert_core_reset(struct pcie_port *pp)
> > struct imx6_pcie *imx6_pcie = to_imx6_pcie(pp);
> > int ret;
> >
> > - regmap_update_bits(imx6_pcie->iomuxc_gpr, IOMUXC_GPR1,
> > - IMX6Q_GPR1_PCIE_TEST_PD, 0 << 18);
> > - regmap_update_bits(imx6_pcie->iomuxc_gpr, IOMUXC_GPR1,
> > - IMX6Q_GPR1_PCIE_REF_CLK_EN, 1 << 16);
> > -
> > ret = clk_prepare_enable(imx6_pcie->pcie_phy);
> > if (ret) {
> > dev_err(pp->dev, "unable to enable pcie_phy clock\n");
> > @@ -282,6 +277,12 @@ static int imx6_pcie_deassert_core_reset(struct pcie_port *pp)
> > /* allow the clocks to stabilize */
> > usleep_range(200, 500);
> >
> > + /* power up core phy and enable ref clock */
> > + regmap_update_bits(imx6_pcie->iomuxc_gpr, IOMUXC_GPR1,
> > + IMX6Q_GPR1_PCIE_TEST_PD, 0 << 18);
> > + regmap_update_bits(imx6_pcie->iomuxc_gpr, IOMUXC_GPR1,
> > + IMX6Q_GPR1_PCIE_REF_CLK_EN, 1 << 16);
> > +
> > /* Some boards don't have PCIe reset GPIO. */
> > if (gpio_is_valid(imx6_pcie->reset_gpio)) {
> > gpio_set_value(imx6_pcie->reset_gpio, 0);
> > --
> > 1.8.3.2
> >
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Pengutronix e.K. | Lucas Stach |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2014-09-08 18:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Message-Id: <1407479800-6730-1-git-send-email-tharvey@gateworks.com>
2014-09-03 4:04 ` [PATCH] PCI: imx6: fix occasional link failure Tim Harvey
2014-09-05 17:32 ` Bjorn Helgaas
2014-09-08 18:27 ` Lucas Stach [this message]
2014-08-08 6:36 Tim Harvey
2014-08-08 8:04 ` Hong-Xing.Zhu
2014-08-08 13:24 ` Greg KH
2014-08-08 15:59 ` Fabio Estevam
2014-08-11 17:15 ` Marek Vasut
2014-08-11 16:17 ` Fabio Estevam
2014-09-16 23:28 ` Bjorn Helgaas
2014-09-16 23:53 ` Marek Vasut
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=1410200876.3945.2.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=bhelgaas@google.com \
--cc=festevam@gmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=marex@denx.de \
--cc=shawn.guo@freescale.com \
--cc=tharvey@gateworks.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;
as well as URLs for NNTP newsgroup(s).