* [PATCH v3 0/2] AM62x watchdog support
@ 2022-11-09 9:30 ` Julien Panis
0 siblings, 0 replies; 8+ messages in thread
From: Julien Panis @ 2022-11-09 9:30 UTC (permalink / raw)
To: nm, vigneshr, afd, kristo, robh+dt, krzysztof.kozlowski+dt,
linux-arm-kernel
Cc: devicetree, linux-kernel
This patch series adds support for AM62x watchdog.
Changes since v0:
- Mark MCU & WKUP watchdogs as reserved
Link: https://lore.kernel.org/all/20220630070826.11074-1-jpanis@baylibre.com/
Changes since v1:
- Rebase patch to v6.1-rc3
Link: https://lore.kernel.org/all/20220718122328.251602-1-jpanis@baylibre.com/
Changes since v2:
- Rebase patch to v6.1-rc4
- Moved wkup_rti0 status ('reserved') into 'k3-am62-wakeup.dtsi'
Link: https://lore.kernel.org/all/20221103181440.232727-1-jpanis@baylibre.com/
Julien Panis (2):
arm64: dts: ti: k3-am62: add watchdog nodes
arm64: dts: ti: k3-am625-sk: mark MCU watchdog as reserved
arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 45 ++++++++++++++++++++++
arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi | 9 +++++
arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi | 11 ++++++
arch/arm64/boot/dts/ti/k3-am625-sk.dts | 5 +++
4 files changed, 70 insertions(+)
base-commit: f0c4d9fc9cc9462659728d168387191387e903cc
--
2.37.3
^ permalink raw reply [flat|nested] 8+ messages in thread
* [PATCH v3 0/2] AM62x watchdog support
@ 2022-11-09 9:30 ` Julien Panis
0 siblings, 0 replies; 8+ messages in thread
From: Julien Panis @ 2022-11-09 9:30 UTC (permalink / raw)
To: nm, vigneshr, afd, kristo, robh+dt, krzysztof.kozlowski+dt,
linux-arm-kernel
Cc: devicetree, linux-kernel
This patch series adds support for AM62x watchdog.
Changes since v0:
- Mark MCU & WKUP watchdogs as reserved
Link: https://lore.kernel.org/all/20220630070826.11074-1-jpanis@baylibre.com/
Changes since v1:
- Rebase patch to v6.1-rc3
Link: https://lore.kernel.org/all/20220718122328.251602-1-jpanis@baylibre.com/
Changes since v2:
- Rebase patch to v6.1-rc4
- Moved wkup_rti0 status ('reserved') into 'k3-am62-wakeup.dtsi'
Link: https://lore.kernel.org/all/20221103181440.232727-1-jpanis@baylibre.com/
Julien Panis (2):
arm64: dts: ti: k3-am62: add watchdog nodes
arm64: dts: ti: k3-am625-sk: mark MCU watchdog as reserved
arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 45 ++++++++++++++++++++++
arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi | 9 +++++
arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi | 11 ++++++
arch/arm64/boot/dts/ti/k3-am625-sk.dts | 5 +++
4 files changed, 70 insertions(+)
base-commit: f0c4d9fc9cc9462659728d168387191387e903cc
--
2.37.3
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 8+ messages in thread
* [PATCH v3 1/2] arm64: dts: ti: k3-am62: add watchdog nodes
2022-11-09 9:30 ` Julien Panis
@ 2022-11-09 9:30 ` Julien Panis
-1 siblings, 0 replies; 8+ messages in thread
From: Julien Panis @ 2022-11-09 9:30 UTC (permalink / raw)
To: nm, vigneshr, afd, kristo, robh+dt, krzysztof.kozlowski+dt,
linux-arm-kernel
Cc: devicetree, linux-kernel
Add nodes for watchdogs :
- 5 in main domain
- 1 in MCU domain
- 1 in wakeup domain
Signed-off-by: Julien Panis <jpanis@baylibre.com>
---
arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 45 ++++++++++++++++++++++
arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi | 9 +++++
arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi | 11 ++++++
3 files changed, 65 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
index 03660476364f..fb8480d7cf76 100644
--- a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
@@ -591,6 +591,51 @@ main_mcan0: can@20701000 {
bosch,mram-cfg = <0x0 128 64 64 64 64 32 32>;
};
+ main_rti0: watchdog@e000000 {
+ compatible = "ti,j7-rti-wdt";
+ reg = <0x00 0x0e000000 0x00 0x100>;
+ clocks = <&k3_clks 125 0>;
+ power-domains = <&k3_pds 125 TI_SCI_PD_EXCLUSIVE>;
+ assigned-clocks = <&k3_clks 125 0>;
+ assigned-clock-parents = <&k3_clks 125 2>;
+ };
+
+ main_rti1: watchdog@e010000 {
+ compatible = "ti,j7-rti-wdt";
+ reg = <0x00 0x0e010000 0x00 0x100>;
+ clocks = <&k3_clks 126 0>;
+ power-domains = <&k3_pds 126 TI_SCI_PD_EXCLUSIVE>;
+ assigned-clocks = <&k3_clks 126 0>;
+ assigned-clock-parents = <&k3_clks 126 2>;
+ };
+
+ main_rti2: watchdog@e020000 {
+ compatible = "ti,j7-rti-wdt";
+ reg = <0x00 0x0e020000 0x00 0x100>;
+ clocks = <&k3_clks 127 0>;
+ power-domains = <&k3_pds 127 TI_SCI_PD_EXCLUSIVE>;
+ assigned-clocks = <&k3_clks 127 0>;
+ assigned-clock-parents = <&k3_clks 127 2>;
+ };
+
+ main_rti3: watchdog@e030000 {
+ compatible = "ti,j7-rti-wdt";
+ reg = <0x00 0x0e030000 0x00 0x100>;
+ clocks = <&k3_clks 128 0>;
+ power-domains = <&k3_pds 128 TI_SCI_PD_EXCLUSIVE>;
+ assigned-clocks = <&k3_clks 128 0>;
+ assigned-clock-parents = <&k3_clks 128 2>;
+ };
+
+ main_rti15: watchdog@e0f0000 {
+ compatible = "ti,j7-rti-wdt";
+ reg = <0x00 0x0e0f0000 0x00 0x100>;
+ clocks = <&k3_clks 130 0>;
+ power-domains = <&k3_pds 130 TI_SCI_PD_EXCLUSIVE>;
+ assigned-clocks = <&k3_clks 130 0>;
+ assigned-clock-parents = <&k3_clks 130 2>;
+ };
+
epwm0: pwm@23000000 {
compatible = "ti,am64-epwm", "ti,am3352-ehrpwm";
#pwm-cells = <3>;
diff --git a/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi b/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi
index f56c803560f2..f82e94def774 100644
--- a/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi
@@ -81,4 +81,13 @@ mcu_gpio0: gpio@4201000 {
clocks = <&k3_clks 79 0>;
clock-names = "gpio";
};
+
+ mcu_rti0: watchdog@4880000 {
+ compatible = "ti,j7-rti-wdt";
+ reg = <0x00 0x04880000 0x00 0x100>;
+ clocks = <&k3_clks 131 0>;
+ power-domains = <&k3_pds 131 TI_SCI_PD_EXCLUSIVE>;
+ assigned-clocks = <&k3_clks 131 0>;
+ assigned-clock-parents = <&k3_clks 131 2>;
+ };
};
diff --git a/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi
index 4090134676cf..7d5bc9dfe51d 100644
--- a/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi
@@ -38,4 +38,15 @@ wkup_i2c0: i2c@2b200000 {
clocks = <&k3_clks 107 4>;
clock-names = "fck";
};
+
+ wkup_rti0: watchdog@2b000000 {
+ compatible = "ti,j7-rti-wdt";
+ reg = <0x00 0x2b000000 0x00 0x100>;
+ clocks = <&k3_clks 132 0>;
+ power-domains = <&k3_pds 132 TI_SCI_PD_EXCLUSIVE>;
+ assigned-clocks = <&k3_clks 132 0>;
+ assigned-clock-parents = <&k3_clks 132 2>;
+ /* WKUP RTI0 is used by DM firmware */
+ status = "reserved";
+ };
};
--
2.37.3
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [PATCH v3 1/2] arm64: dts: ti: k3-am62: add watchdog nodes
@ 2022-11-09 9:30 ` Julien Panis
0 siblings, 0 replies; 8+ messages in thread
From: Julien Panis @ 2022-11-09 9:30 UTC (permalink / raw)
To: nm, vigneshr, afd, kristo, robh+dt, krzysztof.kozlowski+dt,
linux-arm-kernel
Cc: devicetree, linux-kernel
Add nodes for watchdogs :
- 5 in main domain
- 1 in MCU domain
- 1 in wakeup domain
Signed-off-by: Julien Panis <jpanis@baylibre.com>
---
arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 45 ++++++++++++++++++++++
arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi | 9 +++++
arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi | 11 ++++++
3 files changed, 65 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
index 03660476364f..fb8480d7cf76 100644
--- a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
@@ -591,6 +591,51 @@ main_mcan0: can@20701000 {
bosch,mram-cfg = <0x0 128 64 64 64 64 32 32>;
};
+ main_rti0: watchdog@e000000 {
+ compatible = "ti,j7-rti-wdt";
+ reg = <0x00 0x0e000000 0x00 0x100>;
+ clocks = <&k3_clks 125 0>;
+ power-domains = <&k3_pds 125 TI_SCI_PD_EXCLUSIVE>;
+ assigned-clocks = <&k3_clks 125 0>;
+ assigned-clock-parents = <&k3_clks 125 2>;
+ };
+
+ main_rti1: watchdog@e010000 {
+ compatible = "ti,j7-rti-wdt";
+ reg = <0x00 0x0e010000 0x00 0x100>;
+ clocks = <&k3_clks 126 0>;
+ power-domains = <&k3_pds 126 TI_SCI_PD_EXCLUSIVE>;
+ assigned-clocks = <&k3_clks 126 0>;
+ assigned-clock-parents = <&k3_clks 126 2>;
+ };
+
+ main_rti2: watchdog@e020000 {
+ compatible = "ti,j7-rti-wdt";
+ reg = <0x00 0x0e020000 0x00 0x100>;
+ clocks = <&k3_clks 127 0>;
+ power-domains = <&k3_pds 127 TI_SCI_PD_EXCLUSIVE>;
+ assigned-clocks = <&k3_clks 127 0>;
+ assigned-clock-parents = <&k3_clks 127 2>;
+ };
+
+ main_rti3: watchdog@e030000 {
+ compatible = "ti,j7-rti-wdt";
+ reg = <0x00 0x0e030000 0x00 0x100>;
+ clocks = <&k3_clks 128 0>;
+ power-domains = <&k3_pds 128 TI_SCI_PD_EXCLUSIVE>;
+ assigned-clocks = <&k3_clks 128 0>;
+ assigned-clock-parents = <&k3_clks 128 2>;
+ };
+
+ main_rti15: watchdog@e0f0000 {
+ compatible = "ti,j7-rti-wdt";
+ reg = <0x00 0x0e0f0000 0x00 0x100>;
+ clocks = <&k3_clks 130 0>;
+ power-domains = <&k3_pds 130 TI_SCI_PD_EXCLUSIVE>;
+ assigned-clocks = <&k3_clks 130 0>;
+ assigned-clock-parents = <&k3_clks 130 2>;
+ };
+
epwm0: pwm@23000000 {
compatible = "ti,am64-epwm", "ti,am3352-ehrpwm";
#pwm-cells = <3>;
diff --git a/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi b/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi
index f56c803560f2..f82e94def774 100644
--- a/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi
@@ -81,4 +81,13 @@ mcu_gpio0: gpio@4201000 {
clocks = <&k3_clks 79 0>;
clock-names = "gpio";
};
+
+ mcu_rti0: watchdog@4880000 {
+ compatible = "ti,j7-rti-wdt";
+ reg = <0x00 0x04880000 0x00 0x100>;
+ clocks = <&k3_clks 131 0>;
+ power-domains = <&k3_pds 131 TI_SCI_PD_EXCLUSIVE>;
+ assigned-clocks = <&k3_clks 131 0>;
+ assigned-clock-parents = <&k3_clks 131 2>;
+ };
};
diff --git a/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi
index 4090134676cf..7d5bc9dfe51d 100644
--- a/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi
@@ -38,4 +38,15 @@ wkup_i2c0: i2c@2b200000 {
clocks = <&k3_clks 107 4>;
clock-names = "fck";
};
+
+ wkup_rti0: watchdog@2b000000 {
+ compatible = "ti,j7-rti-wdt";
+ reg = <0x00 0x2b000000 0x00 0x100>;
+ clocks = <&k3_clks 132 0>;
+ power-domains = <&k3_pds 132 TI_SCI_PD_EXCLUSIVE>;
+ assigned-clocks = <&k3_clks 132 0>;
+ assigned-clock-parents = <&k3_clks 132 2>;
+ /* WKUP RTI0 is used by DM firmware */
+ status = "reserved";
+ };
};
--
2.37.3
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [PATCH v3 2/2] arm64: dts: ti: k3-am625-sk: mark MCU watchdog as reserved
2022-11-09 9:30 ` Julien Panis
@ 2022-11-09 9:30 ` Julien Panis
-1 siblings, 0 replies; 8+ messages in thread
From: Julien Panis @ 2022-11-09 9:30 UTC (permalink / raw)
To: nm, vigneshr, afd, kristo, robh+dt, krzysztof.kozlowski+dt,
linux-arm-kernel
Cc: devicetree, linux-kernel
MCU wdt is typically used by M4F.
Signed-off-by: Julien Panis <jpanis@baylibre.com>
---
arch/arm64/boot/dts/ti/k3-am625-sk.dts | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-am625-sk.dts b/arch/arm64/boot/dts/ti/k3-am625-sk.dts
index 93a5f0817efc..089970b304cf 100644
--- a/arch/arm64/boot/dts/ti/k3-am625-sk.dts
+++ b/arch/arm64/boot/dts/ti/k3-am625-sk.dts
@@ -503,6 +503,11 @@ &main_mcan0 {
status = "disabled";
};
+&mcu_rti0 {
+ /* MCU RTI0 is used by M4F firmware */
+ status = "reserved";
+};
+
&epwm0 {
status = "disabled";
};
--
2.37.3
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [PATCH v3 2/2] arm64: dts: ti: k3-am625-sk: mark MCU watchdog as reserved
@ 2022-11-09 9:30 ` Julien Panis
0 siblings, 0 replies; 8+ messages in thread
From: Julien Panis @ 2022-11-09 9:30 UTC (permalink / raw)
To: nm, vigneshr, afd, kristo, robh+dt, krzysztof.kozlowski+dt,
linux-arm-kernel
Cc: devicetree, linux-kernel
MCU wdt is typically used by M4F.
Signed-off-by: Julien Panis <jpanis@baylibre.com>
---
arch/arm64/boot/dts/ti/k3-am625-sk.dts | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-am625-sk.dts b/arch/arm64/boot/dts/ti/k3-am625-sk.dts
index 93a5f0817efc..089970b304cf 100644
--- a/arch/arm64/boot/dts/ti/k3-am625-sk.dts
+++ b/arch/arm64/boot/dts/ti/k3-am625-sk.dts
@@ -503,6 +503,11 @@ &main_mcan0 {
status = "disabled";
};
+&mcu_rti0 {
+ /* MCU RTI0 is used by M4F firmware */
+ status = "reserved";
+};
+
&epwm0 {
status = "disabled";
};
--
2.37.3
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply related [flat|nested] 8+ messages in thread
* Re: [PATCH v3 2/2] arm64: dts: ti: k3-am625-sk: mark MCU watchdog as reserved
2022-11-09 9:30 ` Julien Panis
@ 2022-11-09 21:22 ` Andrew Davis
-1 siblings, 0 replies; 8+ messages in thread
From: Andrew Davis @ 2022-11-09 21:22 UTC (permalink / raw)
To: Julien Panis, nm, vigneshr, kristo, robh+dt,
krzysztof.kozlowski+dt, linux-arm-kernel
Cc: devicetree, linux-kernel
On 11/9/22 3:30 AM, Julien Panis wrote:
> MCU wdt is typically used by M4F.
>
See it's this "typically" part I'm concerned about.
It depends on the firmware which peripherals will be used. The firmware
doesn't communicate this to Linux, and Linux doesn't give the firmware
permissions to use one of these peripherals.
We only keep from stepping on the firmware by changing device tree to
never use peripherals that are often used by firmware, and that is not a
hardware description, nor complete when a remote core firmware can use any
device in our systems.
What happens when I change firmware? How do we power sequence this? Who
controls the clocks and clock parents if shared for this peripheral?
I'm thinking we can used something like "application nodes"[0] here. These
are basically DT nodes for a specific firmware application. The nodes
describe the firmware and all hardware it uses (in the linked example,
the remote core to run on, DMAs, SRAM, PHYs). All these devices are under
exclusive control of the application node. So while Linux will still
handle power/clock/state control, no driver will be bound. This also
handles the power sequencing question above, sub-devices need to be active
before starting the firmware, and firmware needs to go down before the
controlled peripherals.
These nodes could be loaded/unloaded as DT overlays, along with the
firmware. So resources are only "reserved" for firmware when
the firmware is actually active.
Thoughts?
Andrew
[0] https://www.spinics.net/lists/netdev/msg823883.html
> Signed-off-by: Julien Panis <jpanis@baylibre.com>
> ---
> arch/arm64/boot/dts/ti/k3-am625-sk.dts | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am625-sk.dts b/arch/arm64/boot/dts/ti/k3-am625-sk.dts
> index 93a5f0817efc..089970b304cf 100644
> --- a/arch/arm64/boot/dts/ti/k3-am625-sk.dts
> +++ b/arch/arm64/boot/dts/ti/k3-am625-sk.dts
> @@ -503,6 +503,11 @@ &main_mcan0 {
> status = "disabled";
> };
>
> +&mcu_rti0 {
> + /* MCU RTI0 is used by M4F firmware */
> + status = "reserved";
> +};
> +
> &epwm0 {
> status = "disabled";
> };
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH v3 2/2] arm64: dts: ti: k3-am625-sk: mark MCU watchdog as reserved
@ 2022-11-09 21:22 ` Andrew Davis
0 siblings, 0 replies; 8+ messages in thread
From: Andrew Davis @ 2022-11-09 21:22 UTC (permalink / raw)
To: Julien Panis, nm, vigneshr, kristo, robh+dt,
krzysztof.kozlowski+dt, linux-arm-kernel
Cc: devicetree, linux-kernel
On 11/9/22 3:30 AM, Julien Panis wrote:
> MCU wdt is typically used by M4F.
>
See it's this "typically" part I'm concerned about.
It depends on the firmware which peripherals will be used. The firmware
doesn't communicate this to Linux, and Linux doesn't give the firmware
permissions to use one of these peripherals.
We only keep from stepping on the firmware by changing device tree to
never use peripherals that are often used by firmware, and that is not a
hardware description, nor complete when a remote core firmware can use any
device in our systems.
What happens when I change firmware? How do we power sequence this? Who
controls the clocks and clock parents if shared for this peripheral?
I'm thinking we can used something like "application nodes"[0] here. These
are basically DT nodes for a specific firmware application. The nodes
describe the firmware and all hardware it uses (in the linked example,
the remote core to run on, DMAs, SRAM, PHYs). All these devices are under
exclusive control of the application node. So while Linux will still
handle power/clock/state control, no driver will be bound. This also
handles the power sequencing question above, sub-devices need to be active
before starting the firmware, and firmware needs to go down before the
controlled peripherals.
These nodes could be loaded/unloaded as DT overlays, along with the
firmware. So resources are only "reserved" for firmware when
the firmware is actually active.
Thoughts?
Andrew
[0] https://www.spinics.net/lists/netdev/msg823883.html
> Signed-off-by: Julien Panis <jpanis@baylibre.com>
> ---
> arch/arm64/boot/dts/ti/k3-am625-sk.dts | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am625-sk.dts b/arch/arm64/boot/dts/ti/k3-am625-sk.dts
> index 93a5f0817efc..089970b304cf 100644
> --- a/arch/arm64/boot/dts/ti/k3-am625-sk.dts
> +++ b/arch/arm64/boot/dts/ti/k3-am625-sk.dts
> @@ -503,6 +503,11 @@ &main_mcan0 {
> status = "disabled";
> };
>
> +&mcu_rti0 {
> + /* MCU RTI0 is used by M4F firmware */
> + status = "reserved";
> +};
> +
> &epwm0 {
> status = "disabled";
> };
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2022-11-09 21:24 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-11-09 9:30 [PATCH v3 0/2] AM62x watchdog support Julien Panis
2022-11-09 9:30 ` Julien Panis
2022-11-09 9:30 ` [PATCH v3 1/2] arm64: dts: ti: k3-am62: add watchdog nodes Julien Panis
2022-11-09 9:30 ` Julien Panis
2022-11-09 9:30 ` [PATCH v3 2/2] arm64: dts: ti: k3-am625-sk: mark MCU watchdog as reserved Julien Panis
2022-11-09 9:30 ` Julien Panis
2022-11-09 21:22 ` Andrew Davis
2022-11-09 21:22 ` Andrew Davis
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.