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@xxxxxxxxxx/ [5] https://patchwork.kernel.org/project/linux-remoteproc/cover/20201216165239.2744-1-grzegorz.jaszczyk@xxxxxxxxxx/ [6] https://patchwork.kernel.org/project/linux-remoteproc/cover/20201211184811.6490-1-grzegorz.jaszczyk@xxxxxxxxxx/ 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