From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
Benson Leung <bleung@chromium.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Thomas Gleixner <tglx@linutronix.de>,
John Stultz <jstultz@google.com>, Stephen Boyd <sboyd@kernel.org>,
linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org,
Brian Norris <briannorris@chromium.org>
Subject: Re: [PATCH 0/7] rtc: Add support for limited alarm timer offsets
Date: Wed, 16 Aug 2023 18:14:35 +0200 [thread overview]
Message-ID: <20230816161435bd2bbd4a@mail.local> (raw)
In-Reply-To: <8079bdf4-f790-451b-a2c2-be4e23c0c3a1@roeck-us.net>
On 16/08/2023 08:50:12-0700, Guenter Roeck wrote:
> > I'm fine with the series, however, this doesn't solve the issue for RTCs
> > that have an absolute limit on the alarm (as opposed to an offset to the
> > current time/date).
> >
>
> I thought that is checked by rtc_valid_range() in rtc_set_alarm().
> Am I missing something ? Of course that assumes that the absolute
> maximum alarm timeout matches range_max, but I didn't find any
> drivers where that would not be the case.
>
There are RTCs where this is not the case. When this is far away in the
future enough, the usual solution is to clip range_max which works but
is not really great intellectually.
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-08-16 16:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 13:39 [PATCH 0/7] rtc: Add support for limited alarm timer offsets Guenter Roeck
2023-08-16 13:39 ` [PATCH 1/7] " Guenter Roeck
2023-08-16 14:57 ` Alexandre Belloni
2023-08-16 15:24 ` Guenter Roeck
2023-08-16 16:19 ` Alexandre Belloni
2023-08-16 19:12 ` Guenter Roeck
2023-08-16 13:39 ` [PATCH 2/7] rtc: alarmtimer: Use maximum alarm time offset Guenter Roeck
2023-08-16 13:39 ` [PATCH 3/7] rtc: cros-ec: Detect and report supported alarm window size Guenter Roeck
2023-08-16 13:39 ` [PATCH 4/7] rtc: cmos: Report supported alarm limit to rtc infrastructure Guenter Roeck
2023-08-16 13:39 ` [PATCH 5/7] rtc: tps6586x: Report maximum alarm limit to rtc core Guenter Roeck
2023-08-16 13:39 ` [PATCH 6/7] rtc: ds1305: " Guenter Roeck
2023-08-16 13:39 ` [PATCH 7/7] rtc: rzn1: " Guenter Roeck
2023-08-17 8:03 ` Miquel Raynal
2023-08-17 13:43 ` Guenter Roeck
2023-08-16 15:03 ` [PATCH 0/7] rtc: Add support for limited alarm timer offsets Alexandre Belloni
2023-08-16 15:50 ` Guenter Roeck
2023-08-16 16:14 ` Alexandre Belloni [this message]
2023-08-16 19:12 ` Guenter Roeck
2023-08-17 19:51 ` Alexandre Belloni
2023-08-17 22:36 ` Guenter Roeck
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=20230816161435bd2bbd4a@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=a.zummo@towertech.it \
--cc=bleung@chromium.org \
--cc=briannorris@chromium.org \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=miquel.raynal@bootlin.com \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
/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.