diff --git a/source/linux/Foundational_Components/Power_Management/pm_low_power_modes.rst b/source/linux/Foundational_Components/Power_Management/pm_low_power_modes.rst index f45927f1..21500d30 100644 --- a/source/linux/Foundational_Components/Power_Management/pm_low_power_modes.rst +++ b/source/linux/Foundational_Components/Power_Management/pm_low_power_modes.rst @@ -238,7 +238,7 @@ sources is found to be enabled, Partial I/O is entered instead of poweroff. The following wakeup sources have been configured for Partial I/O: mcu_uart0, mcu_mcan0, and mcu_mcan1. Partial I/O mode can only be tested -when `k3-am62x-sk-lpm-wkup-sources.dtso `__ +when `k3-am62x-sk-lpm-wkup-sources.dtso `__ overlay is loaded. Please refer to :ref:`How to enable DT overlays` for more details. After Linux boots, the MCAN wakeup for Partial I/O is enabled using the diff --git a/source/linux/Foundational_Components/Power_Management/pm_sw_arch.rst b/source/linux/Foundational_Components/Power_Management/pm_sw_arch.rst index 9a39efca..08d94497 100644 --- a/source/linux/Foundational_Components/Power_Management/pm_sw_arch.rst +++ b/source/linux/Foundational_Components/Power_Management/pm_sw_arch.rst @@ -151,8 +151,8 @@ Specifically, checking of constraints is done at two levels: The code enabling the constraints framework can be found in: -#. TISCI PM Domain driver: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/drivers/pmdomain/ti/ti_sci_pm_domains.c?h=10.00.07 -#. TISCI driver: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/drivers/pmdomain/ti/ti_sci_pm_domains.c?h=10.00.07 +#. TISCI PM Domain driver: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/drivers/pmdomain/ti/ti_sci_pm_domains.c?h=10.01.10 +#. TISCI driver: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/drivers/firmware/ti_sci.c?h=10.01.10 Examples of adding constraints from the remote core side are being implemented and will be enabled in future release. @@ -198,7 +198,7 @@ The various modes and their latencies are documented here: https://downloads.ti. If a device wants to put a constraint to not be powered-off, it can use the Linux QoS framework and set the ``DEV_PM_QOS_RESUME_LATENCY`` equal to 0. An example is shown in the following RemoteProc driver: -https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/drivers/remoteproc/ti_k3_r5_remoteproc.c?h=10.00.07#n535 +https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/drivers/remoteproc/ti_k3_r5_remoteproc.c?h=10.01.10#n523 .. note:: diff --git a/source/linux/Foundational_Components/Power_Management/pm_wakeup_sources.rst b/source/linux/Foundational_Components/Power_Management/pm_wakeup_sources.rst index 859ed34c..9d5bf6fb 100644 --- a/source/linux/Foundational_Components/Power_Management/pm_wakeup_sources.rst +++ b/source/linux/Foundational_Components/Power_Management/pm_wakeup_sources.rst @@ -179,7 +179,7 @@ by configuring the MCU GPIO controller as a wakeup source. In ideal scenarios, the firmware running on MCU core is responsible for configuring MCU GPIO's as a wakeup source. However, if the application design doesn't rely too much on the MCU firmware then Linux can be used to configure the MCU GPIOs as a wakeup source. You can refer to the mcu_gpio_key node in -`k3-am62x-sk-lpm-wkup-sources.dtso `__ +`k3-am62x-sk-lpm-wkup-sources.dtso `__ and use it as a template to configure the MCU GPIO of your choice as a wakeup capable GPIO. A brief guide to configuring an MCU GPIO as wakeup: @@ -238,7 +238,7 @@ source and send a wakeup interrupt to the Device Manager. To understand the role please refer to :ref:`S/W Architecture of System Suspend` MCU GPIO wakeup can only be tested when -`k3-am62x-sk-lpm-wkup-sources.dtso `__ +`k3-am62x-sk-lpm-wkup-sources.dtso `__ overlay is loaded. Please refer to :ref:`How to enable DT overlays` for more details. Once the system has entered Deep Sleep or MCU Only mode as shown in the @@ -281,7 +281,7 @@ Main UART ========= The way to configure UART as an I/O daisy chain wakeup, refer to the -main_uart0 node in `k3-am62x-sk-common.dtsi `_ +main_uart0 node in `k3-am62x-sk-common.dtsi `_ .. code-block:: dts @@ -344,10 +344,10 @@ configuration and working of these frameworks have been covered under the MCU GPIO and Main UART sections. The reference configuration for Main GPIO wakeup can be found under -gpio_key node in `k3-am62x-sk-lpm-wkup-sources.dtso `__ +gpio_key node in `k3-am62x-sk-lpm-wkup-sources.dtso `__ Main GPIO wakeup can only be tested when -`k3-am62x-sk-lpm-wkup-sources.dtso `__ +`k3-am62x-sk-lpm-wkup-sources.dtso `__ overlay is loaded. Please refer to :ref:`How to enable DT overlays` for more details. To use main_gpio as a wakeup source, ensure gpio is a wake-irq in /proc/interrupts: @@ -371,7 +371,7 @@ Sleep and MCU Only modes. In order to use WKUP UART as a wakeup source, it needs to be configured in a generic way using the ti-sysc interconnect target module driver. The reference configuration can be found under target-module in -`k3-am62-wakeup.dtsi `__ +`k3-am62-wakeup.dtsi `__ WKUP UART is generally available on the third serial port (/dev/ttyUSB2) and by default it only shows output from DM R5.