From: Yijie Yang <yijie.yang@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, krzysztof.kozlowski@oss.qualcomm.com
Subject: Re: [PATCH v2 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board
Date: Mon, 12 Jan 2026 11:12:09 +0800 [thread overview]
Message-ID: <3959a318-aca3-43e2-a431-4a9ae40f911f@oss.qualcomm.com> (raw)
In-Reply-To: <6e8e6583-033f-439e-bd92-b24fe432fb96@oss.qualcomm.com>
On 1/9/2026 7:29 PM, Konrad Dybcio wrote:
> On 1/9/26 8:59 AM, YijieYang wrote:
>> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>
>> The PURWA-IOT-EVK is an evaluation platform for IoT products, composed of
>> the Purwa IoT SoM and a carrier board. Together, they form a complete
>> embedded system capable of booting to UART.
>
> [...]
>
>> - backlight: backlight {
>> - compatible = "pwm-backlight";
>> - pwms = <&pmk8550_pwm 0 5000000>;
>> - enable-gpios = <&pmc8380_3_gpios 4 GPIO_ACTIVE_HIGH>;
>> - power-supply = <&vreg_edp_bl>;
>> -
>> - pinctrl-0 = <&edp_bl_en>, <&edp_bl_pwm>;
>> - pinctrl-names = "default";
>> - };
>
> Is the backlight infra different on the Purwa IoT EVK?
As you can see, this Purwa file was copied from the latest
hamoa-iot-evk.dts. However, not all nodes have been verified on Purwa.
Therefore, I need to retain only the functions that work correctly and
keep them aligned with the nodes from my initial version. The deleted
nodes will be updated later by the respective authors from different
technical areas.
>
>> -
>> wcd938x: audio-codec {
>> compatible = "qcom,wcd9385-codec";
>>
>> @@ -60,32 +50,6 @@ chosen {
>> stdout-path = "serial0:115200n8";
>> };
>>
>> - connector3 {
>> - compatible = "usb-a-connector";
>> - label = "USB-3-Type-A";
>> - power-role = "source";
>> -
>> - vbus-supply = <®ulator_usb3_vbus>;
>> -
>> - port {
>> - connector_3_in: endpoint {
>> - };
>> - };
>> - };
>> -
>> - connector6 {
>> - compatible = "usb-a-connector";
>> - label = "USB-6-Type-A";
>> - power-role = "source";
>> -
>> - vbus-supply = <®ulator_usb6_vbus>;
>> -
>> - port {
>> - connector_4_in: endpoint {
>> - };
>> - };
>> - };
>
> Are there no Type-A ports?
ditto
>
> [...]
>
>> panel {
>> compatible = "edp-panel";
>>
>> - backlight = <&backlight>;
>> + //backlight = <&backlight>;
>
> FWIW we can't merge dead code
I will update.
>
>> power-supply = <&vreg_edp_3p3>;
>>
>> port {
>> @@ -920,23 +886,6 @@ &mdss_dp3_phy {
>> status = "okay";
>> };
>>
>> -&pcie4_port0 {
>> - 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>;
>> - };
>> -};
>
> Is the Wi-Fi solution different?
ditto
>
> Konrad
--
Best Regards,
Yijie
next prev parent reply other threads:[~2026-01-12 3:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 7:59 [PATCH v2 0/4] Initial patch set for PURWA-IOT-EVK YijieYang
2026-01-09 7:59 ` [PATCH v2 1/4] dt-bindings: arm: qcom: Document PURWA-IOT-EVK board YijieYang
2026-01-09 7:59 ` [PATCH v2 2/4] firmware: qcom: scm: Allow QSEECOM on PURWA-IOT-EVK YijieYang
2026-01-09 12:48 ` Dmitry Baryshkov
2026-01-09 7:59 ` [PATCH v2 3/4] arm64: dts: qcom: Add PURWA-IOT-SOM platform YijieYang
2026-01-09 12:10 ` Dmitry Baryshkov
2026-01-12 3:02 ` Yijie Yang
2026-01-09 7:59 ` [PATCH v2 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board YijieYang
2026-01-09 11:29 ` Konrad Dybcio
2026-01-12 3:12 ` Yijie Yang [this message]
2026-01-12 5:00 ` Dmitry Baryshkov
2026-01-12 5:51 ` Yijie Yang
2026-01-12 6:01 ` Dmitry Baryshkov
2026-01-12 10:54 ` Konrad Dybcio
2026-01-13 1:45 ` Yijie Yang
2026-01-12 7:14 ` Krzysztof Kozlowski
2026-01-09 8:06 ` [PATCH v2 0/4] Initial patch set for PURWA-IOT-EVK Krzysztof Kozlowski
2026-01-09 8:26 ` Yijie Yang
2026-01-09 9:04 ` Krzysztof Kozlowski
2026-01-09 9:28 ` Konrad Dybcio
2026-01-12 3:13 ` Yijie Yang
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=3959a318-aca3-43e2-a431-4a9ae40f911f@oss.qualcomm.com \
--to=yijie.yang@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--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
all inboxes | Powered by JetHome®