From: Bjorn Helgaas <helgaas@kernel.org>
To: manivannan.sadhasivam@oss.qualcomm.com
Cc: Bartosz Golaszewski <brgl@kernel.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
Raj Kumar Bhagat <raj.bhagat@oss.qualcomm.com>,
Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
Subject: Re: [PATCH v2 0/2] PCI/pwrctrl: A couple of fixes
Date: Mon, 16 Mar 2026 17:32:29 -0500 [thread overview]
Message-ID: <20260316223229.GA58051@bhelgaas> (raw)
In-Reply-To: <20260223-pwrctrl-fixes-7-0-v2-0-97566dfb1809@oss.qualcomm.com>
On Mon, Feb 23, 2026 at 08:15:58PM +0530, Manivannan Sadhasivam via B4 Relay wrote:
> Hi,
>
> This series fixes a couple of issues introduced in the recent pwrctrl rework
> for v7.0. Both issues are due to some incorrect assumptions on deciding when to
> create pwrctrl devices. First issue is due to assuming that all OF graph nodes
> require pwrctrl and another one is due to assuming that all PCI child nodes are
> PCI devices.
>
> Both issues are fixed by changing the pwrctrl device creation logic in
> pwrctrl/core.
>
> Testing
> =======
>
> This series is tested on Lenovo Thinkpad T14s.
>
> Note for Bjorn H
> ================
>
> Even though only patch 1 is fixing a regression on the IPQ board which was not
> part of the testbed of the pwrctrl rework went in for v7.0, patch 2 is also
> fixing an actual issue, but it is not impacting any of the current upstream
> supported platforms. But I'd like to get these two patches merged for v7.0 so
> that both the issues are fixed in the same major release where the issues
> originated.
>
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
> ---
> Changes in v2:
> - Used the compatible match for detecting the PCI devices in DT
> - Link to v1: https://lore.kernel.org/r/20260217-pwrctrl-fixes-7-0-v1-0-b5671e58934f@oss.qualcomm.com
>
> ---
> Manivannan Sadhasivam (2):
> PCI/pwrctrl: Ensure that the remote endpoint node parent has the supply requirement
> PCI/pwrctrl: Only create pwrctrl device if the device node belongs to a PCI device
>
> drivers/pci/pwrctrl/core.c | 54 +++++++++++++++++++++++++++++++++++-----------
> 1 file changed, 41 insertions(+), 13 deletions(-)
Applied to pci/for-linus for v7.0, thanks!
prev parent reply other threads:[~2026-03-16 22:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 14:45 [PATCH v2 0/2] PCI/pwrctrl: A couple of fixes Manivannan Sadhasivam via B4 Relay
2026-02-23 14:45 ` [PATCH v2 1/2] PCI/pwrctrl: Ensure that the remote endpoint node parent has the supply requirement Manivannan Sadhasivam via B4 Relay
2026-02-23 14:46 ` [PATCH v2 2/2] PCI/pwrctrl: Only create pwrctrl device if the device node belongs to a PCI device Manivannan Sadhasivam via B4 Relay
2026-03-16 22:32 ` Bjorn Helgaas [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=20260316223229.GA58051@bhelgaas \
--to=helgaas@kernel.org \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=bhelgaas@google.com \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=krishna.chundru@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mani@kernel.org \
--cc=manivannan.sadhasivam@oss.qualcomm.com \
--cc=raj.bhagat@oss.qualcomm.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