devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vignesh Raghavendra <vigneshr@ti.com>
To: Suman Anna <s-anna@ti.com>, Nishanth Menon <nm@ti.com>,
	Tero Kristo <kristo@kernel.org>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>,
	Lokesh Vutla <lokeshvutla@ti.com>,
	Roger Quadros <rogerq@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>
Subject: Re: [PATCH 1/2] arm64: dts: ti: k3-am65-main: Add ICSSG nodes
Date: Thu, 4 Mar 2021 13:44:15 +0530	[thread overview]
Message-ID: <d624260f-ed26-c0d6-a3a9-6c074277c62d@ti.com> (raw)
In-Reply-To: <20210114194805.8231-2-s-anna@ti.com>



On 1/15/21 1:18 AM, Suman Anna wrote:
> Add the DT nodes for the ICSSG0, ICSSG1 and ICSSG2 processor subsystems
> that are present on the K3 AM65x SoCs. The three ICSSGs are identical
> to each other for the most part, with the ICSSG2 supporting slightly
> enhanced features for supporting SGMII PRU Ethernet. Each ICSSG instance
> is represented by a PRUSS subsystem node. These nodes are enabled by
> default.
> 
[...]
> 
> Signed-off-by: Suman Anna <s-anna@ti.com>
> Signed-off-by: Roger Quadros <rogerq@ti.com>
> ---

Reviewed-by: Vignesh Raghavendra <vigneshr@ti.com>

[...]

Regards
Vignesh

  parent reply	other threads:[~2021-03-04  8:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14 19:48 [PATCH 0/2] Add ICSSG nodes on AM65x & J721E SoCs Suman Anna
2021-01-14 19:48 ` [PATCH 1/2] arm64: dts: ti: k3-am65-main: Add ICSSG nodes Suman Anna
2021-01-21 15:37   ` Nishanth Menon
2021-01-21 15:43     ` Suman Anna
2021-01-21 15:50       ` Nishanth Menon
2021-03-04  8:14   ` Vignesh Raghavendra [this message]
2021-01-14 19:48 ` [PATCH 2/2] arm64: dts: ti: k3-j721e-main: " Suman Anna
2021-01-21 15:38   ` Nishanth Menon
2021-01-21 15:43     ` Suman Anna
2021-03-04  8:27   ` Vignesh Raghavendra

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=d624260f-ed26-c0d6-a3a9-6c074277c62d@ti.com \
    --to=vigneshr@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=grzegorz.jaszczyk@linaro.org \
    --cc=jan.kiszka@siemens.com \
    --cc=kristo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lokeshvutla@ti.com \
    --cc=nm@ti.com \
    --cc=rogerq@kernel.org \
    --cc=s-anna@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;
as well as URLs for NNTP newsgroup(s).