Add devicetree bindings for Variscite VAR-SOM-AM62P System on Module
and its carrier boards.

Signed-off-by: Stefano Radaelli <stefano.radaelli21@gmail.com>
---
v2:
 - Add symphony carrier board compatible

 Documentation/devicetree/bindings/arm/ti/k3.yaml | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/Documentation/devicetree/bindings/arm/ti/k3.yaml b/Documentation/devicetree/bindings/arm/ti/k3.yaml
index bf6003d8fb76..780fbb5970a5 100644
--- a/Documentation/devicetree/bindings/arm/ti/k3.yaml
+++ b/Documentation/devicetree/bindings/arm/ti/k3.yaml
@@ -100,6 +100,12 @@ properties:
           - const: toradex,verdin-am62p          # Verdin AM62P Module
           - const: ti,am62p5
 
+      - description: K3 AM62P5 SoC Variscite SOM and Carrier Boards
+        items:
+          - const: variscite,am62p-var-som-symphony
+          - const: variscite,am62p-var-som
+          - const: ti,am62p5
+
       - description: K3 AM642 SoC
         items:
           - enum:
-- 
2.43.0

On 10/07/2025 00:07, Stefano Radaelli wrote:
> Add devicetree bindings for Variscite VAR-SOM-AM62P System on Module
> and its carrier boards.
> 
> Signed-off-by: Stefano Radaelli <stefano.radaelli21@gmail.com>
> ---
> v2:
>  - Add symphony carrier board compatible
> 
>  Documentation/devicetree/bindings/arm/ti/k3.yaml | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/arm/ti/k3.yaml b/Documentation/devicetree/bindings/arm/ti/k3.yaml
> index bf6003d8fb76..780fbb5970a5 100644
> --- a/Documentation/devicetree/bindings/arm/ti/k3.yaml
> +++ b/Documentation/devicetree/bindings/arm/ti/k3.yaml
> @@ -100,6 +100,12 @@ properties:
>            - const: toradex,verdin-am62p          # Verdin AM62P Module
>            - const: ti,am62p5
>  
> +      - description: K3 AM62P5 SoC Variscite SOM and Carrier Boards
> +        items:
> +          - const: variscite,am62p-var-som-symphony

This is named reversed. Usually Variscite names are var-som-foo and:
https://www.variscite.com/product/system-on-module-som/cortex-a53-krait/var-som-am62p-ti-sitara-am62px/

confirms this, so the compatibles should be var-som-am62p.



Best regards,
Krzysztof

Hi Krzysztof,

Thank you for your suggestion. Actually, our compatible strings for
Variscite SOMs follow the format "som-factor"-"processor". Here are
some examples:

https://github.com/varigit/linux-imx/blob/lf-6.6.y_6.6.52-2.2.0_var01/arch/arm64/boot/dts/freescale/imx93-var-som.dtsi#L14
https://github.com/varigit/linux-imx/blob/lf-6.6.y_6.6.52-2.2.0_var01/arch/arm64/boot/dts/freescale/imx8mp-var-som.dtsi#L15
https://github.com/varigit/linux-imx/blob/lf-6.6.y_6.6.52-2.2.0_var01/arch/arm64/boot/dts/freescale/imx91-var-som.dtsi#L14

These strings are used in our Yocto filesystem for WiFi management and
other applications. Changing them would require updating the entire
Yocto configuration.

Best regards,
Stefano

Il giorno gio 10 lug 2025 alle ore 08:50 Krzysztof Kozlowski
<krzk@kernel.org> ha scritto:
>
> On 10/07/2025 00:07, Stefano Radaelli wrote:
> > Add devicetree bindings for Variscite VAR-SOM-AM62P System on Module
> > and its carrier boards.
> >
> > Signed-off-by: Stefano Radaelli <stefano.radaelli21@gmail.com>
> > ---
> > v2:
> >  - Add symphony carrier board compatible
> >
> >  Documentation/devicetree/bindings/arm/ti/k3.yaml | 6 ++++++
> >  1 file changed, 6 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/arm/ti/k3.yaml b/Documentation/devicetree/bindings/arm/ti/k3.yaml
> > index bf6003d8fb76..780fbb5970a5 100644
> > --- a/Documentation/devicetree/bindings/arm/ti/k3.yaml
> > +++ b/Documentation/devicetree/bindings/arm/ti/k3.yaml
> > @@ -100,6 +100,12 @@ properties:
> >            - const: toradex,verdin-am62p          # Verdin AM62P Module
> >            - const: ti,am62p5
> >
> > +      - description: K3 AM62P5 SoC Variscite SOM and Carrier Boards
> > +        items:
> > +          - const: variscite,am62p-var-som-symphony
>
> This is named reversed. Usually Variscite names are var-som-foo and:
> https://www.variscite.com/product/system-on-module-som/cortex-a53-krait/var-som-am62p-ti-sitara-am62px/
>
> confirms this, so the compatibles should be var-som-am62p.
>
>
>
> Best regards,
> Krzysztof

