[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b4025a37-9589-e10e-7a60-ceee7e96443e@linaro.org>
Date: Sun, 9 Oct 2022 17:30:55 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Yinbo Zhu <zhuyinbo@...ngson.cn>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Huacai Chen <chenhuacai@...nel.org>,
WANG Xuerui <kernel@...0n.name>,
Jiaxun Yang <jiaxun.yang@...goat.com>,
Jianmin Lv <lvjianmin@...ngson.cn>,
Yun Liu <liuyun@...ngson.cn>,
Yang Li <yang.lee@...ux.alibaba.com>,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
loongarch@...ts.linux.dev
Subject: Re: [PATCH v2 2/2] dt-bindings: hpet: add loongson2k hpet binding
On 08/10/2022 08:37, Yinbo Zhu wrote:
> Add the loongson2k High Precision Event Timer (HPET) binding
> with DT schema format using json-schema.
>
> Signed-off-by: Yinbo Zhu <zhuyinbo@...ngson.cn>
> ---
> Change in v2:
> 1. Drop the "hpet0" label.
> 2. Modify the hpet node name to timer.
>
> .../bindings/timer/loongson,ls2k-hpet.yaml | 41 +++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 42 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/timer/loongson,ls2k-hpet.yaml
>
> diff --git a/Documentation/devicetree/bindings/timer/loongson,ls2k-hpet.yaml b/Documentation/devicetree/bindings/timer/loongson,ls2k-hpet.yaml
> new file mode 100644
> index 000000000000..1805f2608de8
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/timer/loongson,ls2k-hpet.yaml
> @@ -0,0 +1,41 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/timer/loongson,ls2k-hpet.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Loongson2k High Precision Event Timer (HPET)
> +
> +maintainers:
> + - Yinbo Zhu <zhuyinbo@...ngson.cn>
> +
> +properties:
> + compatible:
> + const: loongson,ls2k-hpet
> +
> + reg:
> + maxItems: 1
> +
> + clock-frequency: true
What clock? You did not answer to this one...
What values can go here?
Use Common Clock Framework instead (you did not say that it's not
possible, so I assume it's fine).
> +
> + interrupts:
Best regards,
Krzysztof
Powered by blists - more mailing lists