AM64x SoCs have two ESM modules, with one in MAIN voltage domain and the
other in MCU voltage domain. The error output from Main ESM module can
be routed to the MCU ESM module. The error output of MCU ESM can be
configured to reset the device.

For ESM details please refer technical reference manual at
https://www.ti.com/lit/pdf/spruim2

Signed-off-by: Hari Nagalla <hnagalla@ti.com>
---
 arch/arm64/boot/dts/ti/k3-am64.dtsi | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/arm64/boot/dts/ti/k3-am64.dtsi b/arch/arm64/boot/dts/ti/k3-am64.dtsi
index 120974726be8..0622a93ec136 100644
--- a/arch/arm64/boot/dts/ti/k3-am64.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am64.dtsi
@@ -66,6 +66,7 @@
 		#address-cells = <2>;
 		#size-cells = <2>;
 		ranges = <0x00 0x000f4000 0x00 0x000f4000 0x00 0x000002d0>, /* PINCTRL */
+			 <0x00 0x00420000 0x00 0x00420000 0x00 0x00001000>, /* ESM0 */
 			 <0x00 0x00600000 0x00 0x00600000 0x00 0x00001100>, /* GPIO */
 			 <0x00 0x00a40000 0x00 0x00a40000 0x00 0x00000800>, /* Timesync router */
 			 <0x00 0x01000000 0x00 0x01000000 0x00 0x02330400>, /* First peripheral window */
-- 
2.17.1

Please loop in LAKML as stated in MAINTAINERS file.

On 12:21-20220208, Hari Nagalla wrote:
> AM64x SoCs have two ESM modules, with one in MAIN voltage domain and the
> other in MCU voltage domain. The error output from Main ESM module can
> be routed to the MCU ESM module. The error output of MCU ESM can be
> configured to reset the device.

So what happens to the window for MCU ESM - Is that already open?

> 
> For ESM details please refer technical reference manual at
> https://www.ti.com/lit/pdf/spruim2
> 
> Signed-off-by: Hari Nagalla <hnagalla@ti.com>
> ---
>  arch/arm64/boot/dts/ti/k3-am64.dtsi | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm64/boot/dts/ti/k3-am64.dtsi b/arch/arm64/boot/dts/ti/k3-am64.dtsi
> index 120974726be8..0622a93ec136 100644
> --- a/arch/arm64/boot/dts/ti/k3-am64.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am64.dtsi
> @@ -66,6 +66,7 @@
>  		#address-cells = <2>;
>  		#size-cells = <2>;
>  		ranges = <0x00 0x000f4000 0x00 0x000f4000 0x00 0x000002d0>, /* PINCTRL */
> +			 <0x00 0x00420000 0x00 0x00420000 0x00 0x00001000>, /* ESM0 */
>  			 <0x00 0x00600000 0x00 0x00600000 0x00 0x00001100>, /* GPIO */
>  			 <0x00 0x00a40000 0x00 0x00a40000 0x00 0x00000800>, /* Timesync router */
>  			 <0x00 0x01000000 0x00 0x01000000 0x00 0x02330400>, /* First peripheral window */
> -- 
> 2.17.1
> 

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

On 2/8/22 18:35, Nishanth Menon wrote:
>> AM64x SoCs have two ESM modules, with one in MAIN voltage domain and the
>> other in MCU voltage domain. The error output from Main ESM module can
>> be routed to the MCU ESM module. The error output of MCU ESM can be
>> configured to reset the device.
> So what happens to the window for MCU ESM - Is that already open?
> 
Yes, the cbass mcu window already opens MCU ESM address space.

I will loop in LAKML as well..

Thanks

On 19:18-20220208, Hari Nagalla wrote:
> On 2/8/22 18:35, Nishanth Menon wrote:
> > > AM64x SoCs have two ESM modules, with one in MAIN voltage domain and the
> > > other in MCU voltage domain. The error output from Main ESM module can
> > > be routed to the MCU ESM module. The error output of MCU ESM can be
> > > configured to reset the device.
> > So what happens to the window for MCU ESM - Is that already open?
> > 
> Yes, the cbass mcu window already opens MCU ESM address space.

Please add that in the comments to making sure there is no confusion.

> 
> I will loop in LAKML as well..

Thanks.
-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D