From: Marek Vasut <marex@denx.de>
To: Fabio Estevam <festevam@gmail.com>
Cc: Tim Harvey <tharvey@gateworks.com>,
Lucas Stach <l.stach@pengutronix.de>,
Shawn Guo <shawn.guo@freescale.com>,
Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH] PCI: imx6: fix occasional link failure
Date: Mon, 11 Aug 2014 19:15:46 +0200 [thread overview]
Message-ID: <201408111915.46321.marex@denx.de> (raw)
In-Reply-To: <CAOMZO5A+++cABSKFZR8-NUeNw1sASr_32Odymdp=JDXGGSJoNg@mail.gmail.com>
On Friday, August 08, 2014 at 05:59:23 PM, Fabio Estevam wrote:
> On Fri, Aug 8, 2014 at 3:36 AM, Tim Harvey <tharvey@gateworks.com> 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>
>
> Thanks, Tim.
>
> Marek,
>
> Does this fix the PCI linkup failures you reported earlier?
I currently don't have the board available, so I will moan later if this is
still broken. Please go ahead and apply, the patch looks good to me:
Acked-by: Marek Vasut <marex@denx.de>
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-08-11 17:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 6:36 [PATCH] PCI: imx6: fix occasional link failure 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 [this message]
2014-08-11 16:17 ` Fabio Estevam
2014-09-16 23:28 ` Bjorn Helgaas
2014-09-16 23:53 ` Marek Vasut
[not found] <Message-Id: <1407479800-6730-1-git-send-email-tharvey@gateworks.com>
2014-09-03 4:04 ` Tim Harvey
2014-09-05 17:32 ` Bjorn Helgaas
2014-09-08 18:27 ` Lucas Stach
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=201408111915.46321.marex@denx.de \
--to=marex@denx.de \
--cc=bhelgaas@google.com \
--cc=festevam@gmail.com \
--cc=l.stach@pengutronix.de \
--cc=linux-pci@vger.kernel.org \
--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).