From 9d77db3c730780c8ef5ccd4b66403ff5675cfe4e Mon Sep 17 00:00:00 2001 From: hc <hc@nodka.com> Date: Mon, 13 May 2024 10:30:14 +0000 Subject: [PATCH] modify sin led gpio --- kernel/Documentation/devicetree/bindings/bus/ti-sysc.txt | 7 +++++-- 1 files changed, 5 insertions(+), 2 deletions(-) diff --git a/kernel/Documentation/devicetree/bindings/bus/ti-sysc.txt b/kernel/Documentation/devicetree/bindings/bus/ti-sysc.txt index 85a23f5..c984143 100644 --- a/kernel/Documentation/devicetree/bindings/bus/ti-sysc.txt +++ b/kernel/Documentation/devicetree/bindings/bus/ti-sysc.txt @@ -38,6 +38,7 @@ "ti,sysc-dra7-mcasp" "ti,sysc-usb-host-fs" "ti,sysc-dra7-mcan" + "ti,sysc-pruss" - reg shall have register areas implemented for the interconnect target module in question such as revision, sysc and syss @@ -94,6 +95,8 @@ - ti,no-idle-on-init interconnect target module should not be idled at init +- ti,no-idle interconnect target module should not be idled + Example: Single instance of MUSB controller on omap4 using interconnect ranges using offsets from l4_cfg second segment (0x4a000000 + 0x80000 = 0x4a0ab000): @@ -131,6 +134,6 @@ }; }; -Note that other SoCs, such as am335x can have multipe child devices. On am335x +Note that other SoCs, such as am335x can have multiple child devices. On am335x there are two MUSB instances, two USB PHY instances, and a single CPPI41 DMA -instance as children of a single interconnet target module. +instance as children of a single interconnect target module. -- Gitblit v1.6.2