[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID:
<DU0PR09MB61968695A2A3146EE83B7708F6BA2@DU0PR09MB6196.eurprd09.prod.outlook.com>
Date: Wed, 23 Apr 2025 12:12:02 +0000
From: Aleksa Paunovic <aleksa.paunovic@...cgroup.com>
To: "linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>
CC: Djordje Todorovic <djordje.todorovic@...cgroup.com>, Palmer Dabbelt
<palmer@...belt.com>, Conor Dooley <conor@...nel.org>, Aleksandar Rikalo
<arikalo@...il.com>, "linux-riscv@...ts.infradead.org"
<linux-riscv@...ts.infradead.org>, Paul Walmsley <paul.walmsley@...ive.com>,
Albert Ou <aou@...s.berkeley.edu>, Daniel Lezcano
<daniel.lezcano@...aro.org>, Thomas Gleixner <tglx@...utronix.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: [PATCH v3 0/2] Use GCR.U timer device as clocksource
HTEC Public
This series adds bindings for the GCR.U timer device and corresponding
driver support. Accessing the memory mapped mtime register in the GCR.U
region should be faster than trapping to M mode each time the timer
needs to be read.
Aleksa Paunovic (2):
dt-bindings: timer: mti,gcru
Allow for riscv-clock to pick up mmio address.
.../devicetree/bindings/timer/mti,gcru.yaml | 47 +++++++++++++++
arch/riscv/include/asm/timex.h | 59 ++++++++++++-------
drivers/clocksource/Kconfig | 12 ++++
drivers/clocksource/timer-riscv.c | 32 ++++++++++
4 files changed, 130 insertions(+), 20 deletions(-)
create mode 100644 Documentation/devicetree/bindings/timer/mti,gcru.yaml
--
2.34.1
Powered by blists - more mailing lists