From: Krzysztof Kozlowski <krzk@kernel.org>
To: Abel Vesa <abel.vesa@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: arm: qcom: Document Eliza CQM and CQS EVK boards
Date: Sat, 16 May 2026 12:30:41 +0200 [thread overview]
Message-ID: <daa10a6e-7122-4133-9040-2a5de204283e@kernel.org> (raw)
In-Reply-To: <mxgc3iogd2z5m44xffvqc23cdg4mregw73vslujcdr3ff5hyvi@zqgseqplhoey>
On 16/05/2026 12:27, Abel Vesa wrote:
> On 26-05-16 11:58:56, Krzysztof Kozlowski wrote:
>> On Fri, May 15, 2026 at 02:13:31PM +0300, Abel Vesa wrote:
>>> Document the compatible strings for the Qualcomm Eliza CQM and CQS EVK
>>> boards. Both boards are built from a base board paired with a SoM which
>>> is populated with either CQ7790M or CQ7790S (Eliza variants), PMICs,
>>> LPDDR, eMMC and UFS.
>>>
>>> Signed-off-by: Abel Vesa <abel.vesa@oss.qualcomm.com>
>>> ---
>>> Documentation/devicetree/bindings/arm/qcom.yaml | 2 ++
>>> 1 file changed, 2 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
>>> index 2741c07e9f41..28a18254b4b7 100644
>>> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
>>> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
>>> @@ -63,6 +63,8 @@ properties:
>>>
>>> - items:
>>> - enum:
>>> + - qcom,eliza-cqm-evk
>>> + - qcom,eliza-cqs-evk
>>
>> When we talked privately, I asked to mirror Shikra approach. But you did
>> not - it's different from what Shikra sent.
>
> Because I think it is wrong to describe the SoM since it can't be used
> without a base board. Listing SoMs is useless, IMO. But maybe I'm wrong.
>
> So my reason for doing this is basically reducing the list to only
> describe entire setups: MTP, CQM EVK and CQS EVK. No SoMs.
That's really unique statement. All or most of other vendors, including
the most popular for SoMs - NXP, use it. But of course existing practice
is not the sole reason.
The reason is that it is the same useful as having SoC compatible. You
cannot use SoC without base board, then why do you have SoC compatible?
To allow quirks for the SoC. And here to allow quirks for the SoM, since
it is a dedicated and specific hardware component.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-05-16 10:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 11:13 Abel Vesa
2026-05-16 9:58 ` Krzysztof Kozlowski
2026-05-16 10:27 ` Abel Vesa
2026-05-16 10:30 ` Krzysztof Kozlowski [this message]
2026-05-16 11:15 ` Abel Vesa
2026-05-16 9:59 ` Krzysztof Kozlowski
2026-05-16 10:34 ` Abel Vesa
2026-05-16 10:37 ` Krzysztof Kozlowski
2026-05-16 11:12 ` Abel Vesa
2026-05-16 11:22 ` Krzysztof Kozlowski
2026-05-16 11:33 ` Abel Vesa
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=daa10a6e-7122-4133-9040-2a5de204283e@kernel.org \
--to=krzk@kernel.org \
--cc=abel.vesa@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=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®