From: Doug Anderson <dianders@chromium.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Brian Norris <briannorris@chromium.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Brian Norris <computersforpeace@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Alexandru M Stan <amstan@chromium.org>
Subject: Re: [PATCH 2/2] ARM: dts: rockchip: correct regulator PM properties
Date: Thu, 27 Aug 2015 12:30:51 -0700 [thread overview]
Message-ID: <CAD=FV=UiCcqCm+W4=ExOps8Npi=mkdVgJ2zgdomOw3YqPhCqug@mail.gmail.com> (raw)
In-Reply-To: <10828643.SSUS2EOuvv@phil>
Hi,
On Tue, Aug 18, 2015 at 11:19 PM, Heiko Stuebner <heiko@sntech.de> wrote:
> great, just take into account the deep vs. shallow suspend modes :-)
One note: do you think it would make sense to re-implement shallow
suspend as "standby"? I had a proof of concept doing that in
<https://chromium-review.googlesource.com/#/c/275123/>. One nice
advantage is that you "magically" get a second set of regulator states
for standby vs "mem".
If I understand correctly, the distinction between "standby" and "mem"
is not too clearly defined, so if we wanted to use it for this it
wouldn't be terrible?
-Doug
WARNING: multiple messages have this Message-ID (diff)
From: dianders@chromium.org (Doug Anderson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: rockchip: correct regulator PM properties
Date: Thu, 27 Aug 2015 12:30:51 -0700 [thread overview]
Message-ID: <CAD=FV=UiCcqCm+W4=ExOps8Npi=mkdVgJ2zgdomOw3YqPhCqug@mail.gmail.com> (raw)
In-Reply-To: <10828643.SSUS2EOuvv@phil>
Hi,
On Tue, Aug 18, 2015 at 11:19 PM, Heiko Stuebner <heiko@sntech.de> wrote:
> great, just take into account the deep vs. shallow suspend modes :-)
One note: do you think it would make sense to re-implement shallow
suspend as "standby"? I had a proof of concept doing that in
<https://chromium-review.googlesource.com/#/c/275123/>. One nice
advantage is that you "magically" get a second set of regulator states
for standby vs "mem".
If I understand correctly, the distinction between "standby" and "mem"
is not too clearly defined, so if we wanted to use it for this it
wouldn't be terrible?
-Doug
next prev parent reply other threads:[~2015-08-27 19:30 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 18:44 [PATCH 1/2] ARM: dts: rockchip: add veyron-jaq board Brian Norris
2015-08-18 18:44 ` Brian Norris
2015-08-18 18:44 ` Brian Norris
2015-08-18 18:44 ` [PATCH 2/2] ARM: dts: rockchip: correct regulator PM properties Brian Norris
2015-08-18 18:44 ` Brian Norris
2015-08-18 18:44 ` Brian Norris
2015-08-18 19:17 ` Heiko Stuebner
2015-08-18 19:17 ` Heiko Stuebner
2015-08-18 19:17 ` Heiko Stuebner
2015-08-18 20:30 ` Javier Martinez Canillas
2015-08-18 20:30 ` Javier Martinez Canillas
2015-08-18 20:30 ` Javier Martinez Canillas
2015-08-18 20:38 ` Javier Martinez Canillas
2015-08-18 20:38 ` Javier Martinez Canillas
2015-08-18 20:38 ` Javier Martinez Canillas
2015-08-18 22:48 ` Brian Norris
2015-08-18 22:48 ` Brian Norris
2015-08-18 22:48 ` Brian Norris
2015-08-18 23:28 ` Brian Norris
2015-08-18 23:28 ` Brian Norris
2015-08-19 6:19 ` Heiko Stuebner
2015-08-19 6:19 ` Heiko Stuebner
2015-08-19 6:19 ` Heiko Stuebner
2015-08-27 19:30 ` Doug Anderson [this message]
2015-08-27 19:30 ` Doug Anderson
2015-08-27 19:30 ` Doug Anderson
2015-08-27 20:51 ` Heiko Stuebner
2015-08-27 20:51 ` Heiko Stuebner
2015-08-27 20:51 ` Heiko Stuebner
2015-08-27 20:51 ` Heiko Stuebner
2015-08-27 20:56 ` Brian Norris
2015-08-27 20:56 ` Brian Norris
2015-08-27 20:56 ` Brian Norris
2015-08-18 19:19 ` [PATCH 1/2] ARM: dts: rockchip: add veyron-jaq board Heiko Stuebner
2015-08-18 19:19 ` Heiko Stuebner
2015-08-18 23:01 ` Brian Norris
2015-08-18 23:01 ` Brian Norris
2015-08-18 23:01 ` Brian Norris
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='CAD=FV=UiCcqCm+W4=ExOps8Npi=mkdVgJ2zgdomOw3YqPhCqug@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=amstan@chromium.org \
--cc=briannorris@chromium.org \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.