All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	linux-rtc@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Re: Q: use 1s irqs to overcome alarm minute granularity?
Date: Tue, 25 Feb 2025 11:47:44 +0100	[thread overview]
Message-ID: <2025022510474487653067@mail.local> (raw)
In-Reply-To: <Z72ZFf-3Z78O44nm@ninjato>

Hi,

On 25/02/2025 11:19:01+0100, Wolfram Sang wrote:
> so alarms of the Renesas RZ-N1 RTC can only have one-minute-granularity.
> However, it does have a one-second-interrupt. Has it been tried already
> for some driver to use such an interrupt to emulate second-granularity
> of the alarm? My searches did not yield results so far.
> 
> So the idea is, of course, to the let the alarm fire on the minutes.
> Then, enable the second-update irqs until reading the seconds matches
> the requested seconds of the alarm.

I'd say this is probably useless because you will already be awake
anyway so I don't see the clear benefit.

> 
> It would not only gain us a better resolution for alarms, but also
> allows for enabling UIE.

This is already something you can do. I admit this has become super
convoluted since Jon switched UIEs to be handled using the alarm
interrupt...


-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2025-02-25 10:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-25 10:19 Q: use 1s irqs to overcome alarm minute granularity? Wolfram Sang
2025-02-25 10:24 ` Biju Das
2025-02-25 10:28   ` Wolfram Sang
2025-02-25 10:47 ` Alexandre Belloni [this message]
2025-02-25 10:54   ` Wolfram Sang

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=2025022510474487653067@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=wsa+renesas@sang-engineering.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.