mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	YijieYang <yijie.yang@oss.qualcomm.com>,
	Vikash Garodia <vikash.garodia@oss.qualcomm.com>,
	Dikshita Agarwal <dikshita.agarwal@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 3/4] arm64: dts: qcom: Add PURWA-IOT-SOM platform
Date: Tue, 13 Jan 2026 12:29:43 +0100	[thread overview]
Message-ID: <7050d5e6-ddcc-4ccf-99b6-0888318c5d7f@oss.qualcomm.com> (raw)
In-Reply-To: <nfhjbfqflsrye7hqbtgwr5hwkwdtq5z4tbvnta7lk7p7jtvhl4@zbttn6coc7br>

On 1/13/26 11:47 AM, Dmitry Baryshkov wrote:
> On Tue, Jan 13, 2026 at 06:28:15PM +0800, YijieYang wrote:
>> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>
>> The PURWA-IOT-SOM is a compact computing module that integrates a System
>> on Chip (SoC) — specifically the x1p42100 — along with essential
>> components optimized for IoT applications. It is designed to be mounted on
>> carrier boards, enabling the development of complete embedded systems.
>>
>> Make the following peripherals on the SOM enabled:
>> - Regulators on the SOM
>> - Reserved memory regions
>> - PCIe3, PCIe4, PCIe5, PCIe6a
>> - USB0 through USB6 and their PHYs
>> - ADSP, CDSP
>> - Graphic
>>
>> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
>> ---
>>  .../qcom/{hamoa-iot-som.dtsi => purwa-iot-som.dtsi}   | 11 +++++------
>>  1 file changed, 5 insertions(+), 6 deletions(-)
>>  copy arch/arm64/boot/dts/qcom/{hamoa-iot-som.dtsi => purwa-iot-som.dtsi} (99%)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/hamoa-iot-som.dtsi b/arch/arm64/boot/dts/qcom/purwa-iot-som.dtsi
>> similarity index 99%
>> copy from arch/arm64/boot/dts/qcom/hamoa-iot-som.dtsi
>> copy to arch/arm64/boot/dts/qcom/purwa-iot-som.dtsi
>> index b8e3e04a6fbd..fb90beb1096f 100644
>> --- a/arch/arm64/boot/dts/qcom/hamoa-iot-som.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/purwa-iot-som.dtsi
>> @@ -3,11 +3,14 @@
>>   * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
>>   */
>>  
>> -#include "hamoa.dtsi"
>> +#include "purwa.dtsi"
>>  #include "hamoa-pmics.dtsi"
>>  #include <dt-bindings/gpio/gpio.h>
>>  #include <dt-bindings/regulator/qcom,rpmh-regulator.h>
>>  
>> +/delete-node/ &pmc8380_6;
>> +/delete-node/ &pmc8380_6_thermal;
>> +
>>  / {
>>  	reserved-memory {
>>  		linux,cma {
>> @@ -378,16 +381,12 @@ vreg_l3j_0p8: ldo3 {
>>  	};
>>  };
>>  
>> -&iris {
>> -	status = "okay";
>> -};
> 
> Why?

Purwa has a slightly different Iris hw version (8.1.2 on Hamoa, 8.1.11 on Purwa)
which I would assume is slighly weaker, plus there's probably a freqtbl change

Let's take this as-is and enable it later

+Vikash, Dikshita this seems like a really low-hanging fruit, could you take
a look at Purwa support in Iris?

Konrad

  reply	other threads:[~2026-01-13 11:29 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 [this message]
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
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=7050d5e6-ddcc-4ccf-99b6-0888318c5d7f@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dikshita.agarwal@oss.qualcomm.com \
    --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 \
    --cc=vikash.garodia@oss.qualcomm.com \
    --cc=yijie.yang@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

all inboxes | Powered by JetHome®