From: Andrew Davis <afd@ti.com>
To: Robert Nelson <robertcnelson@gmail.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>
Cc: Rob Herring <robh@kernel.org>, Nishanth Menon <nm@ti.com>,
Jared McArthur <j-mcarthur@ti.com>,
Jason Kridner <jkridner@beagleboard.org>,
Deepak Khatri <lorforlinux@beagleboard.org>
Subject: Re: [PATCH 1/2] dt-bindings: arm: ti: Add BeagleY-AI
Date: Mon, 22 Apr 2024 15:57:10 -0500 [thread overview]
Message-ID: <1a5e719f-efa0-4c60-8add-ef7c0464d1ce@ti.com> (raw)
In-Reply-To: <20240328191205.82295-1-robertcnelson@gmail.com>
On 3/28/24 2:12 PM, Robert Nelson wrote:
> This board is based on ti,j722s
>
> https://beagley-ai.org/
> https://openbeagle.org/beagley-ai/beagley-ai
>
> Signed-off-by: Robert Nelson <robertcnelson@gmail.com>
> CC: Rob Herring <robh@kernel.org>
> CC: Nishanth Menon <nm@ti.com>
> CC: Jared McArthur <j-mcarthur@ti.com>
> CC: Jason Kridner <jkridner@beagleboard.org>
> CC: Deepak Khatri <lorforlinux@beagleboard.org>
> ---
> Documentation/devicetree/bindings/arm/ti/k3.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/ti/k3.yaml b/Documentation/devicetree/bindings/arm/ti/k3.yaml
> index 52b51fd7044e..ca23b7e6a35e 100644
> --- a/Documentation/devicetree/bindings/arm/ti/k3.yaml
> +++ b/Documentation/devicetree/bindings/arm/ti/k3.yaml
> @@ -134,6 +134,7 @@ properties:
> - description: K3 J722S SoC and Boards
> items:
> - enum:
> + - beagle,j722s-beagley-ai
Recommend "beagle,am67-beagley-ai". The "J722s" is the family
name, the part used on this board is the AM67. We do the same
for the SK boards, for example, the SK-AM69 uses the AM69
part from the J784s4 family, so it is called k3-am69-sk.dts
with compatible = "ti,am69-sk", "ti,j784s4";
This would otherwise be the first board with a specific part
attached but uses the SoC family name instead of that specific
part name in the DT file/name. Only the EVMs should have the
family name since we sell versions of those with all the different
parts swapped onto it. I don't imagine you will be selling
BeagleY's with TDA4VEN, TDA4AEN, DRA82x, etc.. All your
docs and other collateral use "AM67", using the same here
would help avoid confusion.
Andrew
> - ti,j722s-evm
> - const: ti,j722s
>
next prev parent reply other threads:[~2024-04-22 20:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 19:12 Robert Nelson
2024-03-28 19:12 ` [PATCH 2/2] arm64: dts: ti: Add k3-j722s-beagley-ai Robert Nelson
2024-03-28 19:15 ` Robert Nelson
2024-03-28 19:26 ` Jason Kridner
2024-03-28 19:37 ` Robert Nelson
2024-03-28 21:01 ` [PATCH 1/2] dt-bindings: arm: ti: Add BeagleY-AI Rob Herring
2024-04-02 13:43 ` Rob Herring
2024-04-09 19:41 ` Nishanth Menon
2024-04-22 20:57 ` Andrew Davis [this message]
2024-04-23 19:48 ` Robert Nelson
2024-04-23 20:00 ` Nishanth Menon
2024-04-23 21:44 ` Andrew Davis
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=1a5e719f-efa0-4c60-8add-ef7c0464d1ce@ti.com \
--to=afd@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=j-mcarthur@ti.com \
--cc=jkridner@beagleboard.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorforlinux@beagleboard.org \
--cc=nm@ti.com \
--cc=robertcnelson@gmail.com \
--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®