devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Hao-Wen Ting <haowen.ting@realtek.com>, daniel.lezcano@linaro.org
Cc: jinn.cheng@realtek.com, edwardwu@realtek.com, phelic@realtek.com,
	shawn.huang724@realtek.com, haowen.ting@realtek.com,
	cy.huang@realtek.com, james.tai@realtek.com, cylee12@realtek.com,
	phinex@realtek.com, conor+dt@kernel.org, krzk+dt@kernel.org,
	robh@kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, stanley_chang@realtek.com
Subject: Re: [PATCH v4 2/2] clocksource: Add Realtek system timer driver
Date: Thu, 20 Nov 2025 11:38:01 +0100	[thread overview]
Message-ID: <87a50hkn06.ffs@tglx> (raw)
In-Reply-To: <20251120063010.830805-3-haowen.ting@realtek.com>

On Thu, Nov 20 2025 at 14:30, Hao-Wen Ting wrote:
> Add a system timer driver for Realtek SoCs.
>
> This driver registers the 1 MHz global hardware counter on Realtek
> platforms as a clock event device. Since this hardware counter starts
> counting automatically after SoC power-on, no clock initialization is
> required. Because the counter does not stop or get affected by CPU power
> down, and it supports oneshot mode, it is typically used as a tick
> broadcast timer.
>
> Signed-off-by: Hao-Wen Ting <haowen.ting@realtek.com>

Acked-by: Thomas Gleixner <tglx@linutronix.de>

      reply	other threads:[~2025-11-20 10:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20  6:30 [PATCH v4 0/2] Add Realtek System Timer Hao-Wen Ting
2025-11-20  6:30 ` [PATCH v4 1/2] dt-bindings: timer: Add Realtek SYSTIMER Hao-Wen Ting
2025-11-20  7:52   ` Krzysztof Kozlowski
2025-11-20  6:30 ` [PATCH v4 2/2] clocksource: Add Realtek system timer driver Hao-Wen Ting
2025-11-20 10:38   ` Thomas Gleixner [this message]

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=87a50hkn06.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=conor+dt@kernel.org \
    --cc=cy.huang@realtek.com \
    --cc=cylee12@realtek.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=edwardwu@realtek.com \
    --cc=haowen.ting@realtek.com \
    --cc=james.tai@realtek.com \
    --cc=jinn.cheng@realtek.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phelic@realtek.com \
    --cc=phinex@realtek.com \
    --cc=robh@kernel.org \
    --cc=shawn.huang724@realtek.com \
    --cc=stanley_chang@realtek.com \
    /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).