Re: [PATCH v4 4/4] arm64: dts: qcom: purwa-iot-evk: Describe the PCIe M.2 Key E connector
Konrad Dybcio <[email protected]>
| Newsgroups | org.kernel.vger.linux-devicetree,org.kernel.vger.linux-arm-msm,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On 8/4/26 2:32 PM, Wei Deng wrote: > The Purwa IoT EVK has a PCIe M.2 Mechanical Key E connector for wireless > connectivity cards exposing Wi-Fi over PCIe and Bluetooth over UART. > Purwa inherits hamoa.dtsi via purwa.dtsi and therefore reuses the PCIe > root port compatible and the uart14_ep / pcie4_port0_ep endpoint stub > labels added there. > > Describe the connector node with: > - port@0: PCIe for Wi-Fi, linked to pcie4_port0 > - port@3: UART for Bluetooth, linked to uart14 > > This allows the pwrseq-pcie-m2 driver to manage card power and > dynamically create the UART serdev for UART BT variants of the M.2 > card. > > Remove the chip-specific wcn7850-pmu node, the static bluetooth > serdev under uart14, and the wifi@0 PCI child node, as the M.2 > connector approach replaces WCN7850-specific power sequencing with > a chip-agnostic model. > > Also remove the now-unused vreg_wcn_0p95 and vreg_wcn_1p9 dummy > fixed regulators whose only consumers were the wcn7850-pmu node. > > Signed-off-by: Wei Deng <[email protected]> > --- Reviewed-by: Konrad Dybcio <[email protected]> Konrad