From: Conor Dooley <conor@kernel.org>
To: Aleksa Paunovic <aleksa.paunovic@htecgroup.com>
Cc: "linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
Djordje Todorovic <djordje.todorovic@htecgroup.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Aleksandar Rikalo <arikalo@gmail.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] dt-bindings: timer: mti,gcru
Date: Wed, 23 Apr 2025 16:27:53 +0100 [thread overview]
Message-ID: <20250423-blazer-obtain-ef4a0cd0a23d@spud> (raw)
In-Reply-To: <DU0PR09MB619646561DF9B4F262F8B2B7F6BA2@DU0PR09MB6196.eurprd09.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2278 bytes --]
On Wed, Apr 23, 2025 at 12:14:26PM +0000, Aleksa Paunovic wrote:
> HTEC Public
>
> Add dt-bindings for the GCR.U memory mapped timer device for RISC-V
> platforms. The GCR.U memory region contains shadow copies of the RISC-V
> mtime register and the hrtime Global Configuration Register.
>
> Signed-off-by: Aleksa Paunovic <aleksa.paunovic@htecgroup.com>
> ---
> .../devicetree/bindings/timer/mti,gcru.yaml | 47 +++++++++++++++++++
> 1 file changed, 47 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/timer/mti,gcru.yaml
>
> diff --git a/Documentation/devicetree/bindings/timer/mti,gcru.yaml b/Documentation/devicetree/bindings/timer/mti,gcru.yaml
> new file mode 100644
> index 000000000000..6555dbab402e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/timer/mti,gcru.yaml
> @@ -0,0 +1,47 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/timer/mti,gcru.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: GCR.U timer device for RISC-V platforms
> +
> +maintainers:
> + - Aleksa Paunovic <aleksa.paunovic@htecgroup.com>
> +
> +description:
> + The GCR.U memory region contains memory mapped shadow copies of
> + mtime and hrtime Global Configuration Registers,
> + which software can choose to make accessible from user mode.
> +
> +select:
> + properties:
> + compatible:
> + contains:
> + const: mti,gcru
> +
> + required:
> + - compatible
Why is this select required?
I don't see why it would be since there's not a fallback to a compatble
from some toher binding.
> +
> +properties:
> + compatible:
> + const: mti,gcru
> +
> + reg:
> + items:
> + - description: Read-only shadow copy of the RISC-V mtime register.
> + - description: Read-only shadow copy of the high resolution timer register.
> +
> +required:
> + - compatible
> + - reg
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + gcru: timer@1617F000 {
Drop the "gcru" label from here, there are no users.
> + compatible = "mti,gcru";
> + reg = <0x1617F050 0x8>,
> + <0x1617F090 0x8>;
> + };
> --
> 2.34.1
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-04-23 15:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 12:12 [PATCH v3 0/2] Use GCR.U timer device as clocksource Aleksa Paunovic
2025-04-23 12:14 ` [PATCH v3 1/2] dt-bindings: timer: mti,gcru Aleksa Paunovic
2025-04-23 15:27 ` Conor Dooley [this message]
2025-04-24 6:24 ` Krzysztof Kozlowski
2025-05-14 15:02 ` Aleksa Paunovic
2025-04-23 12:17 ` [PATCH v3 2/2] Allow for riscv-clock to pick up mmio address Aleksa Paunovic
2025-04-29 8:52 ` Daniel Lezcano
2025-05-14 15:13 ` Aleksa Paunovic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250423-blazer-obtain-ef4a0cd0a23d@spud \
--to=conor@kernel.org \
--cc=aleksa.paunovic@htecgroup.com \
--cc=aou@eecs.berkeley.edu \
--cc=arikalo@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=djordje.todorovic@htecgroup.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox