From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: linux-renesas-soc@vger.kernel.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
linux-rtc@vger.kernel.org
Subject: Re: [PATCH v2] rtc: rzn1: implement one-second accuracy for alarms
Date: Wed, 19 Mar 2025 08:45:01 +0100 [thread overview]
Message-ID: <Z9p1_S3FQDeZmiIo@shikoro> (raw)
In-Reply-To: <20250317222437f14a32f0@mail.local>
[-- Attachment #1: Type: text/plain, Size: 891 bytes --]
Hi Alexandre,
> I don't this it matters too much because there seem to be very few
> userspace programs using RTC_IRQP_SET and RTC_PIE_ON, muse, tutka,
> twclock, tvtime and mplayer. They are all either very old or this is an
> optional feature with a better replacement.
Well, this list of users is definitely useful, but my main motivation is
an easier to understand RTC subsystem. I just came this way where I
spent some time trying to understand a complexity only to find out it is
outdated and largely not used anymore. It could be simplified. Also,
less code to maintain.
> While I'm reviewing all your other series, do you mind having a look at
> https://lore.kernel.org/all/20250205173918.600037-1-herve.codina@bootlin.com/
> It has been submitted a while ago now.
Sure thing. Once I am done with my RTC task, I will have more time for
I2C again \o/
Happy hacking,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-03-19 7:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 10:08 [PATCH v2] rtc: rzn1: implement one-second accuracy for alarms Wolfram Sang
2025-03-05 22:06 ` Alexandre Belloni
2025-03-07 6:55 ` Wolfram Sang
2025-03-07 18:38 ` Alexandre Belloni
2025-03-08 13:21 ` Wolfram Sang
2025-03-10 8:16 ` Wolfram Sang
2025-03-10 9:07 ` Wolfram Sang
2025-03-17 22:24 ` Alexandre Belloni
2025-03-19 7:45 ` Wolfram Sang [this message]
2025-03-17 22:26 ` Alexandre Belloni
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=Z9p1_S3FQDeZmiIo@shikoro \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox