From: Jon Hunter <jonathanh@nvidia.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
<linux-rtc@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] RTC for 4.18
Date: Tue, 26 Jun 2018 16:51:40 +0100 [thread overview]
Message-ID: <ff6d048a-c683-56e0-13f9-1627cdfd0ea9@nvidia.com> (raw)
In-Reply-To: <20180610221645.GA26123@piout.net>
Hi Alexandre,
On 10/06/18 23:16, Alexandre Belloni wrote:
> Hi Linus,
>
> Here is the pull-request for the RTC subsystem for 4.18.
>
> Setting the supported range from drivers for RTCs failing soon has
> started. A few fixes are developed along the way.
> Some drivers have been switched to SPDX by their maintainers.
>
> The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
>
> Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git tags/rtc-4.18
>
> for you to fetch changes up to e4302aec8a0646828a701443e303eb5ef48b37f5:
>
> rtc: pxa: fix probe function (2018-06-07 20:11:08 +0200)
>
> ----------------------------------------------------------------
> RTC for 4.18
>
> Subsystem:
> - rework of the rtc-test driver which allows to test the core more thoroughly
> - rtc_set_alarm() now fails early when alarms are not supported
>
> Drivers:
> - mktime is now replaced by mktime64
> - RTC range added for 88pm80x, ab-b5ze-s3, at91rm9200, brcmstb-waketimer,
> ds1685, ftrtc010, ls1x, mxc_v2, rx8581, sprd, st-lpc, tps6586x, tps65910 and
> vr41xx
> - Fixed a possible race condition in probe functions
> - pxa: fix the probe function that is broken since v4.3
> - stm32: now supports stm32mp1
>
> ----------------------------------------------------------------
> Alexandre Belloni (49):
...
> rtc: tps6586x: let the core handle rtc range
Sorry I am missing the original mail with the above change, but I
have noticed on v4.18-rc1 that rtc wake-ups from suspend are no
longer working on one of our Tegra boards. The bisect points to the
above change and reverting it fixes the problem. I have not had
chance to dig further, but if you have any thoughts, please let me
know.
Thanks!
Jon
--
nvpublic
next prev parent reply other threads:[~2018-06-26 15:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-10 22:16 Alexandre Belloni
2018-06-26 15:51 ` Jon Hunter [this message]
2018-06-26 16:15 ` Alexandre Belloni
2018-06-26 16:54 ` Jon Hunter
2018-06-26 21:31 ` Alexandre Belloni
2018-07-09 12:04 ` Jon Hunter
2018-07-09 12:17 ` Alexandre Belloni
2018-07-10 22:14 ` Alexandre Belloni
2018-07-11 9:17 ` Jon Hunter
2018-07-11 9:22 ` 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=ff6d048a-c683-56e0-13f9-1627cdfd0ea9@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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
Powered by JetHome