From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Yijie Yang <yijie.yang@oss.qualcomm.com>,
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 0/4] Initial patch set for PURWA-IOT-EVK
Date: Tue, 23 Dec 2025 18:27:05 +0100 [thread overview]
Message-ID: <0593cc2e-0114-404f-929a-0860d60afefb@oss.qualcomm.com> (raw)
In-Reply-To: <d8642ba4-9a6f-4fb2-bd0c-419ead2630d3@oss.qualcomm.com>
On 12/23/25 3:12 AM, Yijie Yang wrote:
>
>
> On 12/22/2025 5:18 PM, Dmitry Baryshkov wrote:
>> On Mon, Dec 22, 2025 at 02:03:25PM +0800, YijieYang wrote:
>>> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>>
>>> Introduce the device tree, DT bindings, and driver modifications required
>>> to bring up the PURWA-IOT-EVK evaluation board.
>>>
>>> Purwa and Hamoa are IoT variants of x1p42100 and x1e80100, both based on
>>> the IQ-X SoC series. Consequently, the two common files in this series are
>>> prefixed with 'iq-x-iot' to reflect this relationship.
>>>
>>> PURWA-IOT-EVK shares almost the same hardware design with HAMOA-IOT-EVK,
>>> except for differences in the BOM. As a result, most of the DTS can be
>>> shared between them.
>>>
>>> The changes focus on two key hardware components: the PURWA-IOT-SOM and
>>> the PURWA-IOT-EVK carrier board.
>>>
>>> Hardware delta between Hamoa and Purwa:
>>> - Display: Purwa’s display uses a different number of clocks, and its
>>> frequency differs from Hamoa.
>>> - GPU: Purwa requires a separate firmware compared to Hamoa.
>>
>> Is it just a separate firmware, or does it use a different _GPU_?
>
> It uses a different GPU.
I think it would be useful to call this paragraph "Hardware delta between
Hamoa-IoT-SoM/EVK and Purwa-IoT-whatever - because now Dmitry is asking
about differences between Hamoa-the-SoC and Purwa-the-SoC which we
expressed in purwa.dtsi
Konrad
>
>>
>>> - USB0: Purwa uses a PS8833 retimer, while Hamoa uses an FSUSB42 as the
>>> SBU switch.
>>>
>>
>
next prev parent reply other threads:[~2025-12-23 17:27 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 6:03 [PATCH 0/4] Initial patch set for PURWA-IOT-EVK YijieYang
2025-12-22 6:03 ` [PATCH 1/4] firmware: qcom: scm: Allow QSEECOM on PURWA-IOT-EVK YijieYang
2025-12-22 9:11 ` Krzysztof Kozlowski
2025-12-23 1:48 ` Yijie Yang
2025-12-22 6:03 ` [PATCH 2/4] dt-bindings: arm: qcom: Document PURWA-IOT-EVK board YijieYang
2025-12-22 9:10 ` Krzysztof Kozlowski
2025-12-22 6:03 ` [PATCH 3/4] arm64: dts: qcom: Commonize IQ-X-IOT DTSI YijieYang
2025-12-22 9:11 ` Krzysztof Kozlowski
2025-12-23 2:00 ` Yijie Yang
2025-12-23 13:42 ` Krzysztof Kozlowski
2025-12-24 2:27 ` Yijie Yang
2025-12-23 3:38 ` Tingwei Zhang
2025-12-23 13:41 ` Krzysztof Kozlowski
2025-12-24 0:12 ` Tingwei Zhang
2025-12-29 1:23 ` Tingwei Zhang
2025-12-29 7:21 ` Krzysztof Kozlowski
2025-12-29 7:38 ` Yijie Yang
2025-12-29 8:47 ` Krzysztof Kozlowski
2025-12-29 20:08 ` Dmitry Baryshkov
2025-12-30 7:21 ` Krzysztof Kozlowski
2026-01-05 5:36 ` Tingwei Zhang
2026-01-05 15:09 ` Krzysztof Kozlowski
2026-01-06 1:24 ` Tingwei Zhang
2026-01-06 1:47 ` Dmitry Baryshkov
2026-01-06 3:05 ` Tingwei Zhang
2026-01-06 3:26 ` Dmitry Baryshkov
2026-01-06 8:14 ` Tingwei Zhang
2026-01-06 4:11 ` Bjorn Andersson
2025-12-29 10:19 ` Tingwei Zhang
2025-12-29 11:27 ` Konrad Dybcio
2025-12-30 0:48 ` Tingwei Zhang
2025-12-22 6:03 ` [PATCH 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board YijieYang
2025-12-22 9:22 ` Dmitry Baryshkov
2025-12-23 2:02 ` Yijie Yang
2025-12-23 19:08 ` Dmitry Baryshkov
2025-12-22 9:18 ` [PATCH 0/4] Initial patch set for PURWA-IOT-EVK Dmitry Baryshkov
2025-12-23 2:12 ` Yijie Yang
2025-12-23 17:27 ` Konrad Dybcio [this message]
2025-12-23 19:09 ` Dmitry Baryshkov
2025-12-24 2:03 ` Yijie Yang
2025-12-24 2:02 ` Yijie Yang
2025-12-29 12:18 ` Konrad Dybcio
2025-12-30 2:51 ` 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=0593cc2e-0114-404f-929a-0860d60afefb@oss.qualcomm.com \
--to=konrad.dybcio@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 \
--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