From: Francesco Dolcini <francesco.dolcini@toradex.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Francesco Dolcini" <francesco.dolcini@toradex.com>,
"Richard Zhu" <hongxing.zhu@nxp.com>,
"Lucas Stach" <l.stach@pengutronix.de>,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"NXP Linux Team" <linux-imx@nxp.com>,
"Shawn Guo" <shawnguo@kernel.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1] PCI: imx6: Fix PERST# start-up sequence
Date: Mon, 14 Feb 2022 14:20:46 +0100 [thread overview]
Message-ID: <20220214132046.GA87171@francesco-nb.int.toradex.com> (raw)
In-Reply-To: <20220211181824.GA718271@bhelgaas>
Hello Bjorn,
thanks for the review.
On Fri, Feb 11, 2022 at 12:18:24PM -0600, Bjorn Helgaas wrote:
> Mention spec rev & section here, too. Someday we'll consolidate these
> with #defines and identifying all the delays related to sec 6.6.1 (or
> whatever it is) will be important.
I added all the references and will send the v2 later today, however I
do not have access to the PCI-SIG specifications anymore, therefore I'll
mention the one I currently have access to (I did not copy the sections
you mentioned just because you wrote "probably" and I had no way to
double check).
I guess that this should not be a big deal, since we already have
different version of the standard mentioned thought the code with
reference to this topic.
Francesco
prev parent reply other threads:[~2022-02-14 13:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 15:25 [PATCH v1] PCI: imx6: Fix PERST# start-up sequence Francesco Dolcini
2022-02-11 18:18 ` Bjorn Helgaas
2022-02-14 13:20 ` Francesco Dolcini [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=20220214132046.GA87171@francesco-nb.int.toradex.com \
--to=francesco.dolcini@toradex.com \
--cc=festevam@gmail.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=lorenzo.pieralisi@arm.com \
--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 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).