From: Alexey Charkov <alchark@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Alexey Charkov <alchark@gmail.com>
Subject: [PATCH v2 0/4] clocksource/drivers/timer-vt8500: clean up and add watchdog function
Date: Wed, 07 May 2025 10:58:29 +0400 [thread overview]
Message-ID: <20250507-vt8500-timer-updates-v2-0-65e5d1b0855e@gmail.com> (raw)
Add named defines for all registers and bits in timer-vt8500.
Move the system events timer from channel 0 to channel 1 when enough
information is provided by the device tree (i.e. more than one IRQ).
Use channel 0 for the system watchdog
Signed-off-by: Alexey Charkov <alchark@gmail.com>
---
Changes in v2:
- Included the previously reviewed binding change that is directly related
to this series as the first patch here (thanks Krzysztof)
- Created a separate config symbol for the watchdog function to let users
build a kernel without forcing watchdog functionality upon them
(thanks Krzysztof)
- Link to the previous binding submission: https://lore.kernel.org/all/20250506-via_vt8500_timer_binding-v3-1-88450907503f@gmail.com/
- Link to v1: https://lore.kernel.org/r/20250507-vt8500-timer-updates-v1-0-6b76f7f340a6@gmail.com
---
Alexey Charkov (4):
dt-bindings: timer: via,vt8500-timer: Convert to YAML
clocksource/drivers/timer-vt8500: Add defines for magic constants
clocksource/drivers/timer-vt8500: Add watchdog functionality
ARM: dts: vt8500: list all four timer interrupts
.../devicetree/bindings/timer/via,vt8500-timer.txt | 15 ---
.../bindings/timer/via,vt8500-timer.yaml | 51 +++++++++
MAINTAINERS | 1 +
arch/arm/boot/dts/vt8500/vt8500.dtsi | 2 +-
arch/arm/boot/dts/vt8500/wm8505.dtsi | 2 +-
arch/arm/boot/dts/vt8500/wm8650.dtsi | 2 +-
arch/arm/boot/dts/vt8500/wm8750.dtsi | 2 +-
arch/arm/boot/dts/vt8500/wm8850.dtsi | 2 +-
drivers/clocksource/Kconfig | 11 ++
drivers/clocksource/timer-vt8500.c | 118 ++++++++++++++++-----
10 files changed, 162 insertions(+), 44 deletions(-)
---
base-commit: 0a00723f4c2d0b273edd0737f236f103164a08eb
change-id: 20250506-vt8500-timer-updates-44a0d22cd720
Best regards,
--
Alexey Charkov <alchark@gmail.com>
next reply other threads:[~2025-05-07 6:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 6:58 Alexey Charkov [this message]
2025-05-07 6:58 ` [PATCH v2 1/4] dt-bindings: timer: via,vt8500-timer: Convert to YAML Alexey Charkov
2025-05-07 6:58 ` [PATCH v2 2/4] clocksource/drivers/timer-vt8500: Add defines for magic constants Alexey Charkov
2025-05-07 6:58 ` [PATCH v2 3/4] clocksource/drivers/timer-vt8500: Add watchdog functionality Alexey Charkov
2025-05-13 13:40 ` Daniel Lezcano
2025-05-13 16:02 ` Alexey Charkov
2025-05-07 6:58 ` [PATCH v2 4/4] ARM: dts: vt8500: list all four timer interrupts Alexey Charkov
2025-05-12 6:38 ` (subset) " Krzysztof Kozlowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250507-vt8500-timer-updates-v2-0-65e5d1b0855e@gmail.com \
--to=alchark@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).