All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Lukas Wunner <lukas@wunner.de>
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 14:29:42 +0300 (EEST)	[thread overview]
Message-ID: <7c8ebe5d-a5be-6aba-1b84-15dd2f32b52f@linux.intel.com> (raw)
In-Reply-To: <aCRBFWHKa02Hu-ec@wunner.de>

[-- Attachment #1: Type: text/plain, Size: 2342 bytes --]

On Wed, 14 May 2025, Lukas Wunner wrote:

> On Mon, May 12, 2025 at 03:08:57PM +0300, Ilpo Järvinen wrote:
> > There are quite many reset and restore related functions in pci.c that
> > barely depend on the other functions in pci.c. Create reset-restore.c
> > for reset and restore related logic to keep those 1k lines in one place.
> > 
> > Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> 
> Hm, could I get a:
> 
> Suggested-by: Lukas Wunner <lukas@wunner.de>
> 
> ... per:
> 
> https://lore.kernel.org/r/Z7hZZNT5NHYncZ3c@wunner.de/

Ah, I hadn't even noticed you suggested it (I recall reading the first 
paragraph of that but not the last one which made the suggestion). I made 
this patch first back in 2024 and have just sit on top of the change until 
there seems to be reasonably conflict free window.

> >  drivers/pci/Makefile        |    4 +-
> >  drivers/pci/pci.c           | 1015 +----------------------------------
> >  drivers/pci/pci.h           |   10 +
> >  drivers/pci/reset-restore.c | 1014 ++++++++++++++++++++++++++++++++++
> 
> I'd prefer reset.c for succinctness.

I initially had reset.c but was worried the name is too narrow scoped,
I can change back to reset.c.

> That said, this patch conflicts with Mani's slot reset patches
> which a lot of people seem to be interested in:
> 
> https://lore.kernel.org/r/20250508-pcie-reset-slot-v4-0-7050093e2b50@linaro.org/
> 
> Maybe it's better to give Mani's series the advantage and defer
> this patch here to the next cycle.

Fine for me but those conflicts looks quite simple. Next cycle will 
have its own share of conflicts, I'm sure :-).

> > --- 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.

-- 
 i.

  reply	other threads:[~2025-05-14 11:29 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 [this message]
2025-05-14 11:43     ` Lukas Wunner
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=7c8ebe5d-a5be-6aba-1b84-15dd2f32b52f@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    /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.