OpenSBI Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: Anup Patel <anup.patel@oss.qualcomm.com>
Cc: Atish Patra <atish.patra@linux.dev>,
	 Andrew Jones <andrew.jones@oss.qualcomm.com>,
	Samuel Holland <samuel.holland@sifive.com>,
	 Anup Patel <anup@brainfault.org>,
	opensbi@lists.infradead.org
Subject: Re: [PATCH v2 4/4] lib: sbi_timer: Introduce sbi_timer_compute_delta() and friends
Date: Wed, 29 Apr 2026 18:20:48 +1000	[thread overview]
Message-ID: <afG-1_E0ryqY64GQ@lima-default> (raw)
In-Reply-To: <20260425104048.2335262-5-anup.patel@oss.qualcomm.com>

On Sat, Apr 25, 2026 at 04:10:48PM +0530, Anup Patel wrote:
> The users of timer event have to compute next_event (aka timer value
> in the future) based on desired units and unit frequency. Introduce
> sbi_timer_compute_delta() and friends to simplify computing next_event
> for timer event users.
> 
> Signed-off-by: Anup Patel <anup.patel@oss.qualcomm.com>

Reviewed-by: Nicholas Piggin <npiggin@gmail.com>

-- 
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi

  reply	other threads:[~2026-04-29  8:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-25 10:40 [PATCH v2 0/4] Timer events for OpenSBI Anup Patel
2026-04-25 10:40 ` [PATCH v2 1/4] include: sbi: Add sbi_scratch_hartindex() macro Anup Patel
2026-04-25 10:40 ` [PATCH v2 2/4] lib: sbi_timer: Introduce per-HART timer state Anup Patel
2026-04-25 10:40 ` [PATCH v2 3/4] lib: sbi_timer: Add support for timer events Anup Patel
2026-04-29  8:18   ` Nicholas Piggin
2026-04-25 10:40 ` [PATCH v2 4/4] lib: sbi_timer: Introduce sbi_timer_compute_delta() and friends Anup Patel
2026-04-29  8:20   ` Nicholas Piggin [this message]
2026-05-09  7:46 ` [PATCH v2 0/4] Timer events for OpenSBI Anup Patel

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=afG-1_E0ryqY64GQ@lima-default \
    --to=npiggin@gmail.com \
    --cc=andrew.jones@oss.qualcomm.com \
    --cc=anup.patel@oss.qualcomm.com \
    --cc=anup@brainfault.org \
    --cc=atish.patra@linux.dev \
    --cc=opensbi@lists.infradead.org \
    --cc=samuel.holland@sifive.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