From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Joshua Kinard <linux@kumba.dev>,
Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>,
Ovidiu Panait <ovidiu.panait.rb@renesas.com>
Cc: linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: [PATCH 00/11] Stop setting max_user_freq in rtc drivers
Date: Sat, 01 Nov 2025 01:45:02 +0100 [thread overview]
Message-ID: <20251101-max_user_freq-v1-0-c9a274fd6883@bootlin.com> (raw)
max_user_freq has not been related to the hardware RTC since 6610e0893b8b
("RTC: Rework RTC code to use timerqueue for events"). It is not limited by
the hardware capabilities and so it is not necessary to set it from the RTC
drivers as a user with sufficient rights will be able to change the value.
Also, max_user_freq is always clamped to 5000, there is not point in
setting an higher value.
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
---
Alexandre Belloni (11):
rtc: sa1100: stop setting max_user_freq
rtc: ds1685: stop setting max_user_freq
rtc: pic32: stop setting max_user_freq
rtc: renesas-rtca3: stop setting max_user_freq
rtc: rv3028: stop setting max_user_freq
rtc: rv3032: stop setting max_user_freq
rtc: rv8803: stop setting max_user_freq
rtc: rx6110: stop setting max_user_freq
rtc: rx8010: stop setting max_user_freq
rtc: rx8025: stop setting max_user_freq
rtc: sh: stop setting max_user_freq
drivers/rtc/rtc-ds1685.c | 3 ---
drivers/rtc/rtc-pic32.c | 2 --
drivers/rtc/rtc-renesas-rtca3.c | 1 -
drivers/rtc/rtc-rv3028.c | 2 --
drivers/rtc/rtc-rv3032.c | 2 --
drivers/rtc/rtc-rv8803.c | 2 --
drivers/rtc/rtc-rx6110.c | 2 --
drivers/rtc/rtc-rx8010.c | 1 -
drivers/rtc/rtc-rx8025.c | 2 --
drivers/rtc/rtc-sa1100.c | 3 ---
drivers/rtc/rtc-sh.c | 1 -
include/linux/rtc/ds1685.h | 1 -
12 files changed, 22 deletions(-)
---
base-commit: 384150d7a5b60c1086790a8ee07b0629f906cca2
change-id: 20251031-max_user_freq-53e362de297e
Best regards,
--
Alexandre Belloni <alexandre.belloni@bootlin.com>
next reply other threads:[~2025-11-01 0:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-01 0:45 Alexandre Belloni [this message]
2025-11-01 0:45 ` [PATCH 01/11] rtc: sa1100: stop setting max_user_freq Alexandre Belloni
2025-11-01 0:45 ` [PATCH 02/11] rtc: ds1685: " Alexandre Belloni
2025-11-02 6:51 ` Joshua Kinard
2025-11-01 0:45 ` [PATCH 03/11] rtc: pic32: " Alexandre Belloni
2025-11-01 0:45 ` [PATCH 04/11] rtc: renesas-rtca3: " Alexandre Belloni
2025-11-01 15:00 ` Claudiu Beznea
2025-11-01 0:45 ` [PATCH 05/11] rtc: rv3028: " Alexandre Belloni
2025-11-01 0:45 ` [PATCH 06/11] rtc: rv3032: " Alexandre Belloni
2025-11-01 0:45 ` [PATCH 07/11] rtc: rv8803: " Alexandre Belloni
2025-11-01 0:45 ` [PATCH 08/11] rtc: rx6110: " Alexandre Belloni
2025-11-01 0:45 ` [PATCH 09/11] rtc: rx8010: " Alexandre Belloni
2025-11-01 0:45 ` [PATCH 10/11] rtc: rx8025: " Alexandre Belloni
2025-11-01 0:45 ` [PATCH 11/11] rtc: sh: " Alexandre Belloni
2025-11-01 16:28 ` 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=20251101-max_user_freq-v1-0-c9a274fd6883@bootlin.com \
--to=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux@kumba.dev \
--cc=ovidiu.panait.rb@renesas.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;
as well as URLs for NNTP newsgroup(s).