From: Krzysztof Kozlowski <krzk@kernel.org>
To: Stefano Radaelli <stefano.radaelli21@gmail.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/3] dt-bindings: arm: ti: Add bindings for Variscite VAR-SOM-AM62P
Date: Thu, 10 Jul 2025 16:42:16 +0200 [thread overview]
Message-ID: <bb6bc232-cc3e-4689-952f-88cf580604fb@kernel.org> (raw)
In-Reply-To: <CAK+owogfXDNpjT5Ywcvjaegf0H8-pS109039WadhxHXHbe3GSA@mail.gmail.com>
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
next prev parent reply other threads:[~2025-07-10 14:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 22:07 [PATCH v2 0/3] Add support for Variscite VAR-SOM-AM62P5 and Symphony board Stefano Radaelli
2025-07-09 22:07 ` [PATCH v2 1/3] dt-bindings: arm: ti: Add bindings for Variscite VAR-SOM-AM62P Stefano Radaelli
2025-07-10 6:50 ` Krzysztof Kozlowski
2025-07-10 9:21 ` Stefano Radaelli
2025-07-10 13:39 ` Krzysztof Kozlowski
2025-07-10 13:53 ` Stefano Radaelli
2025-07-10 14:42 ` Krzysztof Kozlowski [this message]
2025-07-10 14:57 ` Stefano Radaelli
2025-07-09 22:07 ` [PATCH v2 2/3] arm64: dts: ti: Add support " Stefano Radaelli
2025-07-10 6:17 ` Vignesh Raghavendra
2025-07-10 6:52 ` Krzysztof Kozlowski
2025-07-09 22:07 ` [PATCH v2 3/3] arm64: dts: ti: var-som-am62p: Add support for Variscite Symphony Board Stefano Radaelli
2025-07-10 6:27 ` Vignesh Raghavendra
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=bb6bc232-cc3e-4689-952f-88cf580604fb@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=stefano.radaelli21@gmail.com \
--cc=vigneshr@ti.com \
/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;
as well as URLs for NNTP newsgroup(s).