.../devicetree/bindings/timer/via,vt8500-timer.txt | 15 ------- .../bindings/timer/via,vt8500-timer.yaml | 51 ++++++++++++++++++++++ MAINTAINERS | 1 + 3 files changed, 52 insertions(+), 15 deletions(-)
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.
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
Signed-off-by: Alexey Charkov <alchark@gmail.com>
---
Changes in v3:
- Added Rob's review tag (thanks Rob)
- Rebased on top of next-20250506 to pull in MAINTAINERS updates
- Link to v2: https://lore.kernel.org/r/20250418-via_vt8500_timer_binding-v2-1-3c125568f028@gmail.com
Changes in v2:
- split out this binding change from the big series affecting multiple
subsystems unnecessarily (thanks Rob)
- added description for the four possible interrupts (thanks Rob)
- added overall description of the IC block
Link to v1: https://lore.kernel.org/all/20250416-wmt-updates-v1-6-f9af689cdfc2@gmail.com/
---
.../devicetree/bindings/timer/via,vt8500-timer.txt | 15 -------
.../bindings/timer/via,vt8500-timer.yaml | 51 ++++++++++++++++++++++
MAINTAINERS | 1 +
3 files changed, 52 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@d8130100 {
- 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..e748149948f3140d4a158f800b91e70bf9c4f042
--- /dev/null
+++ b/Documentation/devicetree/bindings/timer/via,vt8500-timer.yaml
@@ -0,0 +1,51 @@
+# 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
+
+description:
+ This is the timer block that is a standalone part of the system power
+ management controller on VIA/WonderMedia SoCs (VIA VT8500 and alike).
+ 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 the
+ watchdog function is enabled, it will reset the system upon match instead
+ of triggering its respective interrupt)
+
+maintainers:
+ - Alexey Charkov <alchark@gmail.com>
+
+properties:
+ compatible:
+ const: via,vt8500-timer
+
+ reg:
+ maxItems: 1
+
+ interrupts:
+ minItems: 1
+ items:
+ - description: Channel 0 match. Note that if the watchdog function
+ is enabled, this interrupt will not fire and the system will
+ reboot instead once the counter reaches match register 0 value
+ - description: Channel 1 match
+ - description: Channel 2 match
+ - description: Channel 3 match
+
+required:
+ - compatible
+ - reg
+ - interrupts
+
+additionalProperties: false
+
+examples:
+ - |
+ timer@d8130100 {
+ compatible = "via,vt8500-timer";
+ reg = <0xd8130100 0x28>;
+ interrupts = <36>;
+ };
diff --git a/MAINTAINERS b/MAINTAINERS
index 16037aaa770fc35efb45fc26555afaa5102e2640..5c38a60eb3bddc47106509d6cc6450ae93e50191 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3467,6 +3467,7 @@ F: Documentation/devicetree/bindings/hwinfo/via,vt8500-scc-id.yaml
F: Documentation/devicetree/bindings/i2c/i2c-wmt.txt
F: Documentation/devicetree/bindings/interrupt-controller/via,vt8500-intc.yaml
F: Documentation/devicetree/bindings/pwm/via,vt8500-pwm.yaml
+F: Documentation/devicetree/bindings/timer/via,vt8500-timer.yaml
F: arch/arm/boot/dts/vt8500/
F: arch/arm/mach-vt8500/
F: drivers/clocksource/timer-vt8500.c
---
base-commit: 0a00723f4c2d0b273edd0737f236f103164a08eb
change-id: 20250418-via_vt8500_timer_binding-9021bd785e80
Best regards,
--
Alexey Charkov <alchark@gmail.com>On 5/6/25 14:16, 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. > > Reviewed-by: Rob Herring (Arm) <robh@kernel.org> > Signed-off-by: Alexey Charkov <alchark@gmail.com> > --- I assume this patch will be part of the "timer-vt8500: clean up and add watchdog function" series -- <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook | <http://twitter.com/#!/linaroorg> Twitter | <http://www.linaro.org/linaro-blog/> Blog
On Tue, May 06, 2025 at 04:16:32PM +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.
>
> Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
> Signed-off-by: Alexey Charkov <alchark@gmail.com>
> ---
> Changes in v3:
> - Added Rob's review tag (thanks Rob)
> - Rebased on top of next-20250506 to pull in MAINTAINERS updates
> - Link to v2: https://lore.kernel.org/r/20250418-via_vt8500_timer_binding-v2-1-3c125568f028@gmail.com
>
> Changes in v2:
> - split out this binding change from the big series affecting multiple
> subsystems unnecessarily (thanks Rob)
> - added description for the four possible interrupts (thanks Rob)
> - added overall description of the IC block
>
> Link to v1: https://lore.kernel.org/all/20250416-wmt-updates-v1-6-f9af689cdfc2@gmail.com/
> ---
The patch does not apply.
--- MAINTAINERS
+++ MAINTAINERS
@@ -3467,6 +3467,7 @@ F: Documentation/devicetree/bindings/hwinfo/via,vt8500-scc-id.yaml
F: Documentation/devicetree/bindings/i2c/i2c-wmt.txt
F: Documentation/devicetree/bindings/interrupt-controller/via,vt8500-intc.yaml
F: Documentation/devicetree/bindings/pwm/via,vt8500-pwm.yaml
^^^^^^ those bindings are not in my tree
+F: Documentation/devicetree/bindings/timer/via,vt8500-timer.yaml
F: arch/arm/boot/dts/vt8500/
F: arch/arm/mach-vt8500/
F: drivers/clocksource/timer-vt8500.c
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
On Tue, May 13, 2025 at 7:49 PM Daniel Lezcano <daniel.lezcano@linaro.org> wrote: > > On Tue, May 06, 2025 at 04:16:32PM +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. > > > > Reviewed-by: Rob Herring (Arm) <robh@kernel.org> > > Signed-off-by: Alexey Charkov <alchark@gmail.com> > > --- > > Changes in v3: > > - Added Rob's review tag (thanks Rob) > > - Rebased on top of next-20250506 to pull in MAINTAINERS updates > > - Link to v2: https://lore.kernel.org/r/20250418-via_vt8500_timer_binding-v2-1-3c125568f028@gmail.com > > > > Changes in v2: > > - split out this binding change from the big series affecting multiple > > subsystems unnecessarily (thanks Rob) > > - added description for the four possible interrupts (thanks Rob) > > - added overall description of the IC block > > > > Link to v1: https://lore.kernel.org/all/20250416-wmt-updates-v1-6-f9af689cdfc2@gmail.com/ > > --- > > The patch does not apply. > > --- MAINTAINERS > +++ MAINTAINERS > @@ -3467,6 +3467,7 @@ F: Documentation/devicetree/bindings/hwinfo/via,vt8500-scc-id.yaml > F: Documentation/devicetree/bindings/i2c/i2c-wmt.txt > F: Documentation/devicetree/bindings/interrupt-controller/via,vt8500-intc.yaml > F: Documentation/devicetree/bindings/pwm/via,vt8500-pwm.yaml > > ^^^^^^ those bindings are not in my tree This series is based on next-20250506. Happy to rebase onto 6.15-rc1, but these will result in a (trivial) conflict when merging the different trees into -next and to master. Please let me know if that's better. Best regards, Alexey
On 5/13/25 18:08, Alexey Charkov wrote: > On Tue, May 13, 2025 at 7:49 PM Daniel Lezcano > <daniel.lezcano@linaro.org> wrote: >> >> On Tue, May 06, 2025 at 04:16:32PM +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. >>> >>> Reviewed-by: Rob Herring (Arm) <robh@kernel.org> >>> Signed-off-by: Alexey Charkov <alchark@gmail.com> >>> --- >>> Changes in v3: >>> - Added Rob's review tag (thanks Rob) >>> - Rebased on top of next-20250506 to pull in MAINTAINERS updates >>> - Link to v2: https://lore.kernel.org/r/20250418-via_vt8500_timer_binding-v2-1-3c125568f028@gmail.com >>> >>> Changes in v2: >>> - split out this binding change from the big series affecting multiple >>> subsystems unnecessarily (thanks Rob) >>> - added description for the four possible interrupts (thanks Rob) >>> - added overall description of the IC block >>> >>> Link to v1: https://lore.kernel.org/all/20250416-wmt-updates-v1-6-f9af689cdfc2@gmail.com/ >>> --- >> >> The patch does not apply. >> >> --- MAINTAINERS >> +++ MAINTAINERS >> @@ -3467,6 +3467,7 @@ F: Documentation/devicetree/bindings/hwinfo/via,vt8500-scc-id.yaml >> F: Documentation/devicetree/bindings/i2c/i2c-wmt.txt >> F: Documentation/devicetree/bindings/interrupt-controller/via,vt8500-intc.yaml >> F: Documentation/devicetree/bindings/pwm/via,vt8500-pwm.yaml >> >> ^^^^^^ those bindings are not in my tree > > This series is based on next-20250506. Happy to rebase onto 6.15-rc1, > but these will result in a (trivial) conflict when merging the > different trees into -next and to master. Please let me know if that's > better. Usually the conflicts are solved from bottom to top when trees are pulled. If I solve the conflict at my level, it is probable another conflict will happen when the tree is pulled Please rebase against v6.15-rc5 -- <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook | <http://twitter.com/#!/linaroorg> Twitter | <http://www.linaro.org/linaro-blog/> Blog
© 2016 - 2025 Red Hat, Inc.