Skip to content

Watchdog on Armada 375 SoC

Jason Gunthorpe linux-arm-kernel linux-watchdog 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest0 of 2 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 2 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/2] Watchdog on Armada 375 SoC
Quoted 4 lines · Ezequiel Garcia

Here we found both the above RSTOUT:

1. It has the same dedicated register as A370/XP (0x20704)
2. Also has a bit in the shared RSTOUT register (0x18254)

Unless you know otherwise I think the same risk exists, RSTOUT could be (or become) internally asserted when you unmask the bit in the control register that drives the pin, which says the watchdog driver should control to it.

Quoted 10 lines

A possible solution is to extend the reg property in the watchdog devicetree and allow for a new optional pair of cells to complete the specification of the RSTOUT.

	watchdog-timer at 20300 {
		compatible = "marvell,orion-wdt";
		reg = <0x20300 0x28
		       {shared RSOUT} 0x4
		       0x0 0x0>;
	};

I wouldn't have the 0x0, if you want to go this way, just make the 375 compatible string require a 3 entry reg.

Jason