All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: 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:54:49 +0100	[thread overview]
Message-ID: <Z72heU393-y555VT@ninjato> (raw)
In-Reply-To: <2025022510474487653067@mail.local>

[-- Attachment #1: Type: text/plain, Size: 681 bytes --]


> > 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...

How can I enable UIE with alarms which do not support
one-second-resolution? I found that most, if not all, drivers which have
RTC_FEATURE_ALARM_RES_MINUTE or RTC_FEATURE_ALARM_RES_2S set, they all
disable RTC_FEATURE_UPDATE_INTERRUPT. Which makes sense to me when I
look at the UIE-via-alarms code in the RTC core. But, yes, it is
convoluted, so maybe I am missing something?

Thanks for your fast reply!


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2025-02-25 10:54 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
2025-02-25 10:54   ` Wolfram Sang [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=Z72heU393-y555VT@ninjato \
    --to=wsa+renesas@sang-engineering.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=miquel.raynal@bootlin.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.