| Message ID | 20230711091713.1113010-3-huaqian.li@siemens.com (mailing list archive) |
|---|---|
| State | Superseded |
| Headers | show |
| Series | Add support for WDIOF_CARDRESET on TI AM65x | expand |
On 11/07/2023 11:17, huaqian.li@siemens.com wrote: > From: Li Hua Qian <huaqian.li@siemens.com> > > This patch adds a reserved memory for the TI AM65X platform watchdog to > reserve the specific info, triggering the watchdog reset in last boot, > to know if the board reboot is due to a watchdog reset. > > Signed-off-by: Li Hua Qian <huaqian.li@siemens.com> > --- > arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi | 11 +++++++++++ > 1 file changed, 11 insertions(+) > > diff --git a/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi b/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi > index e26bd988e522..77380e52a334 100644 > --- a/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi > +++ b/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi > @@ -63,6 +63,12 @@ rtos_ipc_memory_region: ipc-memories@a2000000 { > alignment = <0x1000>; > no-map; > }; > + > + /* To reserve the power-on(PON) reason for watchdog reset */ > + wdt_reset_memory_region: wdt-memory@a2200000 { > + reg = <0x00 0xa2200000 0x00 0x00001000>; > + no-map; > + }; > }; > > leds { > @@ -718,3 +724,8 @@ &mcu_r5fss0_core1 { > <&mcu_r5fss0_core1_memory_region>; > mboxes = <&mailbox0_cluster1>, <&mbox_mcu_r5fss0_core1>; > }; > + > +&mcu_rti1 { > + reg = <0x0 0x40610000 0x0 0x100>, > + <0x0 0xa2200000 0x0 0x1000>; That's a total mess. reserved memory and IO address space. Nope. Best regards, Krzysztof
On Tue, 2023-07-11 at 11:24 +0200, Krzysztof Kozlowski wrote: > On 11/07/2023 11:17, huaqian.li@siemens.com wrote: > > From: Li Hua Qian <huaqian.li@siemens.com> > > > > This patch adds a reserved memory for the TI AM65X platform > > watchdog to > > reserve the specific info, triggering the watchdog reset in last > > boot, > > to know if the board reboot is due to a watchdog reset. > > > > Signed-off-by: Li Hua Qian <huaqian.li@siemens.com> > > --- > > arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi | 11 > > +++++++++++ > > 1 file changed, 11 insertions(+) > > > > diff --git a/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi > > b/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi > > index e26bd988e522..77380e52a334 100644 > > --- a/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi > > +++ b/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi > > @@ -63,6 +63,12 @@ rtos_ipc_memory_region: ipc-memories@a2000000 { > > alignment = <0x1000>; > > no-map; > > }; > > + > > + /* To reserve the power-on(PON) reason for watchdog > > reset */ > > + wdt_reset_memory_region: wdt-memory@a2200000 { > > + reg = <0x00 0xa2200000 0x00 0x00001000>; > > + no-map; > > + }; > > }; > > > > leds { > > @@ -718,3 +724,8 @@ &mcu_r5fss0_core1 { > > <&mcu_r5fss0_core1_memory_region>; > > mboxes = <&mailbox0_cluster1>, <&mbox_mcu_r5fss0_core1>; > > }; > > + > > +&mcu_rti1 { > > + reg = <0x0 0x40610000 0x0 0x100>, > > + <0x0 0xa2200000 0x0 0x1000>; > > That's a total mess. reserved memory and IO address space. Nope. > > > > Best regards, > Krzysztof > Yes, I misunderstood the advice. I intend to roll back as I mentioned in my last email. Any new suggestions please let me know, thank you! Best regards, Li Hua Qian
diff --git a/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi b/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi index e26bd988e522..77380e52a334 100644 --- a/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi +++ b/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi @@ -63,6 +63,12 @@ rtos_ipc_memory_region: ipc-memories@a2000000 { alignment = <0x1000>; no-map; }; + + /* To reserve the power-on(PON) reason for watchdog reset */ + wdt_reset_memory_region: wdt-memory@a2200000 { + reg = <0x00 0xa2200000 0x00 0x00001000>; + no-map; + }; }; leds { @@ -718,3 +724,8 @@ &mcu_r5fss0_core1 { <&mcu_r5fss0_core1_memory_region>; mboxes = <&mailbox0_cluster1>, <&mbox_mcu_r5fss0_core1>; }; + +&mcu_rti1 { + reg = <0x0 0x40610000 0x0 0x100>, + <0x0 0xa2200000 0x0 0x1000>; +};