The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Aditya Choudhury <mail@inferno0230.in>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Abel Vesa <abelvesa@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 1/2] dt-bindings: arm: qcom,ids: Add SoC ID for SM7550
Date: Fri, 13 Nov 2026 14:30:00 +0000	[thread overview]
Message-ID: <avce6OKgtVIi15tR@mediaserver> (raw)
In-Reply-To: <20261113-ambitious-solemn-narwhal-cbaeec@quoll>

On Fri, Nov 13, 2026 at 12:17:35PM +0100, Krzysztof Kozlowski wrote:
> On Thu, Nov 12, 2026 at 10:30:26AM +0000, Aditya Choudhury wrote:
> > Add the ID for the Qualcomm SM7550 SoC, whose internal codename is crow.
> 
> >From where did you get internal codename? Downstream does not use the
> proper codenames.
> 
crow is the codename used in downstream sources. I assumed it was the
internal codename since SM7550 is publicly known as Snapdragon 7 Gen 3.
I was also unsure about this because SM7635 uses milos upstream instead
of volcano downstream.

> > 
> > Signed-off-by: Aditya Choudhury <mail@inferno0230.in>
> > ---
> >  include/dt-bindings/arm/qcom,ids.h | 1 +
> >  1 file changed, 1 insertion(+)
> 
> Where is any user of this? Why do we need such SoC patches separate from
> the actual new SoC?
> 
I sent these patches first because I expected a possible codename
change, just like what happened with SM7635. I wanted to settle the name
before sending the actual SoC support patches, so it wouldn't need to
be changed everywhere later.

There will be follow-up patches to add SM7550 support and support for
the OnePlus Nord CE 4, which is based on SM7550.

> Best regards,
> Krzysztof
> 

Best regards,
Aditya Choudhury


  reply	other threads:[~2026-11-13 14:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12 10:30 [PATCH 0/2] soc: qcom: Add SoC ID for SM7550 Aditya Choudhury
2026-11-12 10:30 ` [PATCH 1/2] dt-bindings: arm: qcom,ids: " Aditya Choudhury
2026-11-13  8:13   ` Konrad Dybcio
2026-11-13 11:17   ` Krzysztof Kozlowski
2026-11-13 14:30     ` Aditya Choudhury [this message]
2026-11-13 14:57       ` Krzysztof Kozlowski
2026-11-13 15:59         ` Aditya Choudhury
2026-11-12 10:30 ` [PATCH 2/2] soc: qcom: socinfo: " Aditya Choudhury
2026-11-13 11:17   ` Krzysztof Kozlowski
2026-11-13  8:12 ` [PATCH 0/2] soc: qcom: " Konrad Dybcio
2026-11-13 14:36   ` Aditya Choudhury
2026-11-13 14:42     ` Konrad Dybcio

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=avce6OKgtVIi15tR@mediaserver \
    --to=mail@inferno0230.in \
    --cc=abelvesa@kernel.org \
    --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 \
    /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