linux-kernel - Re: [PATCH 06/13] dt-bindings: timer: via,vt8500-timer: Convert to YAML

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CABjd4YxKe0cb9qwS-ZHxuYmq3exD8TUPrY-9ZLsT5tCEdvPzWQ@mail.gmail.com>
Date: Thu, 17 Apr 2025 10:34:36 +0400
From: Alexey Charkov <alchark@...il.com>
To: Rob Herring <robh@...nel.org>
Cc: Krzysztof Kozlowski <krzk@...nel.org>, Andi Shyti <andi.shyti@...nel.org>, 
	Conor Dooley <conor+dt@...nel.org>, Thomas Gleixner <tglx@...utronix.de>, 
	Krzysztof Kozlowski <krzk+dt@...nel.org>, Ulf Hansson <ulf.hansson@...aro.org>, 
	Andrew Lunn <andrew+netdev@...n.ch>, "David S. Miller" <davem@...emloft.net>, 
	Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, 
	Uwe Kleine-König <ukleinek@...nel.org>, 
	Daniel Lezcano <daniel.lezcano@...aro.org>, linux-arm-kernel@...ts.infradead.org, 
	linux-i2c@...r.kernel.org, devicetree@...r.kernel.org, 
	linux-kernel@...r.kernel.org, linux-mmc@...r.kernel.org, 
	netdev@...r.kernel.org, linux-pwm@...r.kernel.org
Subject: Re: [PATCH 06/13] dt-bindings: timer: via,vt8500-timer: Convert to YAML

On Thu, Apr 17, 2025 at 12:16 AM Rob Herring <robh@...nel.org> wrote:
>
> On Wed, Apr 16, 2025 at 12:21:31PM +0400, Alexey Charkov wrote:
> > Rewrite the textual description for the VIA/WonderMedia timer
> > as YAML schema.
> >
> > The IP can generate up to four interrupts from four respective match
> > registers, so reflect that in the schema.
> >
> > Signed-off-by: Alexey Charkov <alchark@...il.com>
> > ---
> >  .../devicetree/bindings/timer/via,vt8500-timer.txt | 15 ---------
> >  .../bindings/timer/via,vt8500-timer.yaml           | 36 ++++++++++++++++++++++
> >  MAINTAINERS                                        |  1 +
> >  3 files changed, 37 insertions(+), 15 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/timer/via,vt8500-timer.txt b/Documentation/devicetree/bindings/timer/via,vt8500-timer.txt
> > deleted file mode 100644
> > index 901c73f0d8ef05fb54d517b807d04f80eef2e736..0000000000000000000000000000000000000000
> > --- a/Documentation/devicetree/bindings/timer/via,vt8500-timer.txt
> > +++ /dev/null
> > @@ -1,15 +0,0 @@
> > -VIA/Wondermedia VT8500 Timer
> > ------------------------------------------------------
> > -
> > -Required properties:
> > -- compatible : "via,vt8500-timer"
> > -- reg : Should contain 1 register ranges(address and length)
> > -- interrupts : interrupt for the timer
> > -
> > -Example:
> > -
> > -     timer@...30100 {
> > -             compatible = "via,vt8500-timer";
> > -             reg = <0xd8130100 0x28>;
> > -             interrupts = <36>;
> > -     };
> > diff --git a/Documentation/devicetree/bindings/timer/via,vt8500-timer.yaml b/Documentation/devicetree/bindings/timer/via,vt8500-timer.yaml
> > new file mode 100644
> > index 0000000000000000000000000000000000000000..7d9dc93b708823de9594d20ef6b7e0367c5a36f1
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/timer/via,vt8500-timer.yaml
> > @@ -0,0 +1,36 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/timer/via,vt8500-timer.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: VIA/Wondermedia VT8500 Timer
> > +
> > +maintainers:
> > +  - Alexey Charkov <alchark@...il.com>
> > +
> > +properties:
> > +  compatible:
> > +    const: via,vt8500-timer
> > +
> > +  reg:
> > +    maxItems: 1
> > +
> > +  interrupts:
> > +    minItems: 1
> > +    maxItems: 4
>
> Need to define what each entry is.

Will do, thanks.

These are OS Timer Channel 0~3 Match, respectively. The hardware has a
single 32-bit counter running at 3 MHz and four match registers, each
of which is associated with a dedicated match interrupt, and the first
of which can also serve as the system watchdog (if watchdog function
is enabled, it will reset the system upon match instead of triggering
its respective interrupt).

Best regards,
Alexey