From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: AM43XX: Add functions to save/restore am43xx control registers
Date: Wed, 23 May 2018 11:56:01 -0700 [thread overview]
Message-ID: <20180523185601.GU98604@atomide.com> (raw)
In-Reply-To: <1527013299-7982-1-git-send-email-j-keerthy@ti.com>
* Keerthy <j-keerthy@ti.com> [180522 11:24]:
> From: Tero Kristo <t-kristo@ti.com>
>
> These registers are part of the wkup domain and are lost during RTC only
> suspend and also hibernation, so storing/restoring their state is
> necessary.
>
> Signed-off-by: Tero Kristo <t-kristo@ti.com>
> Signed-off-by: Keerthy <j-keerthy@ti.com>
> ---
>
> Changes in v2:
>
> * Introduced cpu_pm notifier instead of direct calls from pm33xx code.
> * Tested on am437x-gp-evm
>
> Probably too late for 4.18!
Applying into omap-for-v4.18/soc thanks, let's see if we can still
make it. If not, then for v4.19.
Regards,
Tony
prev parent reply other threads:[~2018-05-23 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 18:21 [PATCH v2] ARM: AM43XX: Add functions to save/restore am43xx control registers Keerthy
2018-05-23 18:56 ` Tony Lindgren [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=20180523185601.GU98604@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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).