From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Liam Beguin <liambeguin@gmail.com>
Cc: a.zummo@towertech.it, panfilov.artyom@gmail.com,
linux-rtc@vger.kernel.org
Subject: Re: [PATCH v1 4/4] rtc: ab-eoz9: make use of RTC_FEATURE_ALARM
Date: Mon, 5 Apr 2021 19:43:16 +0200 [thread overview]
Message-ID: <YGtMNITMoImJkiuh@piout.net> (raw)
In-Reply-To: <20210405141334.3884528-5-liambeguin@gmail.com>
On 05/04/2021 10:13:34-0400, Liam Beguin wrote:
> From: Liam Beguin <lvb@xiphos.com>
>
> Move the alarm callbacks in rtc_ops and use RTC_FEATURE_ALARM to notify
> the core whether alarm capabilities are available or not.
>
Please squash that one with the previous one.
alse, the series looks good, thanks for working on that!
> Signed-off-by: Liam Beguin <lvb@xiphos.com>
> ---
> drivers/rtc/rtc-ab-eoz9.c | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/rtc/rtc-ab-eoz9.c b/drivers/rtc/rtc-ab-eoz9.c
> index 4c8ba62fb1c6..a8256747d95d 100644
> --- a/drivers/rtc/rtc-ab-eoz9.c
> +++ b/drivers/rtc/rtc-ab-eoz9.c
> @@ -368,11 +368,6 @@ static int abeoz9_rtc_setup(struct device *dev, struct device_node *node)
> }
>
> static const struct rtc_class_ops rtc_ops = {
> - .read_time = abeoz9_rtc_get_time,
> - .set_time = abeoz9_rtc_set_time,
> -};
> -
> -static const struct rtc_class_ops rtc_alarm_ops = {
> .read_time = abeoz9_rtc_get_time,
> .set_time = abeoz9_rtc_set_time,
> .read_alarm = abeoz9_rtc_read_alarm,
> @@ -540,6 +535,7 @@ static int abeoz9_probe(struct i2c_client *client,
> data->rtc->range_min = RTC_TIMESTAMP_BEGIN_2000;
> data->rtc->range_max = RTC_TIMESTAMP_END_2099;
> data->rtc->uie_unsupported = 1;
> + clear_bit(RTC_FEATURE_ALARM, data->rtc->features);
>
> if (client->irq > 0) {
> ret = devm_request_threaded_irq(dev, client->irq, NULL,
> @@ -554,7 +550,7 @@ static int abeoz9_probe(struct i2c_client *client,
>
> if (client->irq > 0 || device_property_read_bool(dev, "wakeup-source")) {
> ret = device_init_wakeup(dev, true);
> - data->rtc->ops = &rtc_alarm_ops;
> + set_bit(RTC_FEATURE_ALARM, data->rtc->features);
> }
>
> ret = devm_rtc_register_device(data->rtc);
> --
> 2.30.1.489.g328c10930387
>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-04-05 17:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 14:13 [PATCH v1 0/4] add alarm support for the rtc-ab-eoz9 Liam Beguin
2021-04-05 14:13 ` [PATCH v1 1/4] rtc: ab-eoz9: make use of regmap local variable Liam Beguin
2021-04-05 17:36 ` Alexandre Belloni
2021-04-05 20:19 ` Liam Beguin
2021-04-05 14:13 ` [PATCH v1 2/4] rtc: ab-eoz9: set regmap max_register Liam Beguin
2021-04-05 14:13 ` [PATCH v1 3/4] rtc: ab-eoz9: add alarm support Liam Beguin
2021-04-05 17:42 ` Alexandre Belloni
2021-04-05 20:21 ` Liam Beguin
2021-04-05 14:13 ` [PATCH v1 4/4] rtc: ab-eoz9: make use of RTC_FEATURE_ALARM Liam Beguin
2021-04-05 17:43 ` Alexandre Belloni [this message]
2021-04-05 20:24 ` Liam Beguin
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=YGtMNITMoImJkiuh@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=a.zummo@towertech.it \
--cc=liambeguin@gmail.com \
--cc=linux-rtc@vger.kernel.org \
--cc=panfilov.artyom@gmail.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).