[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220719054729.2224766-2-apatel@ventanamicro.com>
Date: Tue, 19 Jul 2022 11:17:28 +0530
From: Anup Patel <apatel@...tanamicro.com>
To: Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Palmer Dabbelt <palmer@...belt.com>,
Paul Walmsley <paul.walmsley@...ive.com>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>
Cc: Atish Patra <atishp@...shpatra.org>,
Samuel Holland <samuel@...lland.org>,
Anup Patel <anup@...infault.org>, devicetree@...r.kernel.org,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
Anup Patel <apatel@...tanamicro.com>
Subject: [PATCH 1/2] dt-bindings: riscv: Add optional DT property riscv,timer-always-on
We add an optional DT property riscv,timer-always-on which if present
in CPU DT node then CPU timer is always powered-on and never loses
context.
Signed-off-by: Anup Patel <apatel@...tanamicro.com>
---
Documentation/devicetree/bindings/riscv/cpus.yaml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/riscv/cpus.yaml b/Documentation/devicetree/bindings/riscv/cpus.yaml
index d632ac76532e..33832b8dfaab 100644
--- a/Documentation/devicetree/bindings/riscv/cpus.yaml
+++ b/Documentation/devicetree/bindings/riscv/cpus.yaml
@@ -78,6 +78,12 @@ properties:
- rv64imac
- rv64imafdc
+ riscv,timer-always-on:
+ type: boolean
+ description:
+ If present, the timer is powered through an always-on power
+ domain, therefore it never loses context.
+
# RISC-V requires 'timebase-frequency' in /cpus, so disallow it here
timebase-frequency: false
--
2.34.1
Powered by blists - more mailing lists