Re: [PATCH v5 04/11] power: sequencing: pcie-m2: Report 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 | <pugjugitz7qmwcua4biufmmltmdwe7n4p4ivpwxmxqiefhtg7u@gatoruxxcwid> |
On Mon, Jul 20, 2026 at 10:04:06AM +0200, Loic Poulain wrote: > The M.2 Key E connector gates/resets its functions through the > W_DISABLE1# (PCIe/WiFi) and W_DISABLE2# (Bluetooth) signals. > When a signal is not routed to a host GPIO, the corresponding > enable/disable callbacks are no-ops, so the consumer cannot gate > or reset that function on its own. > > Implement the .is_controllable() callback on the "uart" and "pcie" > targets so that consumers can query this per instance (based on the > runtime presence of the W_DISABLE2#/W_DISABLE1# GPIOs) via > pwrseq_is_controllable(). > > Signed-off-by: Loic Poulain <[email protected]> Reviewed-by: Manivannan Sadhasivam <[email protected]> - Mani -- மணிவண்ணன் சதாசிவம்