From: Tingwei Zhang <tingwei.zhang@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
YijieYang <yijie.yang@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 3/4] arm64: dts: qcom: Commonize IQ-X-IOT DTSI
Date: Mon, 29 Dec 2025 09:23:32 +0800 [thread overview]
Message-ID: <4f79d090-7d1c-4fb3-a835-a7e4ff96f79c@oss.qualcomm.com> (raw)
In-Reply-To: <8bcf058f-5bf9-46ce-a188-e94954101f2f@oss.qualcomm.com>
On 12/24/2025 8:12 AM, Tingwei Zhang wrote:
>
> On 12/23/2025 9:41 PM, Krzysztof Kozlowski wrote:
>> On 23/12/2025 04:38, Tingwei Zhang wrote:
>>> On 12/22/2025 5:11 PM, Krzysztof Kozlowski wrote:
>>>> On Mon, Dec 22, 2025 at 02:03:28PM +0800, YijieYang wrote:
>>>>> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>>>>
>>>>> HAMOA-IOT-EVK and PURWA-IOT-EVK share a similar board design. Extract
>>>>> the common components into separate files for better maintainability.
>>>> SoMs do not share actual hardware. DTSI does not represent what looks
>>>> similar to you, but actually common parts.
>>> Purwa SOM board and Hamoa SOM board share same design. They share same PCB.
>>> The difference is only on chip. Purwa SOM board has Purwa and Hamoa SOM board
>>> has Hamoa on it.
>> I do not speak about boards. Read carefully feedback and respond to the
>> actual feedback, not some other arguments.
>>
>> NAK
> In this change, the SoM hardware except SoC is described by iq-x-iot-som.dtsi since it's common between Hamoa and Purwa. Hamoa and Purwa SoC hardware is described in hamoa.dtsi and purwa.dtsi. Hamoa-iot-som.dtsi includes iq-x-iot-som.dtsi and hamoa.dtsi. This change could reduce the duplicate code and review effort on a totally new purwa-iot-som.dtsi. If we found any bug, it can be fixed in one common file instead of two separate files. Same idea is used in x1-crd.dtsi. X1e80100-crd.dts include x1-crd.dtsi and hamoa.dtsi.
Krzysztof,
Please let me know your opinion on this. This could be a common case for
Hamoa/Purwa boards share same PCB. Share same dtsi file like x1-crd.dtsi
would reduce maintenance effort.
>> Best regards,
>> Krzysztof
next prev parent reply other threads:[~2025-12-29 1:23 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 [this message]
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
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=4f79d090-7d1c-4fb3-a835-a7e4ff96f79c@oss.qualcomm.com \
--to=tingwei.zhang@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@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