linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: l.stach@pengutronix.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] PCI: mvebu: change delay after reset to the PCIe spec mandated 100ms
Date: Tue, 31 Jan 2017 11:27:05 +0100	[thread overview]
Message-ID: <1485858425.21479.31.camel@pengutronix.de> (raw)
In-Reply-To: <20170130204740.GT20550@bhelgaas-glaptop.roam.corp.google.com>

Am Montag, den 30.01.2017, 14:47 -0600 schrieb Bjorn Helgaas:
> On Mon, Jan 16, 2017 at 12:11:42PM +0100, Lucas Stach wrote:
> > The current default of 20ms cause some devices, which are slow to initialize,
> > to not show up during the bus scanning. Change this to the PCIe spec mandated
> > 100ms and document this in the DT binding.
> > 
> > From PCIe base spec rev 3.0, chapter "6.6.1. Conventional Reset":
> > 
> > "To allow components to perform internal initialization, system software must
> > wait a specified minimum period following the end of a Conventional Reset of
> > one or more devices before it is permitted to issue Configuration Requests to
> > those devices.
> > 
> > With a Downstream Port that does not support Link speeds greater than
> > 5.0 GT/s, software must wait a minimum of 100 ms before sending a
> > Configuration Request to the device immediately below that Port."
> > 
> > Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> > ---
> >  Documentation/devicetree/bindings/pci/mvebu-pci.txt | 3 ++-
> >  drivers/pci/host/pci-mvebu.c                        | 2 +-
> >  2 files changed, 3 insertions(+), 2 deletions(-)
> > 
> > diff --git a/Documentation/devicetree/bindings/pci/mvebu-pci.txt b/Documentation/devicetree/bindings/pci/mvebu-pci.txt
> > index 08c716b2c6b6..2de6f65ecfb1 100644
> > --- a/Documentation/devicetree/bindings/pci/mvebu-pci.txt
> > +++ b/Documentation/devicetree/bindings/pci/mvebu-pci.txt
> > @@ -78,7 +78,8 @@ and the following optional properties:
> >    multiple lanes. If this property is not found, we assume that the
> >    value is 0.
> >  - reset-gpios: optional gpio to PERST#
> > -- reset-delay-us: delay in us to wait after reset de-assertion
> > +- reset-delay-us: delay in us to wait after reset de-assertion, if not
> > +  specified will default to 100ms, as required by the PCIe specification.
> >  
> >  Example:
> >  
> > diff --git a/drivers/pci/host/pci-mvebu.c b/drivers/pci/host/pci-mvebu.c
> > index 45a89d969700..0c9dd47ce74d 100644
> > --- a/drivers/pci/host/pci-mvebu.c
> > +++ b/drivers/pci/host/pci-mvebu.c
> > @@ -1162,7 +1162,7 @@ static int mvebu_pcie_powerup(struct mvebu_pcie_port *port)
> >  		return ret;
> >  
> >  	if (port->reset_gpio) {
> > -		u32 reset_udelay = 20000;
> > +		u32 reset_udelay = 100000;
> 
> Can we use "PCI_PM_D3COLD_WAIT * 1000" for the initial value to connect it
> with other similar cases?

Sure, I didn't know there is a define for this. Will send an updated
patch.

Regards,
Lucas

      reply	other threads:[~2017-01-31 10:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16 11:11 [PATCH] PCI: mvebu: change delay after reset to the PCIe spec mandated 100ms Lucas Stach
2017-01-16 11:44 ` Jason Cooper
2017-01-30 20:47 ` Bjorn Helgaas
2017-01-31 10:27   ` Lucas Stach [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=1485858425.21479.31.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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).