From: Olof Johansson <olof@lixom.net>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, arm@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 3/3] pm changes for am335x and am437x for v5.2
Date: Sun, 28 Apr 2019 23:04:24 -0700 [thread overview]
Message-ID: <20190429060424.vw2giqpcnkcwkqm2@localhost> (raw)
In-Reply-To: <pull-1555087688-487222@atomide.com-3>
On Fri, Apr 12, 2019 at 10:02:07AM -0700, Tony Lindgren wrote:
> From: "Tony Lindgren" <tony@atomide.com>
>
> The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
>
> Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v5.2/am4-pm-v2-signed
>
> for you to fetch changes up to 35667d812c38a219ea2dc6f23d33db50de57099e:
>
> Merge branch 'omap-for-v5.2/am4-ddr3' into omap-for-v5.2/am4-pm-v2 (2019-04-10 09:06:01 -0700)
>
> ----------------------------------------------------------------
> PM changes for am335x and am437x
>
> This series adds support for am437x RTC-only mode in suspend. In the
> RTC-only mode suspend, everything is shut down except the RTC. This
> makes the power consumption very low for suspend mode.
>
> To support RTC-only mode, we need to export omap_rtc_power_off_program()
> from the rtc driver and improve PM code to save and restore the wkup
> domain context. As RTC-only mode depends on the device being wired
> properly for things like memory, we need to also check for the machine
> type before we allow it. We also need to run DDR3 hardware leveling on
> resume.
>
> Note that there is a trivial merge conflict between the RTC branch
> and these changes where the RTC branch makes tm2bcd() a void function
> and the error handling parts can be just dropped.
Merged, thanks!
-Olof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-04-29 6:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 17:02 [GIT PULL 1/3] soc changes for omaps for v5.2 Tony Lindgren
2019-04-12 17:02 ` [GIT PULL 2/3] ti-sysc driver " Tony Lindgren
2019-04-29 6:03 ` Olof Johansson
2019-04-12 17:02 ` [GIT PULL 3/3] pm changes for am335x and am437x " Tony Lindgren
2019-04-29 6:04 ` Olof Johansson [this message]
2019-04-29 6:03 ` [GIT PULL 1/3] soc changes for omaps " Olof Johansson
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=20190429060424.vw2giqpcnkcwkqm2@localhost \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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).