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@xxxxxxxxxxx> > --- > 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@xxxxxxxxxxx> > + > +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
