[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250714-wooden-ebony-turaco-a0accf@krzk-bin>
Date: Mon, 14 Jul 2025 09:24:59 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Aleksa Paunovic <aleksa.paunovic@...cgroup.com>
Cc: Daniel Lezcano <daniel.lezcano@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
Paul Walmsley <paul.walmsley@...ive.com>, Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>, Alexandre Ghiti <alex@...ti.fr>, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linux-riscv@...ts.infradead.org,
Djordje Todorovic <djordje.todorovic@...cgroup.com>, Conor Dooley <conor.dooley@...rochip.com>
Subject: Re: [PATCH v5 1/2] dt-bindings: timer: mti,gcru
On Fri, Jul 11, 2025 at 11:56:45PM +0200, Aleksa Paunovic wrote:
> +$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@...cgroup.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.
> +
> +properties:
> + compatible:
> + const: mti,gcru
Is this architecture? vendor prefix suggests not. So is this for SoC?
Then why there are no SoC compatibles here instead?
Best regards,
Krzysztof
Powered by blists - more mailing lists