From: Yijie Yang <yijie.yang@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 3/3] arm64: dts: qcom: Add base HAMOA-IOT-EVK board
Date: Mon, 1 Sep 2025 16:00:35 +0800 [thread overview]
Message-ID: <2de9fa44-0d77-4631-9d09-32c48a93a7f6@oss.qualcomm.com> (raw)
In-Reply-To: <qgirqibqvsld7n2ac4cvuvtqknhqkq535jkxnxjjqvss5wpm36@i3mbp7qgqxju>
On 2025-08-28 19:18, Dmitry Baryshkov wrote:
> On Thu, Aug 28, 2025 at 12:48:47PM +0800, Yijie Yang wrote:
>> The HAMOA-IOT-EVK is an evaluation platform for IoT products, composed of
>> the Hamoa IoT SoM and a carrier board. Together, they form a complete
>> embedded system capable of booting to UART.
>>
>> This change enables the following peripherals on the carrier board:
>> - UART
>> - On-board regulators
>> - USB Type-C mux
>> - Pinctrl
>> - Embedded USB (EUSB) repeaters
>> - NVMe
>> - pmic-glink
>> - USB DisplayPorts
>> - Bluetooth
>> - Graphic
>> - Audio
>>
>> Written in collaboration with Quill Qi (Audio) <le.qi@oss.qualcomm.com>,
>> Jie Zhang (Graphics) <quic_jiezh@quicinc.com>, Shuai Zhang (Bluetooth)
>> <quic_shuaz@quicinc.com>, and Yongxing Mou (USB DisplayPorts)
>> <quic_yongmou@quicinc.com>.
>>
>> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
>> ---
>> arch/arm64/boot/dts/qcom/Makefile | 1 +
>> arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts | 1247 ++++++++++++++++++++++++++++
>> 2 files changed, 1248 insertions(+)
>>
>> +
>> + wcd938x: audio-codec {
>> + compatible = "qcom,wcd9385-codec";
>> +
>> + pinctrl-0 = <&wcd_default>;
>> + pinctrl-names = "default";
>> +
>> + reset-gpios = <&tlmm 191 GPIO_ACTIVE_LOW>;
>> +
>> + qcom,micbias1-microvolt = <1800000>;
>> + qcom,micbias2-microvolt = <1800000>;
>> + qcom,micbias3-microvolt = <1800000>;
>> + qcom,micbias4-microvolt = <1800000>;
>> + qcom,mbhc-buttons-vthreshold-microvolt = <75000 150000 237000 500000
>> + 500000 500000 500000 500000>;
>
> Other platforms use a single line here. If you don't want to do it,
> align data to start from the same column rather than restarting from the
> column 1.
I will update it to a single line.
>
>> + qcom,mbhc-headset-vthreshold-microvolt = <1700000>;
>> + qcom,mbhc-headphone-vthreshold-microvolt = <50000>;
>> + qcom,rx-device = <&wcd_rx>;
>> + qcom,tx-device = <&wcd_tx>;
>> +
>> + vdd-buck-supply = <&vreg_l15b_1p8>;
>> + vdd-rxtx-supply = <&vreg_l15b_1p8>;
>> + vdd-io-supply = <&vreg_l15b_1p8>;
>> + vdd-mic-bias-supply = <&vreg_bob1>;
>> +
>> + #sound-dai-cells = <1>;
>> + };
>> +
>> + wcn7850-pmu {
>> + compatible = "qcom,wcn7850-pmu";
>> +
>> + vdd-supply = <&vreg_wcn_0p95>;
>> + vddio-supply = <&vreg_l15b_1p8>;
>> + vddaon-supply = <&vreg_wcn_0p95>;
>> + vdddig-supply = <&vreg_wcn_0p95>;
>> + vddrfa1p2-supply = <&vreg_wcn_1p9>;
>> + vddrfa1p8-supply = <&vreg_wcn_1p9>;
>> +
>> + bt-enable-gpios = <&tlmm 116 GPIO_ACTIVE_HIGH>;
>
> Okay, so how is WiFi controlled? Is there a GPIO? The DT should be
> describing the hardware, not the UEFI behaviour.
>
>> +
>> + pinctrl-0 = <&wcn_bt_en>;
>> + pinctrl-names = "default";
>> +
>
--
Best Regards,
Yijie
prev parent reply other threads:[~2025-09-01 8:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 4:48 [PATCH v8 0/3] Initial support for Qualcomm Hamoa IOT EVK board Yijie Yang
2025-08-28 4:48 ` [PATCH v8 1/3] dt-bindings: arm: qcom: Document HAMOA-IOT-EVK board Yijie Yang
2025-08-28 4:48 ` [PATCH v8 2/3] arm64: dts: qcom: Add HAMOA-IOT-SOM platform Yijie Yang
2025-08-28 4:48 ` [PATCH v8 3/3] arm64: dts: qcom: Add base HAMOA-IOT-EVK board Yijie Yang
2025-08-28 11:15 ` Dmitry Baryshkov
2025-08-29 0:56 ` Yijie Yang
2025-08-28 11:18 ` Dmitry Baryshkov
2025-09-01 3:02 ` Yingying Tang
2025-09-02 2:37 ` Dmitry Baryshkov
2025-09-02 6:56 ` Yingying Tang
2025-09-02 9:50 ` Dmitry Baryshkov
2025-09-02 10:09 ` Konrad Dybcio
2025-09-01 8:00 ` Yijie Yang [this message]
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=2de9fa44-0d77-4631-9d09-32c48a93a7f6@oss.qualcomm.com \
--to=yijie.yang@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).