On Feb 12, 2025 at 15:52:48 -0600, Kendall Willis wrote:
> From: Vibhore Vardhan <vibhore@xxxxxx>
>
> Similar to the TI K3-AM62x Soc commit ce27f7f9e328c8582a169f97f1466976561f1
> ("arm64: dts: ti: k3-am62-wakeup: Configure ti-sysc for wkup_uart0")
> The devices in the wkup domain are capable of waking up the system from
> suspend. We can configure the wkup domain devices in a generic way using
> the ti-sysc interconnect target module driver like we have done with the
> earlier TI SoCs.
>
> As ti-sysc manages the SYSCONFIG related registers independent of the
> child hardware device, the wake-up configuration is also set even if
> wkup_uart0 is reserved by sysfw.
>
> The wkup_uart0 device has interconnect target module register mapping like
> dra7 wkup uart. There is a 1 MB interconnect target range with one uart IP
> block in the target module. The power domain and clock affects the whole
> interconnect target module.
>
> Note we change the functional clock name to follow the ti-sysc binding
> and use "fck" instead of "fclk".
>
> Also note that we need to disable the target module reset as noted by
> Markus. Otherwise the sysfw using wkup_uart0 can get confused on some
> devices leading to boot time issues such as mbox timeouts.
>
> Signed-off-by: Vibhore Vardhan <vibhore@xxxxxx>
> Signed-off-by: Kendall Willis <k-willis@xxxxxx>
> ---
> Tested by suspend/resume with WKUP UART wakeup source on AM62P.
>
> Similar patch was sent for AM62x by Tony,
> https://lore.kernel.org/all/20231219072503.12427-1-tony@xxxxxxxxxxx/
>
> Similar patch was sent for AM62a by Dhruva,
> https://lore.kernel.org/all/20241231-am62a-dt-ti-sysc-wkup-v1-1-a9b0d18a2649@xxxxxx/
>
> Original patch for AM62p existed in the TI Vendor tree with Vibhore's
> authorship:
> https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/?h=ti-linux-6.6.y&id=efab3fb636673837886599a49cddf1e862c8aeb6
> ---
Reviewed-by: Dhruva Gole <d-gole@xxxxxx>
--
Best regards,
Dhruva Gole
Texas Instruments Incorporated
