linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Suman Anna <s-anna@ti.com>
Cc: Santosh Shilimkar <ssantosh@kernel.org>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	devicetree@vger.kernel.org, Lokesh Vutla <lokeshvutla@ti.com>,
	Rob Herring <robh+dt@kernel.org>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	linux-arm-kernel@lists.infradead.org,
	Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>,
	Kishon Vijay Abraham I <kishon@ti.com>
Subject: Re: [PATCH 1/2] dt-bindings: soc: ti: pruss: Update bindings for K3 AM64x SoCs
Date: Wed, 14 Jul 2021 13:16:15 -0600	[thread overview]
Message-ID: <20210714191615.GA2994029@robh.at.kernel.org> (raw)
In-Reply-To: <20210623165032.31223-2-s-anna@ti.com>

On Wed, 23 Jun 2021 11:50:31 -0500, Suman Anna wrote:
> The K3 AM64x SoCs also have the Gigabit Ethernet capable PRU-ICSS IP
> that is present on existing K3 AM65x and J721E SoCs (ICSSG). The IP
> is similar to the ones used on K3 J721E or AM65x SR2.0 SoCs.
> 
> Update the PRUSS bindings for these ICSSG instances.
> 
> Signed-off-by: Suman Anna <s-anna@ti.com>
> ---
>  Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 

Acked-by: Rob Herring <robh@kernel.org>

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2021-07-14 19:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-23 16:50 [PATCH 0/2] Add AM64x SoC support to PRUSS platform driver Suman Anna
2021-06-23 16:50 ` [PATCH 1/2] dt-bindings: soc: ti: pruss: Update bindings for K3 AM64x SoCs Suman Anna
2021-06-23 17:48   ` Grygorii Strashko
2021-07-14 19:16   ` Rob Herring [this message]
2021-06-23 16:50 ` [PATCH 2/2] soc: ti: pruss: Enable support for ICSSG subsystems on " Suman Anna
2021-06-23 17:48   ` Grygorii Strashko

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=20210714191615.GA2994029@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=grzegorz.jaszczyk@linaro.org \
    --cc=jan.kiszka@siemens.com \
    --cc=kishon@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lokeshvutla@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=s-anna@ti.com \
    --cc=ssantosh@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).