All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: "Lucas Stach" <l.stach@pengutronix.de>,
	"Pengutronix Kernel Team" <kernel@pengutronix.de>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Francesco Dolcini" <francesco.dolcini@toradex.com>,
	"Richard Zhu" <hongxing.zhu@nxp.com>,
	"Fabio Estevam" <festevam@gmail.com>,
	"NXP Linux Team" <linux-imx@nxp.com>,
	"Rob Herring" <robh@kernel.org>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Shawn Guo <shawnguo@kernel.org>,
	Bjorn Helgaas <helgaas@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Sascha Hauer <s.hauer@pengutronix.de>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH v3] PCI: imx6: Fix PERST# start-up sequence
Date: Wed, 11 May 2022 13:51:39 +0100	[thread overview]
Message-ID: <165227348638.11227.1444036865071474526.b4-ty@arm.com> (raw)
In-Reply-To: <20220404081509.94356-1-francesco.dolcini@toradex.com>

On Mon, 4 Apr 2022 10:15:09 +0200, Francesco Dolcini wrote:
> According to the PCIe standard the PERST# signal (reset-gpio in
> fsl,imx* compatible dts) should be kept asserted for at least 100 usec
> before the PCIe refclock is stable, should be kept asserted for at
> least 100 msec after the power rails are stable and the host should wait
> at least 100 msec after it is de-asserted before accessing the
> configuration space of any attached device.
> 
> [...]

Applied to pci/imx6, thanks!

[1/1] PCI: imx6: Fix PERST# start-up sequence
      https://git.kernel.org/lpieralisi/pci/c/a6809941c1

Thanks,
Lorenzo

WARNING: multiple messages have this Message-ID (diff)
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: "Lucas Stach" <l.stach@pengutronix.de>,
	"Pengutronix Kernel Team" <kernel@pengutronix.de>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Francesco Dolcini" <francesco.dolcini@toradex.com>,
	"Richard Zhu" <hongxing.zhu@nxp.com>,
	"Fabio Estevam" <festevam@gmail.com>,
	"NXP Linux Team" <linux-imx@nxp.com>,
	"Rob Herring" <robh@kernel.org>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Shawn Guo <shawnguo@kernel.org>,
	Bjorn Helgaas <helgaas@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Sascha Hauer <s.hauer@pengutronix.de>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH v3] PCI: imx6: Fix PERST# start-up sequence
Date: Wed, 11 May 2022 13:51:39 +0100	[thread overview]
Message-ID: <165227348638.11227.1444036865071474526.b4-ty@arm.com> (raw)
In-Reply-To: <20220404081509.94356-1-francesco.dolcini@toradex.com>

On Mon, 4 Apr 2022 10:15:09 +0200, Francesco Dolcini wrote:
> According to the PCIe standard the PERST# signal (reset-gpio in
> fsl,imx* compatible dts) should be kept asserted for at least 100 usec
> before the PCIe refclock is stable, should be kept asserted for at
> least 100 msec after the power rails are stable and the host should wait
> at least 100 msec after it is de-asserted before accessing the
> configuration space of any attached device.
> 
> [...]

Applied to pci/imx6, thanks!

[1/1] PCI: imx6: Fix PERST# start-up sequence
      https://git.kernel.org/lpieralisi/pci/c/a6809941c1

Thanks,
Lorenzo

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-05-11 12:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04  8:15 [PATCH v3] PCI: imx6: Fix PERST# start-up sequence Francesco Dolcini
2022-04-04  8:15 ` Francesco Dolcini
2022-04-11 16:00 ` Lucas Stach
2022-04-11 16:00   ` Lucas Stach
2022-04-11 16:50 ` Lorenzo Pieralisi
2022-04-11 16:50   ` Lorenzo Pieralisi
2022-05-09 14:09   ` Francesco Dolcini
2022-05-09 14:09     ` Francesco Dolcini
2022-05-10 17:49     ` Lorenzo Pieralisi
2022-05-10 17:49       ` Lorenzo Pieralisi
2022-05-11  7:13       ` Francesco Dolcini
2022-05-11  7:13         ` Francesco Dolcini
2022-05-11  9:32         ` Pali Rohár
2022-05-11  9:32           ` Pali Rohár
2022-05-11 12:51 ` Lorenzo Pieralisi [this message]
2022-05-11 12:51   ` Lorenzo Pieralisi

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=165227348638.11227.1444036865071474526.b4-ty@arm.com \
    --to=lorenzo.pieralisi@arm.com \
    --cc=festevam@gmail.com \
    --cc=francesco.dolcini@toradex.com \
    --cc=helgaas@kernel.org \
    --cc=hongxing.zhu@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=kw@linux.com \
    --cc=l.stach@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.