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: Mon, 9 Jul 2018 13:04:36 +0100 [thread overview]
Message-ID: <7fab97df-9cd9-fa57-47a8-883a717dd96c@nvidia.com> (raw)
In-Reply-To: <20180626213138.GI4207@piout.net>
Hi Alexandre,
On 26/06/18 22:31, Alexandre Belloni wrote:
> On 26/06/2018 17:54:57+0100, Jon Hunter wrote:
>>
>> On 26/06/18 17:15, Alexandre Belloni wrote:
>>> Hi,
>>>
>>> On 26/06/2018 16:51:40+0100, Jon Hunter wrote:
>>>>> 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 for the report, does the following patch fix the issue:
>>>
>>> https://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git/patch/?id=1b287f23b0a1fcb2b502dae981a8024be379391e
>>
>> Thanks. I gave the above a test, but still not waking-up from suspend.
>>
>
> Ok, I probably found the issue but the fix is not immediate. I'll try to
> post something tomorrow.
Sorry if I missed it, but did you send a fix for this?
Cheers
Jon
--
nvpublic
next prev parent reply other threads:[~2018-07-09 12:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-10 22:16 [GIT PULL] RTC for 4.18 Alexandre Belloni
2018-06-26 15:51 ` Jon Hunter
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 [this message]
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=7fab97df-9cd9-fa57-47a8-883a717dd96c@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;
as well as URLs for NNTP newsgroup(s).