On Thu, Oct 3, 2024 at 1:07 PM Johan Hovold <johan@xxxxxxxxxx> wrote: > > On Mon, Sep 30, 2024 at 12:30:39PM +0200, Bartosz Golaszewski wrote: > > From: Bartosz Golaszewski <bartosz.golaszewski@xxxxxxxxxx> > > > > Add a node for the PMU of the WCN6855 and rework the inputs of the wifi > > and bluetooth nodes to consume the PMU's outputs. > > > > With this we can drop the regulator-always-on properties from vreg_s11b > > and vreg_s12b as they will now be enabled by the power sequencing > > driver. > > > > Tested-by: Steev Klimaszewski <steev@xxxxxxxx> # Thinkpad X13s > > Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@xxxxxxxxxx> > > Without this patch I'm seeing an indefinite probe deferral with > 6.12-rc1: > > platform 1c00000.pcie:pcie@0:wifi@0: deferred probe pending: pci-pwrctl-pwrseq: Failed to get the power sequencer > > Can you please look into that and make sure that the existing DT > continues to work without such warnings. > Ah, dammit, I missed the fact that X13s already has this node defined so PCI pwrctl will consume it and try to get the power sequencer handle. I'm wondering how to tackle it though... It will most likely require some kind of a driver quirk where we check if we have the PMU node and if not, then don't try to set up power sequencing. Any other ideas? > > - > > - enable-gpios = <&tlmm 133 GPIO_ACTIVE_HIGH>; > > - swctrl-gpios = <&tlmm 132 GPIO_ACTIVE_HIGH>; > > What about swctrl? You're just removing this pin from DT now without any > comment on why you think that is the right thing to do. > > Should this one also be an input to the PMU block? > I recently added it to the bindings as an optional property. It's technically an output of the PMU to the host indicating the state of the clock supply to the BT module. We're not really using it but I can keep it here if you prefer. Bart
