Received-SPF: pass (google.com: domain of linux-kernel+bounces-155817-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Precedence: bulk
MIME-Version: 1.0
References: <20240328191205.82295-1-robertcnelson@gmail.com> <1a5e719f-efa0-4c60-8add-ef7c0464d1ce@ti.com>
In-Reply-To: <1a5e719f-efa0-4c60-8add-ef7c0464d1ce@ti.com>
From: Robert Nelson <robertcnelson@gmail.com>
Date: Tue, 23 Apr 2024 14:48:44 -0500
Message-ID: <CAOCHtYjHhH2M_+7md-e2vh_d_3H2r66OhXEp2acd0D+6O+uwcg@mail.gmail.com>
Subject: Re: [PATCH 1/2] dt-bindings: arm: ti: Add BeagleY-AI
To: Andrew Davis <afd@ti.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, 
	devicetree@vger.kernel.org, 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>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Apr 22, 2024 at 3:57=E2=80=AFPM Andrew Davis <afd@ti.com> wrote:
>
> 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/Documen=
tation/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 =3D "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

Andrew, would you like us to model this just like the AM69-SK? and
also rename the device tree? or just the bindings..

k3-j722s-beagley-ai.dtb -> k3-am67-beagley-ai.dtb or even the am67a
k3-am67a-beagley-ai.dtb ?

Regards,

--=20
Robert Nelson
https://rcn-ee.com/