RE: [PATCH v3 1/6] dt-binding: ARM: samsung: Add Samsung Exynos8855
From: Alim Akhtar
Date: Mon Jul 06 2026 - 07:43:12 EST
> -----Original Message-----
> From: Ivaylo Ivanov <ivo.ivanov.ivanov1@xxxxxxxxx>
> Sent: Monday, July 6, 2026 1:27 PM
> To: Alim Akhtar <alim.akhtar@xxxxxxxxxxx>; krzk@xxxxxxxxxx;
> peter.griffin@xxxxxxxxxx; robh@xxxxxxxxxx; conor+dt@xxxxxxxxxx;
> linusw@xxxxxxxxxx
> Cc: linux-samsung-soc@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx;
> devicetree@xxxxxxxxxxxxxxx; linux-gpio@xxxxxxxxxxxxxxx;
> hajun.sung@xxxxxxxxxxx
> Subject: Re: [PATCH v3 1/6] dt-binding: ARM: samsung: Add Samsung
> Exynos8855
>
> On 7/6/26 6:44 AM, Alim Akhtar wrote:
> > Hi Ivaylo,
> > Thanks for your review.
>
> No problem :D
>
> >
> >> -----Original Message-----
> >> From: Ivaylo Ivanov <ivo.ivanov.ivanov1@xxxxxxxxx>
> >> Sent: Monday, July 6, 2026 4:11 AM
> >> To: Alim Akhtar <alim.akhtar@xxxxxxxxxxx>; krzk@xxxxxxxxxx;
> >> peter.griffin@xxxxxxxxxx; robh@xxxxxxxxxx; conor+dt@xxxxxxxxxx;
> >> linusw@xxxxxxxxxx
> >> Cc: linux-samsung-soc@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx;
> >> devicetree@xxxxxxxxxxxxxxx; linux-gpio@xxxxxxxxxxxxxxx;
> >> hajun.sung@xxxxxxxxxxx
> >> Subject: Re: [PATCH v3 1/6] dt-binding: ARM: samsung: Add Samsung
> >> Exynos8855
> >>
> >> On 6/27/26 20:12, Alim Akhtar wrote:
> >>> Add Samsung Exynos8855 smdk board to documentation
> >>>
> >>> Signed-off-by: Alim Akhtar <alim.akhtar@xxxxxxxxxxx>
> >>> ---
> >>> .../devicetree/bindings/arm/samsung/samsung-boards.yaml | 6 ++++++
> >>> 1 file changed, 6 insertions(+)
> >>>
> >>> diff --git
> >>> a/Documentation/devicetree/bindings/arm/samsung/samsung-boards.yaml
> >>> b/Documentation/devicetree/bindings/arm/samsung/samsung-boards.yaml
> >>> index 753b3ba1b607..273464400477 100644
> >>> ---
> >>> a/Documentation/devicetree/bindings/arm/samsung/samsung-boards.yaml
> >>> +++ b/Documentation/devicetree/bindings/arm/samsung/samsung-
> >> boards.yam
> >>> +++ l
> >>> @@ -235,6 +235,12 @@ properties:
> >>> - winlink,e850-96 # WinLink E850-96
> >>> - const: samsung,exynos850
> >>>
> >>> + - description: Exynos8855 based boards
> >>> + items:
> >>> + - enum:
> >>> + - samsung,exynos8855-smdk # Samsung SMDK
> >>> + - const: samsung,exynos8855
> >>
> >> Is there any particular reason for using "exynos8855" rather than the
> >> commercial name - exynos1580? We've already established using the
> >> latter naming scheme as a convention (e.g. exynos3830 -> exynos850,
> >> exynos9830 ->
> >> exynos990) rather than the development model numbers, so I don't
> >> think breaking that will help anyone with the already painful model number
> confusion.
> >>
> > The reason for using Exynos8855 is that it comes from the chip-id register,
> which is RO register.
> > And in my opinion it has to be chip-id, maintaining two names is confusing (as
> you also mentioned).
>
> I see your point but I'm not sure whether exynos-based platforms like tensors
> will follow this. Afaik GS101's development name is e9845. So there likely will
> still be some deviation.
>
Hmm...I would say, those are custom SoCs (of course based on Exynos as base platform) and they don’t carry "Exynos"
in their nomenclature, like GS101, or Artpec and many more...
However Exynos8855 and other SoCs in this family are native Exynos SoCs.
So for Exynos SoCs (exception 850, 990), let's have chip-id based nomenclature as a standard, that's what I am thinking, it is easy to maintain that way.
> It's not really a fatal thing, just a nit imo because all bindings will have to follow
> that for the upstreamed SoC, so non-revertable. But if maintainers are okay with
> this, I'm happy to start using chip-id names for future contributions too.
>
Thank you, Looking forward for more contributions, no need to revert what is merged already.
> Best regards,
> Ivaylo
>
> > Yes, there were couple of deviation but let's come back to the "original"
> convention (which is to use chip-id).
> >
> > @ Krzysztof, Peter
> > Any input on this?
> >
> >> Best regards,
> >> Ivaylo
> >>
> >>> +
> >>> - description: Exynos8895 based boards
> >>> items:
> >>> - enum:
> >
> >