From: Lukas Wunner <lukas@wunner.de>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH 1/1] PCI: Move reset and restore related code to reset-restore.c
Date: Wed, 14 May 2025 13:43:49 +0200 [thread overview]
Message-ID: <aCSB9Y5OwNkdiuez@wunner.de> (raw)
In-Reply-To: <7c8ebe5d-a5be-6aba-1b84-15dd2f32b52f@linux.intel.com>
On Wed, May 14, 2025 at 02:29:42PM +0300, Ilpo Järvinen wrote:
> On Wed, 14 May 2025, Lukas Wunner wrote:
> > > --- a/drivers/pci/pci.c
> > > +++ b/drivers/pci/pci.c
> > > @@ -69,15 +69,7 @@ struct pci_pme_device {
> > > */
> > > #define PCI_RESET_WAIT 1000 /* msec */
> >
> > I'd move PCI_RESET_WAIT, pci_dev_wait() and
> > pci_bridge_wait_for_secondary_bus() to reset.c as well.
> > Then pci_dev_d3_sleep() is the only function which is no longer static.
>
> Okay I'll move those as well but that static statement is not exactly
> true, I'll these need to do these as well:
>
> - move pci_bus_max_d3cold_delay() along with
> pci_bridge_wait_for_secondary_bus() to keep that static, or turn that
> into a non-static.
>
> - make pcie_wait_for_link_delay() non-static.
Sorry, missed that. In that case I suggest moving pcie_wait_for_link()
as well. It is already non-static. Then you can keep the static on
pcie_wait_for_link_delay().
Per PCIe r6.2 sec 5.8, a transition from D3cold to D0uninitialized
implies a Fundamental Reset. That could serve as a creative
justification in the commit message or in the code comment at the
top of reset.c why it contains D3cold-related functions. ;)
Thanks,
Lukas
next prev parent reply other threads:[~2025-05-14 11:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 12:08 [PATCH 1/1] PCI: Move reset and restore related code to reset-restore.c Ilpo Järvinen
2025-05-14 7:07 ` Lukas Wunner
2025-05-14 11:29 ` Ilpo Järvinen
2025-05-14 11:43 ` Lukas Wunner [this message]
2025-05-14 12:09 ` Ilpo Järvinen
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=aCSB9Y5OwNkdiuez@wunner.de \
--to=lukas@wunner.de \
--cc=bhelgaas@google.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--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