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:37:03 +0200 [thread overview]
Message-ID: <d946b45b-cef0-43a2-b31c-a3860836745e@kernel.org> (raw)
In-Reply-To: <if7u76ecucdpjff7v5a5nryb3oiyouofn4ldpu6dmfweg5tjmh@gxdvexjrazvh>
On 16/05/2026 12:34, Abel Vesa wrote:
> On 26-05-16 11:59:37, 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(+)
>>
>> Heh, I noticed only after sending email - where is any user of that?
>>
>> I expressed it many times - we do not take bindings without users.
>
> Well, my intention for the DT patchset was to include the eliza-cqm-som.dtsi
> and eliza-cqm-ek.dts as well, basically having the eliza-cqm-som.dtsi
> include the eliza-cqs-som.dtsi and later on add the modem (and the rest
> of the CQM) in there.
>
> But then, I realized that I don't know exactly the differences between
> CQM and CQS, specifically the SoM related ones.
>
> So I decided to send without the CQM entirely.
But it is not about CQM. There is no user of any of these - neither CQS
nor CQM.
And still whatever intention you had, it cannot bypass the rules - we do
not take bindings without users. They make almost no sense to the
project, because the goal is not to document entire world's hardware in
the DT.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-05-16 10:37 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
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 [this message]
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=d946b45b-cef0-43a2-b31c-a3860836745e@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®