On 10/07/2025 11:21, Stefano Radaelli wrote:
> Hi Krzysztof,
> 
> Thank you for your suggestion. Actually, our compatible strings for
> Variscite SOMs follow the format "som-factor"-"processor". Here are
> some examples:

Then why do you define it reversed here? How this som-factor-processor
is an argument to my request to use som-factor-processor?

> 
> https://github.com/varigit/linux-imx/blob/lf-6.6.y_6.6.52-2.2.0_var01/arch/arm64/boot/dts/freescale/imx93-var-som.dtsi#L14
> https://github.com/varigit/linux-imx/blob/lf-6.6.y_6.6.52-2.2.0_var01/arch/arm64/boot/dts/freescale/imx8mp-var-som.dtsi#L15
> https://github.com/varigit/linux-imx/blob/lf-6.6.y_6.6.52-2.2.0_var01/arch/arm64/boot/dts/freescale/imx91-var-som.dtsi#L14
> 
> These strings are used in our Yocto filesystem for WiFi management and
> other applications. Changing them would require updating the entire

I did not ask about these. We talk here about this compatible.

I asked to reply with mailing list style already. Why are you still
top-posting? It makes the discussion difficult.

https://people.kernel.org/tglx/notes-about-netiquette

Best regards,
Krzysztof

> Then why do you define it reversed here? How this som-factor-processor
> is an argument to my request to use som-factor-processor?

I apologize for the confusion in my previous email. I made an error in
my explanation - our compatible strings actually follow the format
"processor"-"som-factor", not "som-factor"-"processor" as I
incorrectly stated. That's why our compatible string is
"variscite,am62p-var-som" (processor-som-factor), consistent with the
examples I provided of Variscite kernel like
"variscite,imx93-var-som", "variscite,imx8mp-var-som", and
"variscite,imx91-var-som".

>
> I asked to reply with mailing list style already. Why are you still
> top-posting? It makes the discussion difficult.
>
> https://people.kernel.org/tglx/notes-about-netiquette
>

I apologize for the top-posting. I didn't realize I was doing it and
will ensure to follow proper mailing list etiquette going forward.

Best Regards,
Stefano

On 10/07/2025 15:53, Stefano Radaelli wrote:
>> Then why do you define it reversed here? How this som-factor-processor
>> is an argument to my request to use som-factor-processor?
> 
> I apologize for the confusion in my previous email. I made an error in
> my explanation - our compatible strings actually follow the format
> "processor"-"som-factor", not "som-factor"-"processor" as I
> incorrectly stated. That's why our compatible string is
> "variscite,am62p-var-som" (processor-som-factor), consistent with the
> examples I provided of Variscite kernel like
> "variscite,imx93-var-som", "variscite,imx8mp-var-som", and
> "variscite,imx91-var-som".

There are no such compatibles. There are:

variscite,var-som-mx93
variscite,var-som-mx8mn

and others with exact format how I asked - var-som-<processor>.

Best regards,
Krzysztof

On 10/07/2025 16:42, Krzysztof Kozlowski wrote:
> There are no such compatibles. There are:
>
> variscite,var-som-mx93
> variscite,var-som-mx8mn
>
> and others with exact format how I asked - var-som-<processor>.
>

You are absolutely correct, and I apologize for the confusion.
I was incorrectly referring to our internal kernel tree instead of
checking the mainline kernel compatibles.

Thank you for your patience in correcting me.
I will follow your advice and use the proper mainline format
"var-som-<processor>" for consistency with the existing Variscite compatibles
already present in mainline, rather than our internal naming convention.

I will update the patch accordingly.

Best regards,
Stefano