From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Gabriele Mazzotta <gabriele.mzt@gmail.com>
Cc: a.zummo@towertech.it, rtc-linux@googlegroups.com,
linux-kernel@vger.kernel.org, matthew.garrett@nebula.com
Subject: Re: [PATCH 1/2] rtc-cmos: Clear expired alarm after resume
Date: Sat, 4 Jun 2016 16:46:26 +0200 [thread overview]
Message-ID: <20160604144626.GM4594@piout.net> (raw)
In-Reply-To: <1464795615-7748-1-git-send-email-gabriele.mzt@gmail.com>
Hi,
On 01/06/2016 at 17:40:14 +0200, Gabriele Mazzotta wrote :
> If the system wakes up because of a wake alarm, the internal state
> of the alarm is not updated. As consequence, the state no longer
> reflects the actual state of the hardware and setting a new alarm
> is not possible until the expired alarm is cleared.
>
I'm not completely sure to understand what is happening but could you
check whether that one is solved by
2b2f5ff00f63847d95adad6289bd8b05f5983dd5 in my tree (rtc-next).
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-06-04 14:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 15:40 [PATCH 1/2] rtc-cmos: Clear expired alarm after resume Gabriele Mazzotta
2016-06-01 15:40 ` [PATCH 2/2] rtc-cmos: Restore " Gabriele Mazzotta
2016-06-01 16:11 ` [PATCH 1/2] rtc-cmos: Clear expired " Gabriele Mazzotta
2016-06-04 14:46 ` Alexandre Belloni [this message]
2016-06-04 16:58 ` Gabriele Mazzotta
2016-06-04 17:48 ` Alexandre Belloni
2016-08-25 14:54 ` Gabriele Mazzotta
2016-08-30 23:28 ` Alexandre Belloni
2016-08-31 15:05 ` Gabriele Mazzotta
2016-08-31 16:08 ` Alexandre Belloni
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=20160604144626.GM4594@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=gabriele.mzt@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.garrett@nebula.com \
--cc=rtc-linux@googlegroups.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).