Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Jim Quinlan <james.quinlan@broadcom.com>,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Cc: "open list:PCI NATIVE HOST BRIDGE AND ENDPOINT DRIVERS"
	<linux-pci@vger.kernel.org>, "'Cyril Brulebois" <kibi@debian.org>,
	"maintainer:BROADCOM BCM7XXX ARM ARCHITECTURE"
	<bcm-kernel-feedback-list@broadcom.com>,
	"'Nicolas Saenz Julienne" <nsaenz@kernel.org>,
	"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
	"Krzysztof Wilczyński" <kwilczynski@kernel.org>
Subject: Re: POSSIBLE REGRESSION: PCI/pwrctrl: Skip scanning for the device further if pwrctrl device is created
Date: Mon, 19 May 2025 09:05:57 -0500	[thread overview]
Message-ID: <20250519140557.GA1236950@bhelgaas> (raw)
In-Reply-To: <CA+-6iNwgaByXEYD3j=-+H_PKAxXRU78svPMRHDKKci8AGXAUPg@mail.gmail.com>

On Mon, May 05, 2025 at 01:39:39PM -0400, Jim Quinlan wrote:
> Hello,
> 
> I recently rebased to the latest Linux master
> 
> ebd297a2affa Linus.Torvalds Merge tag 'net-6.15-rc5' of
> git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net
> 
> and noticed that PCI is broken for
> "drivers/pci/controller/pcie-brcmstb.c"  I've bisected this to the
> following commit
> 
> 2489eeb777af PCI/pwrctrl: Skip scanning for the device further if
> pwrctrl device is created
> 
> which is part of the series [1].  The driver in pcie-brcmstb.c is
> expecting the add_bus() method to be invoked twice per boot-up, but
> the second call does not happen.  Not only does this code in
> brcm_pcie_add_bus() turn on regulators, it also subsequently initiates
> PCIe linkup.
> 
> If I revert the aforementioned commit, all is well.
> 
> FWIW, I have included the relevant sections of the PCIe DT we use at [2].

Mani, Bartosz, where are we at with this?  The 2489eeb777af commit log
doesn't mention a problem fixed by that commit; it sounds more like an
optimization -- just avoiding an unnecessary scan.

2489eeb777af appeared in v6.15-rc1, so there's still time to revert it
before v6.15 if that's the right way to fix this regression.

> [1] https://lore.kernel.org/lkml/20241231-pci-pwrctrl-slot-v2-0-6a15088ba541@linaro.org/T/#t
> [2]
> 
> pcie@1000110000 {
>         reg = <0x10 0x110000 0x0 0x9130>;
>         ...
> 
>         pci@0,0 {
>                 vpcie3v3-supply = <0x45>;
>                 vpcie12v-supply = <0x44>;
>                 reg = <0x0 0x0 0x0 0x0 0x0>;
>                 ranges;
>                 bus-range = <0x1 0xff>;
>                 compatible = "pciclass,0604";
>                 device_type = "pci";
>                 #address-cells = <0x3>;
>                 #size-cells = <0x2>;
> 
>                 pci-ep@0,0 {
>                         local-mac-address = [ 00 10 18 f0 35 55 ];
>                         reg = <0x10000 0x0 0x0 0x0 0x0>;
>                 };
>         };
> }



  reply	other threads:[~2025-05-19 14:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-05 17:39 POSSIBLE REGRESSION: PCI/pwrctrl: Skip scanning for the device further if pwrctrl device is created Jim Quinlan
2025-05-19 14:05 ` Bjorn Helgaas [this message]
2025-05-19 17:28   ` Manivannan Sadhasivam
2025-05-19 18:25     ` Jim Quinlan
2025-05-19 19:59       ` Jim Quinlan
2025-05-19 21:56         ` Bjorn Helgaas
2025-05-19 23:03           ` Jim Quinlan
2025-05-20  4:11             ` Manivannan Sadhasivam
2025-05-20 15:06               ` Jim Quinlan
2025-05-20 23:40                 ` Manivannan Sadhasivam
2025-05-21 22:08                   ` Jim Quinlan
2025-05-22  9:41                     ` Manivannan Sadhasivam
2025-05-19 17:26 ` 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=20250519140557.GA1236950@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=james.quinlan@broadcom.com \
    --cc=kibi@debian.org \
    --cc=kwilczynski@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=nsaenz@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