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 15:59:17 +0000 [thread overview]
Message-ID: <avcz1Z6OnT-c2kgQ@inferno0230.in> (raw)
In-Reply-To: <b945d65b-60a9-4437-999f-15b5f0307b5e@kernel.org>
On Fri, Nov 13, 2026 at 03:57:17PM +0100, Krzysztof Kozlowski wrote:
> On 13/11/2026 15:30, Aditya Choudhury wrote:
> > 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.
>
> As you can easily check, names in downstream are not codenames and have
> no meaning. Don't use them.
>
> >
> >>>
> >>> 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.
>
> But this does not settle the name! You only sent SoC ID, without the
> actual name. Organize your work in proper chunks, not split without
> proper reason. This only limits the view and makes review unnecessarily
> difficult.
>
Sorry about that. I sent only the SoC IDs because I had seen it done
that way in the git history, and I hoped it would also get the codename
sorted out first.
I can either send a v2 of this series with crow reworded to Camano, or
send the whole SoC bring-up with the SoC ID patches included in it.
If I send the whole bring-up, should it go out as v2 of this series, or
as a new series?
Either works for me, whichever you prefer.
> Best regards,
> Krzysztof
Best regards,
Aditya Choudhury
next prev parent reply other threads:[~2026-11-13 15:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 10:30 [PATCH 0/2] soc: qcom: " 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
2026-11-13 14:57 ` Krzysztof Kozlowski
2026-11-13 15:59 ` Aditya Choudhury [this message]
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=avcz1Z6OnT-c2kgQ@inferno0230.in \
--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
all inboxes | Powered by JetHome®