rtc: sh: stop setting max_user_freq

max_user_freq has not been related to the hardware RTC since commit
6610e0893b8b ("RTC: Rework RTC code to use timerqueue for events"). Stop
setting it from individual driver to avoid confusing new contributors.

Reviewed-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Link: https://patch.msgid.link/20251101-max_user_freq-v1-11-c9a274fd6883@bootlin.com
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>

diff --git a/drivers/rtc/rtc-sh.c b/drivers/rtc/rtc-sh.c
index 619800a004799cc26708f29857c920e3eb918870..0510dc64c3e2528d7768ed433afc3a749ba09f10 100644 (file)
--- a/drivers/rtc/rtc-sh.c
+++ b/drivers/rtc/rtc-sh.c
@@ -423,7 +423,6 @@ static int __init sh_rtc_probe(struct platform_device *pdev)
        writeb(tmp, rtc->regbase + RCR1);
 
        rtc->rtc_dev->ops = &sh_rtc_ops;
-       rtc->rtc_dev->max_user_freq = 256;
 
        if (rtc->capabilities & RTC_CAP_4_DIGIT_YEAR) {
                rtc->rtc_dev->range_min = RTC_TIMESTAMP_BEGIN_1900;