linux-rtc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: "Csókás Bence" <csokas.bence@prolan.hu>
Cc: linux-rtc@vger.kernel.org
Subject: Re: [PATCH 1/2] rtc: Add UIE handling ability to rtc_class_ops
Date: Thu, 30 May 2024 12:35:32 +0200	[thread overview]
Message-ID: <20240530103532e6d4f421@mail.local> (raw)
In-Reply-To: <81184944-5012-41da-a596-220b74437552@prolan.hu>

On 30/05/2024 11:59:47+0200, Csókás Bence wrote:
> Hi!
> 
> On 5/28/24 19:56, Alexandre Belloni wrote:
> > Hello,
> > 
> > On 28/05/2024 18:13:14+0200, Csókás, Bence wrote:
> > > Currently, Update Interrupt Enable is performed by emulating
> > > it with either polling, or alarm interrupts. Some RTCs, however,
> > > can directly provide Update Interrupts.
> > > 
> > 
> > This has been removed from the kernel 13 years ago. What is your use
> > case to reintroduce it?
> 
> The rationale was in the cover letter. Currently, the RTC core uses the
> alarm system to implement UI, but this causes lost updates on PCF2129.
> However, it has built-in Update Interrupt capabilities in the form of the
> Second Interrupt, therefore we should just use that.
> 
> So my question would instead be: what was the rationale of removing it in
> the first place?

Well, you didn't answer my question which is why do you need UIE and
especially UIE from the RTC? Using the timer emulation is probably what
you want because it is in sync with your system time.


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

  reply	other threads:[~2024-05-30 10:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28 16:13 [PATCH 1/2] rtc: Add UIE handling ability to rtc_class_ops Csókás, Bence
2024-05-28 17:56 ` Alexandre Belloni
2024-05-30  9:59   ` Csókás Bence
2024-05-30 10:35     ` Alexandre Belloni [this message]
2024-05-30 13:47       ` Csókás Bence

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=20240530103532e6d4f421@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=csokas.bence@prolan.hu \
    --cc=linux-rtc@vger.kernel.org \
    /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).