From: Johan Hovold <johan@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Bjorn Helgaas <helgaas@kernel.org>
Cc: "Krishna Chaitanya Chundru" <quic_krichai@quicinc.com>,
rafael@kernel.org, ulf.hansson@linaro.org,
"Kevin Xie" <kevin.xie@starfivetech.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
Markus.Elfring@web.de, quic_mrana@quicinc.com,
m.szyprowski@samsung.com, linux-pm@vger.kernel.org,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev
Subject: Re: [PATCH v7 2/2] PCI: Enable runtime pm of the host bridge
Date: Mon, 20 Jan 2025 11:29:41 +0100 [thread overview]
Message-ID: <Z44llTKsKfbEcnnI@hovoldconsulting.com> (raw)
In-Reply-To: <20250119152940.6yum3xnrvqx2xjme@thinkpad>
On Sun, Jan 19, 2025 at 08:59:40PM +0530, Manivannan Sadhasivam wrote:
> On Tue, Jan 14, 2025 at 03:16:53PM -0600, Bjorn Helgaas wrote:
> > On Mon, Jan 13, 2025 at 09:55:49PM +0530, Manivannan Sadhasivam wrote:
> > > On Tue, Jan 07, 2025 at 03:27:59PM +0100, Johan Hovold wrote:
> > > > > > I just noticed that this change in 6.13-rc1 is causing the
> > > > > > following warning on resume from suspend on machines like the
> > > > > > Lenovo ThinkPad X13s:
> > > > > > pci0004:00: pcie4: Enabling runtime PM for inactive device with active children
> > > > > > which may have unpopulated ports (this laptop SKU does not
> > > > > > have a modem).
> > What's the plan for this? Does anybody have a proposal?
> >
>
> TBH, I don't know how to fix this issue in a proper way. I need inputs from
> Rafael/Ulf.
>
> > IIUC there is no functional issue, but the new warning must be fixed,
> > and it would sure be nice to do it before v6.13. If there *is* a
> > functional problem, we need to consider a revert ASAP.
> >
>
> There is no functional problem that I'm aware of, so revert is not warranted.
I'd argue for reverting the offending commit as that is the only way to
make sure that the new warning is ever addressed.
Vendors unfortunately do not a have a good track record of following up
and fixing issues like this.
Judging from a quick look at the code (and the commit message of the
patch in question), no host controller driver depends on the commit in
question as the ones that do enable runtime PM just resume
unconditionally at probe() currently (i.e. effectively ignores the state
of their children).
Johan
next prev parent reply other threads:[~2025-01-20 10:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 8:41 [PATCH v7 0/2] PCI: Enable runtime pm of the host bridge Krishna chaitanya chundru
2024-11-11 8:41 ` [PATCH v7 1/2] PCI: starfive: Enable PCIe controller's runtime PM before probing " Krishna chaitanya chundru
2024-11-11 8:41 ` [PATCH v7 2/2] PCI: Enable runtime pm of the " Krishna chaitanya chundru
2024-11-11 16:46 ` Markus Elfring
2024-11-13 5:24 ` Krishna Chaitanya Chundru
2025-01-07 13:19 ` Johan Hovold
2025-01-07 14:10 ` Krishna Chaitanya Chundru
2025-01-07 14:27 ` Johan Hovold
2025-01-13 16:25 ` Manivannan Sadhasivam
2025-01-14 21:16 ` Bjorn Helgaas
2025-01-19 15:29 ` Manivannan Sadhasivam
2025-01-20 10:29 ` Johan Hovold [this message]
2025-01-20 15:28 ` Manivannan Sadhasivam
2025-01-21 13:18 ` Johan Hovold
2025-01-21 13:34 ` Johan Hovold
2025-01-24 5:15 ` Manivannan Sadhasivam
2025-01-27 14:31 ` Ulf Hansson
2025-01-27 19:57 ` Rafael J. Wysocki
2025-01-28 11:47 ` Rafael J. Wysocki
2025-01-28 15:58 ` Manivannan Sadhasivam
2025-01-28 16:07 ` Rafael J. Wysocki
2024-11-12 23:44 ` [PATCH v7 0/2] " Bjorn Helgaas
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=Z44llTKsKfbEcnnI@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=Markus.Elfring@web.de \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=kevin.xie@starfivetech.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=quic_krichai@quicinc.com \
--cc=quic_mrana@quicinc.com \
--cc=rafael@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=robh@kernel.org \
--cc=ulf.hansson@linaro.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