summaryrefslogtreecommitdiff
path: root/Documentation/devicetree/bindings/arm/twd.txt
diff options
context:
space:
mode:
authorMarc Gonzalez <marc_gonzalez@sigmadesigns.com>2015-10-09 10:20:47 +0100
committerRussell King <rmk+kernel@arm.linux.org.uk>2015-10-09 16:22:53 +0100
commit194444c52edd857210b3895e83ce45c64b58e251 (patch)
tree65e0cc031ef48d29ab39561728c75df51ef1959f /Documentation/devicetree/bindings/arm/twd.txt
parentff5138f3af4ed61ed42e00d7d771a0502460488f (diff)
ARM: 8441/2: twd: Don't set CLOCK_EVT_FEAT_C3STOP unconditionally
In 5388a6b266 ("ARM: SMP: Always enable clock event broadcast support") Russell noted that "the TWD local timers are unable to wake up the CPU when it is placed into a low power mode". However, some platforms do not stop the TWD block in low-power mode, and can thus use the TWD timer in one-shot mode, without setting up a broadcast device. Make the driver check for the "always-on" boolean property, and set the CLOCK_EVT_FEAT_C3STOP flag accordingly. Acked-by: Mark Rutland <mark.rutland@arm.com> Signed-off-by: Marc Gonzalez <marc_gonzalez@sigmadesigns.com> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Diffstat (limited to 'Documentation/devicetree/bindings/arm/twd.txt')
-rw-r--r--Documentation/devicetree/bindings/arm/twd.txt5
1 files changed, 5 insertions, 0 deletions
diff --git a/Documentation/devicetree/bindings/arm/twd.txt b/Documentation/devicetree/bindings/arm/twd.txt
index 75b8610939fa..383ea19c2bf0 100644
--- a/Documentation/devicetree/bindings/arm/twd.txt
+++ b/Documentation/devicetree/bindings/arm/twd.txt
@@ -19,6 +19,11 @@ interrupts.
- reg : Specify the base address and the size of the TWD timer
register window.
+Optional
+
+- always-on : a boolean property. If present, the timer is powered through
+ an always-on power domain, therefore it never loses context.
+
Example:
twd-timer@2c000600 {