From: Joshua Kinard <linux@kumba.dev>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>,
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
Subject: Re: [PATCH 02/11] rtc: ds1685: stop setting max_user_freq
Date: Sun, 2 Nov 2025 01:51:19 -0500 [thread overview]
Message-ID: <ac3e483d-6784-4acc-9fcc-b3bb605ab0c1@kumba.dev> (raw)
In-Reply-To: <20251101-max_user_freq-v1-2-c9a274fd6883@bootlin.com>
On 10/31/2025 20:45, Alexandre Belloni wrote:
> 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.
>
> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
> ---
> drivers/rtc/rtc-ds1685.c | 3 ---
> include/linux/rtc/ds1685.h | 1 -
> 2 files changed, 4 deletions(-)
>
> diff --git a/drivers/rtc/rtc-ds1685.c b/drivers/rtc/rtc-ds1685.c
> index 97423f1d0361..5fc8e36b1abf 100644
> --- a/drivers/rtc/rtc-ds1685.c
> +++ b/drivers/rtc/rtc-ds1685.c
> @@ -1268,9 +1268,6 @@ ds1685_rtc_probe(struct platform_device *pdev)
> rtc_dev->range_min = RTC_TIMESTAMP_BEGIN_2000;
> rtc_dev->range_max = RTC_TIMESTAMP_END_2099;
>
> - /* Maximum periodic rate is 8192Hz (0.122070ms). */
> - rtc_dev->max_user_freq = RTC_MAX_USER_FREQ;
> -
> /* See if the platform doesn't support UIE. */
> if (pdata->uie_unsupported)
> clear_bit(RTC_FEATURE_UPDATE_INTERRUPT, rtc_dev->features);
> diff --git a/include/linux/rtc/ds1685.h b/include/linux/rtc/ds1685.h
> index 01da4582db6d..8ec0ebfaef04 100644
> --- a/include/linux/rtc/ds1685.h
> +++ b/include/linux/rtc/ds1685.h
> @@ -324,7 +324,6 @@ struct ds1685_rtc_platform_data {
> #define RTC_SQW_2HZ 0x0f /* 0 1 1 1 1 */
> #define RTC_SQW_0HZ 0x00 /* 0 0 0 0 0 */
> #define RTC_SQW_32768HZ 32768 /* 1 - - - - */
> -#define RTC_MAX_USER_FREQ 8192
>
>
> /*
>
Acked-by: Joshua Kinard <linux@kumba.dev>
next prev parent reply other threads:[~2025-11-02 6:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-01 0:45 [PATCH 00/11] Stop setting max_user_freq in rtc drivers Alexandre Belloni
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 [this message]
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=ac3e483d-6784-4acc-9fcc-b3bb605ab0c1@kumba.dev \
--to=linux@kumba.dev \
--cc=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=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
all inboxes | Powered by JetHome®