Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: Niklas Cassel <cassel@kernel.org>,
	Wilfred Mallawa <wilfred.mallawa@wdc.com>,
	Bjorn Helgaas <helgaas@kernel.org>,
	Damien Le Moal <dlemoal@kernel.org>,
	linux-pci@vger.kernel.org
Subject: Re: reset_slot() callback not respecting MPS config
Date: Sat, 24 May 2025 14:40:23 +0200	[thread overview]
Message-ID: <aDG-NzeW0fdIwall@wunner.de> (raw)
In-Reply-To: <6jslic5nfxz3ywllriiw7uw6jwc6iz362nwuane6xam66kbv6a@x6krddl53mkg>

On Fri, May 23, 2025 at 09:00:27PM +0530, Manivannan Sadhasivam wrote:
> I thought that it *might* be possible to reset individual ports,
> so that's why I passed the root port 'pci_dev' to the callback
> in a hope that the controller drivers could use it to identify
> the root port they are resetting.

Makes sense.

> You are right. We should check if the parent bus of the bridge
> is a root bus or not.

Okay, that's simple enough:  pci_is_root_bus(dev->bus)

> Yes, pretty much so. I could rename it to reset_root_port(),
> since I still believe that multi root port setups may be able
> to reset them separately.

Conceivably, a PCIe host controller might also possess RCiEPs
in addition to Root Ports.  Those are allowed to be FLR-capable,
but could also be reset through a platform-specific means.

PCIe r6.3 page 121 defines the term "Root Complex Component",
which encompasses Root Ports but also RCiEPs.  So if you want to
be super generic, you could use that term in lieu of Root Port,
though it consumes more characters.

Thanks,

Lukas

  reply	other threads:[~2025-05-24 12:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-22 16:19 reset_slot() callback not respecting MPS config Niklas Cassel
2025-05-23  5:30 ` Wilfred Mallawa
2025-05-23  5:33 ` Lukas Wunner
2025-05-23  6:23   ` Wilfred Mallawa
2025-05-23  6:39   ` Manivannan Sadhasivam
2025-05-23 14:51     ` Lukas Wunner
2025-05-23 15:30       ` Manivannan Sadhasivam
2025-05-24 12:40         ` Lukas Wunner [this message]
2025-05-25  7:59           ` Manivannan Sadhasivam
2025-05-23  7:02   ` Niklas Cassel
2025-05-23 14:59     ` Lukas Wunner
2025-05-23 15:49 ` Manivannan Sadhasivam

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=aDG-NzeW0fdIwall@wunner.de \
    --to=lukas@wunner.de \
    --cc=cassel@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=helgaas@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=wilfred.mallawa@wdc.com \
    /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