From: Wei Deng <wei.deng@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-pm@vger.kernel.org, mengshi.wu@oss.qualcomm.com,
quic_chezhou@quicinc.com, cheng.jiang@oss.qualcomm.com,
shuai.zhang@oss.qualcomm.com, jinwang.li@oss.qualcomm.com,
xiuzhuo.shang@oss.qualcomm.com
Subject: Re: [PATCH 1/3] arm64: dts: qcom: hamoa-iot-evk: Describe the PCIe M.2 Key E connector
Date: Mon, 13 Jul 2026 14:55:47 +0530 [thread overview]
Message-ID: <20260713092547.4100116-1-wei.deng@oss.qualcomm.com> (raw)
In-Reply-To: <63643fc3-3a3b-4aef-96b4-de42498cf47b@oss.qualcomm.com>
On Fri, 10 Jul 2026, Konrad Dybcio wrote:
> On 7/9/26 9:29 AM, Wei Deng wrote:
> > The hamoa IoT EVK has the PCIe M.2 Mechanical Key E connector to
> > connect wireless connectivity cards over PCIe and UART interfaces.
> > Hence, describe the connector node, link it with the PCIe 4 Root Port
> > node and replace the static BT serdev under UART14 and the
> > chip-specific wifi@0 child node with graph port/endpoints, allowing
> > the pwrseq-pcie-m2 driver to power the card and dynamically create
> > the BT serdev device.
> >
> > The M.2 Key E connector is powered by vreg_wcn_3p3. WLAN enable is
> > controlled via W_DISABLE1# (GPIO117) and BT enable via W_DISABLE2#
> > (GPIO116), both described as active-low GPIOs on the connector node.
> >
> > Remove the chip-specific wcn7850-pmu node as the M.2 connector
> > approach replaces the WCN7850-specific power sequencing with a
> > chip-agnostic one managed by the pwrseq-pcie-m2 driver.
> >
> > Also add 'compatible = "pciclass,0604"' to pcie4_port0 in hamoa.dtsi
> > to allow the PCI subsystem to associate the DT node with the
> > PCI-to-PCI bridge device.
> >
> > Signed-off-by: Wei Deng <wei.deng@oss.qualcomm.com>
> > ---
>
> [...]
>
> > @@ -1025,19 +1004,10 @@ &pcie4_port0 {
> > reset-gpios = <&tlmm 146 GPIO_ACTIVE_LOW>;
> > wake-gpios = <&tlmm 148 GPIO_ACTIVE_LOW>;
> >
> > - wifi@0 {
> > - compatible = "pci17cb,1107";
> > - reg = <0x10000 0x0 0x0 0x0 0x0>;
> > -
> > - vddaon-supply = <&vreg_pmu_aon_0p59>;
> > - vddwlcx-supply = <&vreg_pmu_wlcx_0p8>;
> > - vddwlmx-supply = <&vreg_pmu_wlmx_0p85>;
> > - vddrfacmn-supply = <&vreg_pmu_rfa_cmn>;
> > - vddrfa0p8-supply = <&vreg_pmu_rfa_0p8>;
> > - vddrfa1p2-supply = <&vreg_pmu_rfa_1p2>;
> > - vddrfa1p8-supply = <&vreg_pmu_rfa_1p8>;
> > - vddpcie0p9-supply = <&vreg_pmu_pcie_0p9>;
> > - vddpcie1p8-supply = <&vreg_pmu_pcie_1p8>;
> > + port {
> > + pcie4port0_ep: endpoint {
>
> "pcie4_port0_ep", please
>
> Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
>
> Konrad
>
Thanks for the review!
Will fix in v2.
--
Best Regards,
Wei Deng
next prev parent reply other threads:[~2026-07-13 9:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 7:29 [PATCH 0/3] power: sequencing: pcie-m2: Enable USB/UART BT coexistence on Hamoa EVK Wei Deng
2026-07-09 7:29 ` [PATCH 1/3] arm64: dts: qcom: hamoa-iot-evk: Describe the PCIe M.2 Key E connector Wei Deng
2026-07-09 7:42 ` sashiko-bot
2026-07-09 7:44 ` Dmitry Baryshkov
2026-07-09 8:12 ` Wei Deng
2026-07-10 13:50 ` Konrad Dybcio
2026-07-13 9:25 ` Wei Deng [this message]
2026-07-09 7:29 ` [PATCH 2/3] power: sequencing: pcie-m2: Match WCN6855 and WCN7851 UART BT variants by subdevice ID Wei Deng
2026-07-09 7:39 ` sashiko-bot
2026-07-09 7:29 ` [PATCH 3/3] power: sequencing: pcie-m2: Deassert W_DISABLE2# when no UART serdev is created Wei Deng
2026-07-09 7:44 ` sashiko-bot
2026-07-09 7:56 ` Dmitry Baryshkov
2026-07-13 9:16 ` Wei Deng
2026-07-09 7:46 ` [PATCH 0/3] power: sequencing: pcie-m2: Enable USB/UART BT coexistence on Hamoa EVK Dmitry Baryshkov
2026-07-09 8:12 ` Wei Deng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260713092547.4100116-1-wei.deng@oss.qualcomm.com \
--to=wei.deng@oss.qualcomm.com \
--cc=cheng.jiang@oss.qualcomm.com \
--cc=devicetree@vger.kernel.org \
--cc=jinwang.li@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mengshi.wu@oss.qualcomm.com \
--cc=quic_chezhou@quicinc.com \
--cc=shuai.zhang@oss.qualcomm.com \
--cc=xiuzhuo.shang@oss.qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox