Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:7 as permitted sender) client-ip=2620:137:e000::3:7;
Date:   Tue, 12 Dec 2023 09:42:38 -0600
From:   Nishanth Menon <nm@ti.com>
To:     Andrew Davis <afd@ti.com>
CC:     Vaishnav Achath <vaishnav.a@ti.com>, <ssantosh@kernel.org>,
        <linux-kernel@vger.kernel.org>,
        <linux-arm-kernel@lists.infradead.org>, <vigneshr@ti.com>,
        <u-kumar1@ti.com>, <j-choudhary@ti.com>
Subject: Re: [PATCH] soc: ti: k3-socinfo: Add JTAG ID for J722S
Message-ID: <20231212154238.3sn5fxpestaqacrc@defog>
References: <20231211132600.25289-1-vaishnav.a@ti.com>
 <81f90d13-da10-4a68-a0e7-95212f40b3e8@ti.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <81f90d13-da10-4a68-a0e7-95212f40b3e8@ti.com>
Precedence: bulk

On 09:19-20231212, Andrew Davis wrote:
> On 12/11/23 7:26 AM, Vaishnav Achath wrote:
> > Add JTAG ID info for the J722S SoC family to enable SoC detection.
> > 
> > More details about this SoC can be found in the TRM:
> > 	https://www.ti.com/lit/zip/sprujb3
> > 
> > Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>
> > ---
> 
> Simple enough,
> 
> Reviewed-by: Andrew Davis <afd@ti.com>
> 
> Although I do question our use of the J7x names. All of our parts here
> also have a "Sitara AMxx" branding. For instance here we could call
> this new device by its "AM67" name, then J784S4 renamed as AM69, etc.
> Then we would have a consistent naming (internally we will have to deal
> with the part name madness, but why expose that externally if we don't
> have to).

J722S is a new die and the core part, what rebranding/spins happens to it is
subject to mktg group, not going to hold this series with that.

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D