mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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
Date: Tue, 12 Dec 2023 09:42:38 -0600	[thread overview]
Message-ID: <20231212154238.3sn5fxpestaqacrc@defog> (raw)
In-Reply-To: <81f90d13-da10-4a68-a0e7-95212f40b3e8@ti.com>

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

  reply	other threads:[~2023-12-12 15:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-11 13:26 Vaishnav Achath
2023-12-12 15:19 ` Andrew Davis
2023-12-12 15:42   ` Nishanth Menon [this message]
2023-12-12 16:16     ` Andrew Davis
2023-12-13 13:58 ` Nishanth Menon

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=20231212154238.3sn5fxpestaqacrc@defog \
    --to=nm@ti.com \
    --cc=afd@ti.com \
    --cc=j-choudhary@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ssantosh@kernel.org \
    --cc=u-kumar1@ti.com \
    --cc=vaishnav.a@ti.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

all inboxes | Powered by JetHome®