public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tingwei Zhang <tingwei.zhang@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	Yijie Yang <yijie.yang@oss.qualcomm.com>,
	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: Tue, 6 Jan 2026 16:14:12 +0800	[thread overview]
Message-ID: <1f856ebc-acbf-44f3-ac16-d21baac99033@oss.qualcomm.com> (raw)
In-Reply-To: <gizxtjc2hia76qs37vl7atg5ixyk4fpr6qnwqlsajkddhxwb46@nyngnrdo5r57>



On 1/6/2026 11:26 AM, Dmitry Baryshkov wrote:
> On Tue, Jan 06, 2026 at 11:05:30AM +0800, Tingwei Zhang wrote:
>>
>> On 1/6/2026 9:47 AM, Dmitry Baryshkov wrote:
>>> On Tue, Jan 06, 2026 at 09:24:38AM +0800, Tingwei Zhang wrote:
>>>> On 1/5/2026 11:09 PM, Krzysztof Kozlowski wrote:
>>>>> On 05/01/2026 06:36, Tingwei Zhang wrote:
>>>>>> On 12/30/2025 3:21 PM, Krzysztof Kozlowski wrote:
>>>>>>> On 29/12/2025 21:08, Dmitry Baryshkov wrote:
>>>>>>>> On Mon, Dec 29, 2025 at 09:47:05AM +0100, Krzysztof Kozlowski wrote:
>>>>>>>>> On 29/12/2025 08:38, Yijie Yang wrote:
>>>>>>>>>> On 12/29/2025 3:21 PM, Krzysztof Kozlowski wrote:
>>>>>>>>>>> On 29/12/2025 02:23, Tingwei Zhang wrote:
>>>>>>>>>>>> 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:
>>>>> If this was the same SoM, just with different SoC soldered, it would
>>>>> have the same PMICs. Different PMICs means different SoM...
>>>> I agree. It's not same SoM, but they are very similar with same circuit board.
>>>>> Anyway, I shared my opinion and I am not going to spend more time on
>>>>> this. It should not be my task to go through schematics and prove that
>>>>> PMICs differ. Authors should.
>>>> We will make it more clear in the description about PMIC difference.
>>>> Since we have the agreement that Hamoa/Purwa modules are very similar,
>>>> we will use common dtsi in next version. Please let me know if you think
>>>> that's not correct thing to do.
>>> I think, you have been clearly told _not_ _to_. You have agreed that
>>> they are not the same module. So, please stop.
>>>
>> From hardware side, I think we are on same page. Hamoa and Purwa modules
>> are not same SoM, but they are very similar. The only difference is different
>> SoC, PCI, APC supply and one PMIC. The circuit boards are same.
>> We have exactly same case on Hamoa/Purwa CRD which uses a common
>> dtsi.
>> Can we use common dtsi for the hardware boards which are very similar?
>> Is that very strict that the hardware boards have to be exactly same?
> I don't have a very strict opinion about the shared DTSIs. However, I
> really want to point out: you got an review comment that it is
> unacceptable, you never got a comment that it's fine, nevertheless you
> want to ignore that review comment, coming from DT bindings maintainer.
> In 99% of the cases _ignoring_ the comment is a very wrong idea.
>
> From my PoV, asking to "Please let me know if you think that's not
> correct thing to do." after you got all the previous emails is rude.
>
I had understood that boards with very similar designs could utilize common devices
such as the Hamoa/Purwa CRD, and that we had aligned on the similarity between
the Hamoa and Purwa SoM boards. If this assumption is incorrect, please accept
my apologies.



  reply	other threads:[~2026-01-06  8:14 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 [this message]
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=1f856ebc-acbf-44f3-ac16-d21baac99033@oss.qualcomm.com \
    --to=tingwei.zhang@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=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