linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: linux-pci@vger.kernel.org,
	Richard Zhu <Hong-Xing.Zhu@freescale.com>,
	Shawn Guo <Shawn.Guo@freescale.com>
Subject: Re: [PATCH 2/2] PCI: imx6: fix boot hang when link already enabled
Date: Thu, 4 Sep 2014 14:24:36 -0600	[thread overview]
Message-ID: <20140904202436.GA17125@google.com> (raw)
In-Reply-To: <1409743007.1535.1.camel@pengutronix.de>

On Wed, Sep 03, 2014 at 01:16:47PM +0200, Lucas Stach wrote:
> Am Donnerstag, den 14.08.2014, 14:22 -0600 schrieb Bjorn Helgaas:
> > On Thu, Jul 31, 2014 at 08:16:05PM +0200, Lucas Stach wrote:
> > > This fixes a boot hang observed when the bootloader
> > > already enabled the PCIe link for it's own use. The
> > > fundamental problem is that Freescale forgot to wire
> > > up the core reset, so software doesn't have a sane way
> > > to get the core into a defined state.
> > > 
> > > According to the DW PCIe core reference manual configuration
> > > of the core may only happen when the LTSSM is disabled, so
> > > this is one of the first things we need to do. Apparently
> > > this isn't safe to do when the LTSSM is in any other state
> > > than "detect" as we observe an instant machine hang when
> > > trying to do so while the link is already up.
> > > 
> > > As a workaround force LTSSM into detect state right before
> > > hitting the disable switch.
> > 
> 
> Bjorn,
> 
> I would have expected for this to show up in 3.17 as it fixes a real bug
> and has been posted some time ago. While you have picked it up into your
> pci/host-imx6 branch it doesn't show up in Linus tree nor in any pull
> requests AFAICS.
> Was it intentional from you to hold this patch or is this just an
> oversight?

Nope, I just missed it, thanks for the reminder.  I put in my
for-linus branch and will ask Linus to pull it after it's been
in -next for a few days.

Bjorn

  reply	other threads:[~2014-09-04 20:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-31 18:16 [PATCH 0/2] i.MX6 PCIe fixes for 3.17 Lucas Stach
2014-07-31 18:16 ` [PATCH 1/2] MAINTAINERS: add myself as co-maintainer for i.MX6 PCI driver Lucas Stach
2014-07-31 18:16 ` [PATCH 2/2] PCI: imx6: fix boot hang when link already enabled Lucas Stach
2014-08-09 17:49   ` Tim Harvey
2014-08-11  8:24     ` Lucas Stach
2014-08-15  5:01       ` Tim Harvey
2014-08-14 20:22   ` Bjorn Helgaas
2014-08-15  9:57     ` Lucas Stach
2014-09-03 11:16     ` Lucas Stach
2014-09-04 20:24       ` Bjorn Helgaas [this message]
2014-09-22 13:27         ` Fabio Estevam
2014-09-22 13:32           ` Lucas Stach
2014-09-22 14:08             ` Fabio Estevam

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=20140904202436.GA17125@google.com \
    --to=bhelgaas@google.com \
    --cc=Hong-Xing.Zhu@freescale.com \
    --cc=Shawn.Guo@freescale.com \
    --cc=l.stach@pengutronix.de \
    --cc=linux-pci@vger.kernel.org \
    /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).