All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suman Anna <s-anna@ti.com>
To: Santosh Shilimkar <ssantosh@kernel.org>,
	Rob Herring <robh+dt@kernel.org>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
	Lokesh Vutla <lokeshvutla@ti.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, Suman Anna <s-anna@ti.com>
Subject: [PATCH 0/2] Add AM64x SoC support to PRUSS platform driver
Date: Wed, 23 Jun 2021 11:50:30 -0500	[thread overview]
Message-ID: <20210623165032.31223-1-s-anna@ti.com> (raw)

Hi Santosh,

The following series adds the base support for the ICSSG IP on AM64x SoCs.
Patches are on top of v5.13-rc1 + minor fix that Jan had posted [1].

The ICSSG IP on AM64x is a minor revised version that looks almost same as
the version used on J721E. There is no SGMII support on AM64x SoCs, but
otherwise they have the same 2 PRUs, 2 RTUS and 2 Tx_PRUs just like J721E
and AM65x SR2.0 SoCs.

The CFG sub-module is the only sub-module that has a different revision
version w.r.t J721E. J721E and AM65x differed in CFG, ECC Aggregator,
RAT Slices. ECAP, INTC, MDIO and UART0 are all identical. There are no
revision registers on IEP0/IEP1, MII_RT, MII_G_RT, PROTECT or TASK Manager
modules, and these look to be identical from a quick register comparision
from TRM. There are no SGMII registers at all. IEP, MII_RT and MII_G_RT
are also syscon nodes, so any differences would have to be dealt
within the client drivers.

regards,
Suman

[1] https://patchwork.kernel.org/project/linux-arm-kernel/patch/d6e24953-ea89-fd1c-6e16-7a0142118054@siemens.com/

Suman Anna (2):
  dt-bindings: soc: ti: pruss: Update bindings for K3 AM64x SoCs
  soc: ti: pruss: Enable support for ICSSG subsystems on K3 AM64x SoCs

 Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml | 6 ++++--
 drivers/soc/ti/pruss.c                                 | 1 +
 2 files changed, 5 insertions(+), 2 deletions(-)

-- 
2.30.1


WARNING: multiple messages have this Message-ID (diff)
From: Suman Anna <s-anna@ti.com>
To: Santosh Shilimkar <ssantosh@kernel.org>,
	Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org,
	Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Lokesh Vutla <lokeshvutla@ti.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Kishon Vijay Abraham I <kishon@ti.com>,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Add AM64x SoC support to PRUSS platform driver
Date: Wed, 23 Jun 2021 11:50:30 -0500	[thread overview]
Message-ID: <20210623165032.31223-1-s-anna@ti.com> (raw)

Hi Santosh,

The following series adds the base support for the ICSSG IP on AM64x SoCs.
Patches are on top of v5.13-rc1 + minor fix that Jan had posted [1].

The ICSSG IP on AM64x is a minor revised version that looks almost same as
the version used on J721E. There is no SGMII support on AM64x SoCs, but
otherwise they have the same 2 PRUs, 2 RTUS and 2 Tx_PRUs just like J721E
and AM65x SR2.0 SoCs.

The CFG sub-module is the only sub-module that has a different revision
version w.r.t J721E. J721E and AM65x differed in CFG, ECC Aggregator,
RAT Slices. ECAP, INTC, MDIO and UART0 are all identical. There are no
revision registers on IEP0/IEP1, MII_RT, MII_G_RT, PROTECT or TASK Manager
modules, and these look to be identical from a quick register comparision
from TRM. There are no SGMII registers at all. IEP, MII_RT and MII_G_RT
are also syscon nodes, so any differences would have to be dealt
within the client drivers.

regards,
Suman

[1] https://patchwork.kernel.org/project/linux-arm-kernel/patch/d6e24953-ea89-fd1c-6e16-7a0142118054@siemens.com/

Suman Anna (2):
  dt-bindings: soc: ti: pruss: Update bindings for K3 AM64x SoCs
  soc: ti: pruss: Enable support for ICSSG subsystems on K3 AM64x SoCs

 Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml | 6 ++++--
 drivers/soc/ti/pruss.c                                 | 1 +
 2 files changed, 5 insertions(+), 2 deletions(-)

-- 
2.30.1


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

             reply	other threads:[~2021-06-23 16:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-23 16:50 Suman Anna [this message]
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 16:50   ` Suman Anna
2021-06-23 17:48   ` Grygorii Strashko
2021-06-23 17:48     ` Grygorii Strashko
2021-07-14 19:16   ` Rob Herring
2021-07-14 19:16     ` Rob Herring
2021-06-23 16:50 ` [PATCH 2/2] soc: ti: pruss: Enable support for ICSSG subsystems on " Suman Anna
2021-06-23 16:50   ` Suman Anna
2021-06-23 17:48   ` Grygorii Strashko
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=20210623165032.31223-1-s-anna@ti.com \
    --to=s-anna@ti.com \
    --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=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 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.