mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yijie Yang <yijie.yang@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v3 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board
Date: Wed, 14 Jan 2026 10:27:16 +0800	[thread overview]
Message-ID: <3906614d-d9df-485c-963b-603e2311bc2c@oss.qualcomm.com> (raw)
In-Reply-To: <2qa3kn6gw4f5qlncq6iwgxattfbbztu42gpcbekqfghcrdg3l5@z7zsx44xch7a>



On 1/13/2026 6:52 PM, Dmitry Baryshkov wrote:
> On Tue, Jan 13, 2026 at 06:28:16PM +0800, 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.
>>
>> PURWA-IOT-EVK uses the PS8833 as a retimer for USB0, unlike HAMOA-IOT-EVK.
>> Meanwhile, USB0 bypasses the SBU selector FSUSB42. As a result, the glink
>> topology differs from that of HAMOA-IOT-EVK.
> 
> What is "glink topology"?

What I’m referring to here is that the graph composed of glink nodes and 
their peers.

> 
>>
>> Make the following peripherals on the carrier board enabled:
>> - UART
>> - On-board regulators
>> - USB Type-C mux
>> - Pinctrl
>> - Embedded USB (EUSB) repeaters
>> - NVMe
>> - pmic-glink
>> - USB DisplayPorts
>> - Bluetooth
>> - WLAN
>> - Audio
>> - PCIe ports for PCIe3 through PCIe6a
>>
>> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
>> ---
>>   arch/arm64/boot/dts/qcom/Makefile             |   1 +
>>   .../{hamoa-iot-evk.dts => purwa-iot-evk.dts}  | 102 +++++++++++-------
>>   2 files changed, 65 insertions(+), 38 deletions(-)
>>   copy arch/arm64/boot/dts/qcom/{hamoa-iot-evk.dts => purwa-iot-evk.dts} (95%)
>>
>> @@ -1102,9 +1140,7 @@ edp_bl_reg_en: edp-bl-reg-en-state {
>>   		pins = "gpio10";
>>   		function = "normal";
>>   	};
>> -};
>>   
>> -&pmc8380_3_gpios {
> 
> This needs to be fixed in hamoa-iot-evk.dtsi.

Will do.

> 
>>   	pm_sde7_aux_3p3_en: pcie-aux-3p3-default-state {
>>   		pins = "gpio8";
>>   		function = "normal";
>> @@ -1171,16 +1207,6 @@ &smb2360_2_eusb2_repeater {
>>   	vdd3-supply = <&vreg_l8b_3p0>;
>>   };
>>   
>> -&spi11 {
>> -	status = "okay";
>> -
>> -	tpm@0 {
>> -		compatible = "st,st33htpm-spi", "tcg,tpm_tis-spi";
> 
> No TPM on the board?

It has not been verified yet since this patch set was sent out; I will 
add it.

> 
>> -		reg = <0>;
>> -		spi-max-frequency = <20000000>;
>> -	};
>> -};
>> -
>>   &swr0 {
>>   	status = "okay";
>>   
>> @@ -1470,7 +1496,7 @@ &usb_1_ss0_hsphy {
>>   };
>>   
>>   &usb_1_ss0_qmpphy_out {
>> -	remote-endpoint = <&pmic_glink_ss0_ss_in>;
>> +	remote-endpoint = <&retimer_ss0_ss_in>;
>>   };
>>   
>>   &usb_1_ss1_dwc3_hs {
>> -- 
>> 2.34.1
>>
> 

-- 
Best Regards,
Yijie


  reply	other threads:[~2026-01-14  2:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-13 10:28 [PATCH v3 0/4] Initial patch set for PURWA-IOT-EVK YijieYang
2026-01-13 10:28 ` [PATCH v3 1/4] dt-bindings: arm: qcom: Document PURWA-IOT-EVK board YijieYang
2026-01-13 10:28 ` [PATCH v3 2/4] firmware: qcom: scm: Allow QSEECOM on PURWA-IOT-EVK YijieYang
2026-01-13 10:28 ` [PATCH v3 3/4] arm64: dts: qcom: Add PURWA-IOT-SOM platform YijieYang
2026-01-13 10:47   ` Dmitry Baryshkov
2026-01-13 11:29     ` Konrad Dybcio
2026-01-13 17:50       ` Dmitry Baryshkov
2026-01-14  1:38         ` Yijie Yang
2026-01-21 13:10       ` Vikash Garodia
2026-01-13 10:28 ` [PATCH v3 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board YijieYang
2026-01-13 10:52   ` Dmitry Baryshkov
2026-01-14  2:27     ` Yijie Yang [this message]
2026-01-14  3:14       ` Dmitry Baryshkov
2026-01-13 14:52 ` [PATCH v3 0/4] Initial patch set for PURWA-IOT-EVK Rob Herring

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=3906614d-d9df-485c-963b-603e2311bc2c@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

all inboxes | Powered by JetHome®