From: Suman Anna <s-anna@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: devicetree@vger.kernel.org,
Grygorii Strashko <grygorii.strashko@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Lokesh Vutla <lokeshvutla@ti.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/11] Add PRU-ICSS nodes on AM335x, AM437x & AM57xx SoCs
Date: Thu, 29 Jul 2021 17:46:10 -0500 [thread overview]
Message-ID: <20210729224621.2295-1-s-anna@ti.com> (raw)
Hi Tony,
The following series adds the DT nodes for the Programmable Real-Time
Unit and Industrial Communication Subsystems (PRU-ICSS or simply PRUSS)
present on certain AM335x, AM437x and all AM57xx SoCs. For details, please
refer to the respective Technical Reference Manuals [1][2][3] or the cover
letter from the first foundation PRUSS platform driver [4]. The next-gen
ICSSG nodes were already mainlined for K3 AM65x and J721E SoCs.
The sub-system is represented through multiple platform device nodes
which are supported through a corresponding platform driver, like the
PRUSS platform driver, PRUSS irqchip driver and a PRU remoteproc driver
(upstreamed in 5.10, 5.11 kernels). This series adds the foundation PRUSS
nodes, that can in turn be referenced and used by PRU client/application
drivers. The client bindings and driver changes were posted previously
and need a refresh [5][6], but won't affect these nodes.
The PRU-ICSS is not supported on every device in the AM335x and AM437x
SoC family. It is only supported on AM3356+ and AM4376+ SoCs. All AM57xx
SoCs (but not DRA7xx SoCs) support PRU-ICSS. I have taken slightly different
approaches in the patches for each of the SoC families:
- AM57xx PRU-ICSS target modules are already cleanly separated in
am57-pruss.dtsi, so the nodes are directly added in enabled state.
- AM437x PRUSS nodes are directly added and enabled in the am4372.dtsi,
as all the existing AM437x board dts files use AM4376+ SoCs.
- AM335x PRUSS nodes are also added in the common am33xx-l4.dtsi file,
and the parent ti-sysc target-module is enabled only in the required
board dts files. There are about 35 different AM335x board dts files,
with many of them using AM3352. I couldn't identify exactly what SoC
version is being used for some of them, so the PRU-ICSS nodes are
enabled only on known TI boards.
- MDIO nodes are currently disabled, they will be enabled after the PRU
Ethernet driver is upstreamed.
Patches are on top of 5.14-rc3 (should apply cleanly on 5.14-rc1 as
well), as I had to use that version due to some Ethernet issues for NFS.
Let me know if you prefer the AM57 style of a separate dtsi file for
PRUSS, and I can repost these quickly.
regards
Suman
[1] AM335x TRM Rev.Q: https://www.ti.com/lit/pdf/spruh73
[2] AM437x TRM Rev.I: https://www.ti.com/lit/pdf/spruhl7
[3] AM571x TRM Rev.I: https://www.ti.com/lit/pdf/spruhz7
[4] https://patchwork.kernel.org/project/linux-arm-kernel/cover/1596020528-19510-1-git-send-email-grzegorz.jaszczyk@linaro.org/
[5] https://patchwork.kernel.org/project/linux-remoteproc/cover/20201216165239.2744-1-grzegorz.jaszczyk@linaro.org/
[6] https://patchwork.kernel.org/project/linux-remoteproc/cover/20201211184811.6490-1-grzegorz.jaszczyk@linaro.org/
Andrew F. Davis (1):
ARM: dts: am4372: Add PRUSS MDIO controller node
Suman Anna (10):
ARM: dts: am33xx-l4: Add PRUSS node
ARM: dts: am33xx-l4: Add PRUSS MDIO controller node
ARM: dts: am335x-bone-common: Enable PRU-ICSS node
ARM: dts: am335x-evm: Enable PRU-ICSS module
ARM: dts: am335x-evmsk: Enable PRU-ICSS module
ARM: dts: am335x-icev2: Enable PRU-ICSS module
ARM: dts: am4372: Add the PRU-ICSS1 DT node
ARM: dts: am4372: Add the PRU-ICSS0 DT node
ARM: dts: am57xx: Add PRU-ICSS nodes
ARM: dts: am57xx: Add PRUSS MDIO controller nodes
arch/arm/boot/dts/am335x-bone-common.dtsi | 4 +
arch/arm/boot/dts/am335x-evm.dts | 4 +
arch/arm/boot/dts/am335x-evmsk.dts | 4 +
arch/arm/boot/dts/am335x-icev2.dts | 4 +
arch/arm/boot/dts/am33xx-l4.dtsi | 82 ++++++++
arch/arm/boot/dts/am4372.dtsi | 165 ++++++++++++++++
arch/arm/boot/dts/am437x-cm-t43.dts | 4 +
arch/arm/boot/dts/am437x-gp-evm.dts | 4 +
arch/arm/boot/dts/am437x-idk-evm.dts | 4 +
arch/arm/boot/dts/am437x-sk-evm.dts | 4 +
arch/arm/boot/dts/am43x-epos-evm.dts | 4 +
arch/arm/boot/dts/am57-pruss.dtsi | 178 +++++++++++++++++-
arch/arm/boot/dts/am571x-idk.dts | 8 +
arch/arm/boot/dts/am572x-idk.dts | 8 +
arch/arm/boot/dts/am574x-idk.dts | 8 +
.../boot/dts/am57xx-beagle-x15-common.dtsi | 8 +
arch/arm/boot/dts/am57xx-cl-som-am57x.dts | 8 +
17 files changed, 500 insertions(+), 1 deletion(-)
--
2.32.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-07-29 22:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 22:46 Suman Anna [this message]
2021-07-29 22:46 ` [PATCH 01/11] ARM: dts: am33xx-l4: Add PRUSS node Suman Anna
2021-07-29 22:46 ` [PATCH 02/11] ARM: dts: am33xx-l4: Add PRUSS MDIO controller node Suman Anna
2021-07-29 22:46 ` [PATCH 03/11] ARM: dts: am335x-bone-common: Enable PRU-ICSS node Suman Anna
2021-07-29 22:46 ` [PATCH 04/11] ARM: dts: am335x-evm: Enable PRU-ICSS module Suman Anna
2021-07-29 22:46 ` [PATCH 05/11] ARM: dts: am335x-evmsk: " Suman Anna
2021-07-29 22:46 ` [PATCH 06/11] ARM: dts: am335x-icev2: " Suman Anna
2021-07-29 22:46 ` [PATCH 07/11] ARM: dts: am4372: Add the PRU-ICSS1 DT node Suman Anna
2021-07-29 22:46 ` [PATCH 08/11] ARM: dts: am4372: Add the PRU-ICSS0 " Suman Anna
2021-07-29 22:46 ` [PATCH 09/11] ARM: dts: am4372: Add PRUSS MDIO controller node Suman Anna
2021-07-29 22:46 ` [PATCH 10/11] ARM: dts: am57xx: Add PRU-ICSS nodes Suman Anna
2021-07-29 22:46 ` [PATCH 11/11] ARM: dts: am57xx: Add PRUSS MDIO controller nodes Suman Anna
2021-08-03 12:53 ` [PATCH 00/11] Add PRU-ICSS nodes on AM335x, AM437x & AM57xx SoCs Tony Lindgren
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=20210729224621.2295-1-s-anna@ti.com \
--to=s-anna@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).