aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSuman Anna2014-08-05 16:12:01 -0500
committerSuman Anna2019-03-11 12:02:29 -0500
commit8011736d9058879d6fa94834fd5acf1176a38eed (patch)
tree281e2ec823be387c1e708cdeb12060ac177bff74
parent8af91133c784d77e5610137338ffae1619e41d71 (diff)
downloadremoteproc-8011736d9058879d6fa94834fd5acf1176a38eed.tar.gz
remoteproc-8011736d9058879d6fa94834fd5acf1176a38eed.tar.xz
remoteproc-8011736d9058879d6fa94834fd5acf1176a38eed.zip
ARM: dts: omap5-uevm: Add watchdog timers for IPU and DSP
The watchdog timers have been added for the IPU and DSP remoteproc devices for the OMAP5 uEVM board. The following timers (same as the timers on OMAP4 Panda boards) are used as the watchdog timers, DSP : GPT6 IPU : GPT9 & GPT11 (one for each Cortex-M4 core) The MPU-side drivers will use this data to initialize the watchdog timers, and listen for any watchdog triggers. The BIOS-side code needs to configure and refresh these timers properly to not throw a watchdog error. These timers can be changed or removed as per the system integration needs, alongside appropriate equivalent changes on the firmware side. Signed-off-by: Suman Anna <s-anna@ti.com>
-rw-r--r--arch/arm/boot/dts/omap5-uevm.dts2
1 files changed, 2 insertions, 0 deletions
diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts/omap5-uevm.dts
index a800a49b1547..c02fc2b48e62 100644
--- a/arch/arm/boot/dts/omap5-uevm.dts
+++ b/arch/arm/boot/dts/omap5-uevm.dts
@@ -226,10 +226,12 @@
226 status = "okay"; 226 status = "okay";
227 memory-region = <&dsp_memory_region>; 227 memory-region = <&dsp_memory_region>;
228 timers = <&timer5>; 228 timers = <&timer5>;
229 watchdog-timers = <&timer6>;
229}; 230};
230 231
231&ipu { 232&ipu {
232 status = "okay"; 233 status = "okay";
233 memory-region = <&ipu_memory_region>; 234 memory-region = <&ipu_memory_region>;
234 timers = <&timer3>; 235 timers = <&timer3>;
236 watchdog-timers = <&timer9>, <&timer11>;
235}; 237};