Re: [PATCH v2 6/6] arm64: dts: qcom: rb3gen2: add Industrial BT UART overlay
Konrad Dybcio <[email protected]> Fri, 31 Jul 2026 14:50:09 +0200
| 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 | <[email protected]> |
On 7/31/26 8:53 AM, Rahul Samana wrote: > > > On 29-07-2026 18:01, Konrad Dybcio wrote: >> On 7/27/26 5:45 PM, Rahul Samana wrote: >>> The reworked RB3 Gen 2 Industrial mezzanine keeps the common Industrial >>> mezzanine hardware description but routes QCC2072 Bluetooth over UART4 >>> instead of the default Bluetooth-over-USB path. >>> >>> Build this variant by applying the common Industrial mezzanine overlay >>> first, followed by the BT UART overlay. The overlay models the M.2 E-key >>> connector graph endpoints for PCIe and UART, and disables the on-board >>> WCN6750 PMU and UART7 path so the M.2 QCC2072 Bluetooth controller can be >>> used instead. >> >> So is the onboard module disabled? Can we not just use two in parallel? >> > > The Industrial mezzanine variants do not support the on-board WCN6750 > wireless path. The common Industrial mezzanine overlay already disables > the on-board Wi-Fi node. What does 'do not support' it mean here? They are physically present as part of the SoM, so unless the lanes are somehow diverted away, why is it not? Konrad