Re: [PATCH v5 06/11] Bluetooth: hci_qca: Set 'bt_en_available' based on pwrseq power controllability
Manivannan Sadhasivam <[email protected]>
| Newsgroups | org.kernel.vger.linux-bluetooth,org.kernel.vger.linux-arm-msm,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel,org.kernel.vger.linux-pci,org.kernel.vger.linux-pm |
|---|---|
| Message-ID | <fggkksxpo7qcpyxoggnsdup5nrlbj6y47lleuytmchcfs7rmft@3i7m7iwf2lup> |
On Mon, Jul 20, 2026 at 10:04:08AM +0200, Loic Poulain wrote: > A Bluetooth device only needs the non-persistent setup if the host can > gate its power, so that it is actually reset on the next power-on. When the > power is controlled by a power sequencer, whether the host can gate it > depends on the hardware wiring, e.g. the presence of the BT_EN or > W_DISABLE2# line. > > Query the generic pwrseq_is_controllable() helper whenever the BT power > comes from a sequencer, regardless of which provider it is (M2, WCN, ...). > If the power is not controllable, clear 'bt_en_available' so that > HCI_QUIRK_NON_PERSISTENT_SETUP is not set. > > This is based on Manivannan's original patch that keyed the decision off > the W_DISABLE2# device tree property, it now uses the generic pwrseq helper > and handles the always-on case. > > Signed-off-by: Loic Poulain <[email protected]> Reviewed-by: Manivannan Sadhasivam <[email protected]> - Mani -- மணிவண்ணன் சதாசிவம்