Re: [PATCH v3 0/7] PCI/pwrctrl: Major rework to integrate pwrctrl devices with controller drivers

From: Manivannan Sadhasivam

Date: Tue Dec 30 2025 - 07:33:29 EST


On Tue, Dec 30, 2025 at 12:31:11PM +0100, Niklas Cassel wrote:
> Hello Mani,
>
> On Mon, Dec 29, 2025 at 10:56:51PM +0530, Manivannan Sadhasivam via B4 Relay wrote:
> > **NOTE**: With this series, the controller driver may undergo multiple probe
> > deferral if the pwrctrl driver was not available during the controller driver
> > probe. This is pretty much required to avoid the resource allocation issue. I
> > plan to replace probe deferral with blocking wait in the coming days.
>
> It sounds like you want to base that upcoming series on top of this series.
>
> Considering that we are only at -rc3, would it perhaps be a good idea to
> wait for you to implement the blocking wait, so that it can be part of
> this series, to avoid the additional code churn?
>

Blocking wait feture is not strictly required for this functionality. It is
something I wanted to implement to avoid multiple probe deferrals, but blocking
wait will also achieve the same by just waiting for all pwrctrl drivers to be
probed instead of returning -EPROBE_DEFER.

But I haven't figured out yet on how to do it though. That's why I sent this
series to allow it to be put into -next and have some test coverage.

If I happen to send the blocking wait patches this cycle itself (should be
atmost 2 patches), those patches could be squashed with this series itself. So
I don't see it as a big churn.

- Mani

--
மணிவண்ணன் சதாசிவம்