All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
Cc: Conor Dooley <conor@kernel.org>, Nishanth Menon <nm@ti.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Tero Kristo <kristo@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Kees Cook <kees@kernel.org>, Tony Luck <tony.luck@intel.com>,
	"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
	Felipe Balbi <balbi@kernel.org>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	linux-hardening@vger.kernel.org,
	Devarsh Thakkar <devarsht@ti.com>, Hari Nagalla <hnagalla@ti.com>,
	linux@ew.tq-group.com
Subject: Re: [PATCH 2/5] dt-bindings: arm: ti: Add compatible for AM625-based TQMa62xx SOM family and carrier board
Date: Mon, 11 Nov 2024 15:23:49 -0600	[thread overview]
Message-ID: <20241111212349.GA1955710-robh@kernel.org> (raw)
In-Reply-To: <068c22af19c07a7c79bb4abb0366a2505b4b1aae.camel@ew.tq-group.com>

On Mon, Nov 11, 2024 at 10:58:57AM +0100, Matthias Schiffer wrote:
> On Wed, 2024-11-06 at 16:40 +0000, Conor Dooley wrote:
> > On Wed, Nov 06, 2024 at 01:03:08PM +0100, Matthias Schiffer wrote:
> > > On Tue, 2024-11-05 at 18:55 +0000, Conor Dooley wrote:
> > > > On Tue, Nov 05, 2024 at 11:40:20AM +0100, Matthias Schiffer wrote:
> > > > > On Mon, 2024-11-04 at 18:47 +0000, Conor Dooley wrote:
> > > > > > On Mon, Nov 04, 2024 at 10:47:25AM +0100, Matthias Schiffer wrote:
> > > > > > > The TQMa62xx is a SoM family with a pluggable connector. The MBa62xx is
> > > > > > > the matching reference/starterkit carrier board.
> > > > > > 
> > > > > > Why all the wildcards? Why isn't there a compatible per device in the
> > > > > > family?
> > > 
> > > Because all variants use the same Device Tree. There is also only one compatible and one (main) DTSI
> > > for the AM62 SoC family, which our Device Trees are based on.
> > 
> > So what varies between the members of the family?
> 
> There are currently 6 SoCs in the family:
> - AM6254
> - AM6252
> - AM6251
> - AM6234
> - AM6232
> - AM6231
> 
> They differ in:
> - Existence of GPU (AM625 vs AM623)
> - Number of Cortex-A53 cores (last digit)
>  
> All of these use ti,am625 as their SoC-level compatible. The differences are currently handled by U-
> Boot, which checks various feature flags in the SoC registers and patches the OS DTB accordingly by
> removing CPU nodes and disabling the GPU node if necessary.

That's how it should be. Most likely, those are all the same die. 
Different die are expensive and it takes a high volume to justify the 
cost.

Rob


  reply	other threads:[~2024-11-11 23:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-04  9:47 [PATCH 0/5] TQ-Systems TQMa62xx SoM and MBa62xx board Matthias Schiffer
2024-11-04  9:47 ` [PATCH 1/5] dt-bindings: usb: dwc3: Allow connector in USB controller node Matthias Schiffer
2024-11-04 18:47   ` Conor Dooley
2024-11-04  9:47 ` [PATCH 2/5] dt-bindings: arm: ti: Add compatible for AM625-based TQMa62xx SOM family and carrier board Matthias Schiffer
2024-11-04 18:47   ` Conor Dooley
2024-11-05 10:40     ` Matthias Schiffer
2024-11-05 18:55       ` Conor Dooley
2024-11-06 12:03         ` Matthias Schiffer
2024-11-06 16:40           ` Conor Dooley
2024-11-11  9:58             ` Matthias Schiffer
2024-11-11 21:23               ` Rob Herring [this message]
2024-11-11 21:24   ` Rob Herring (Arm)
2024-11-04  9:47 ` [PATCH 3/5] arm64: dts: ti: k3-am62: Add DM R5 ranges in cbass Matthias Schiffer
2024-11-04  9:47 ` [PATCH 4/5] arm64: dts: ti: k3-am62-wakeup: Add R5F device node Matthias Schiffer
2024-11-04  9:47 ` [PATCH 5/5] arm64: dts: ti: Add TQ-Systems TQMa62xx SoM and MBa62xx carrier board Device Trees Matthias Schiffer
2024-11-04 14:39 ` [PATCH 0/5] TQ-Systems TQMa62xx SoM and MBa62xx board Rob Herring (Arm)

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=20241111212349.GA1955710-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=balbi@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devarsht@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gpiccoli@igalia.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hnagalla@ti.com \
    --cc=kees@kernel.org \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@ew.tq-group.com \
    --cc=matthias.schiffer@ew.tq-group.com \
    --cc=nm@ti.com \
    --cc=tony.luck@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.