From: Philippe Schenker <philippe.schenker@toradex.com>
To: "a.zummo@towertech.it" <a.zummo@towertech.it>,
"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>
Cc: Marcel Ziswiler <marcel.ziswiler@toradex.com>,
"zhipeng.wang_1@nxp.com" <zhipeng.wang_1@nxp.com>,
"linux-rtc@vger.kernel.org" <linux-rtc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Francesco Dolcini <francesco.dolcini@toradex.com>
Subject: Re: [PATCH] rtc: allow rtc_read_alarm without read_alarm callback
Date: Wed, 15 Feb 2023 15:00:43 +0000 [thread overview]
Message-ID: <1c631d431d134f78d72bb3c23bb692f62d67803a.camel@toradex.com> (raw)
In-Reply-To: <20230214222754.582582-1-alexandre.belloni@bootlin.com>
On Tue, 2023-02-14 at 23:27 +0100, alexandre.belloni@bootlin.com wrote:
> From: Alexandre Belloni <alexandre.belloni@bootlin.com>
>
> .read_alarm is not necessary to read the current alarm because it is
> recorded in the aie_timer and so rtc_read_alarm() will never call
> rtc_read_alarm_internal() which is the only function calling the
> callback.
>
> Reported-by: Zhipeng Wang <zhipeng.wang_1@nxp.com>
> Reported-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
> Fixes: 7ae41220ef58 ("rtc: introduce features bitfield")
> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Tested-by: Philippe Schenker <philippe.schenker@toradex.com>
I tested on our SoMs Colibri iMX8X and Apalis iMX8
I used the variants that had i.MX 8QXP and i.MX 8QM placed. This patch
did solve the problem we currently have. I also wanted to mention that I
could not get them to run on a mainline kernel in a acceptable time-
frame so I tested on Toradex's kernel that is based on NXP's Kernel. [1]
[1]
https://git.toradex.com/cgit/linux-toradex.git/log/?h=toradex_5.15-2.1.x-imx
> ---
> drivers/rtc/interface.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/rtc/interface.c b/drivers/rtc/interface.c
> index 7c30cb3c764d..499d89150afc 100644
> --- a/drivers/rtc/interface.c
> +++ b/drivers/rtc/interface.c
> @@ -392,7 +392,7 @@ int rtc_read_alarm(struct rtc_device *rtc, struct
> rtc_wkalrm *alarm)
> return err;
> if (!rtc->ops) {
> err = -ENODEV;
> - } else if (!test_bit(RTC_FEATURE_ALARM, rtc->features) ||
> !rtc->ops->read_alarm) {
> + } else if (!test_bit(RTC_FEATURE_ALARM, rtc->features)) {
> err = -EINVAL;
> } else {
> memset(alarm, 0, sizeof(struct rtc_wkalrm));
prev parent reply other threads:[~2023-02-15 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 22:27 alexandre.belloni
2023-02-15 15:00 ` Philippe Schenker [this message]
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=1c631d431d134f78d72bb3c23bb692f62d67803a.camel@toradex.com \
--to=philippe.schenker@toradex.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=francesco.dolcini@toradex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=marcel.ziswiler@toradex.com \
--cc=zhipeng.wang_1@nxp.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®