From: Krzysztof Kozlowski <krzk@kernel.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
david@ixit.cz, 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>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: arm: qcom,ids: Add SoC ID for Snapdragon SDA 850
Date: Wed, 24 Jun 2026 09:37:37 +0200 [thread overview]
Message-ID: <9b089e83-56a2-465f-a364-a1e8bad20540@kernel.org> (raw)
In-Reply-To: <90f9f8a8-971d-4cb7-b2a0-248349b329d4@oss.qualcomm.com>
On 24/06/2026 09:35, Konrad Dybcio wrote:
> On 6/24/26 8:26 AM, Krzysztof Kozlowski wrote:
>> On 23/06/2026 20:41, David Heidelberg via B4 Relay wrote:
>>> From: David Heidelberg <david@ixit.cz>
>>>
>>> Add SoC ID for Qualcomm Snapdragon SDA850.
>>>
>>> Signed-off-by: David Heidelberg <david@ixit.cz>
>>> ---
>>> Will be used by Comma three.
>>
>> Can you provide a link?
>
> Previous gen of https://comma.ai/shop/comma-four, they don't seem
> to have the old one listed on their website anymore
I meant, link to the upstream user. Something which will convince why do
we want this patch.
>
> The other computer tells me SDA850 doesn't exist and 348 is SDM850
> (for which we have a number of DTs in the kernel today), so let's
> rename it and add a second patch to add it to socinfo
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-06-24 7:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 18:41 [PATCH] dt-bindings: arm: qcom,ids: Add SoC ID for Snapdragon SDA 850 David Heidelberg via B4 Relay
2026-06-23 18:48 ` sashiko-bot
2026-06-24 6:26 ` Krzysztof Kozlowski
2026-06-24 7:35 ` Konrad Dybcio
2026-06-24 7:37 ` Krzysztof Kozlowski [this message]
2026-06-24 11:37 ` David Heidelberg
2026-06-24 7:02 ` Mukesh Ojha
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=9b089e83-56a2-465f-a364-a1e8bad20540@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@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 \
/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