linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/3] ARM: dts: rockchip: correct regulator power states for suspend
Date: Mon, 24 Aug 2015 19:04:29 +0200	[thread overview]
Message-ID: <2616064.1Av4bHmkNF@phil> (raw)
In-Reply-To: <1440022721-73712-3-git-send-email-briannorris@chromium.org>

Am Mittwoch, 19. August 2015, 15:18:41 schrieb Brian Norris:
> When getting translated from a downstream device tree that used slightly
> different DT bindings, these regulators got labeled with the
> "on-in-suspend" state, when they were actually supposed to be turned off
> for S3 suspend. This was harmless, but not intentional, AFAICT.
> 
> Let's turn them off to get the optimal power state.
> 
> Signed-off-by: Brian Norris <briannorris@chromium.org>
> Cc: Alexandru M Stan <amstan@chromium.org>
> Cc: Douglas Anderson <dianders@chromium.org>
> ---

applied to my dts branch for 4.3

  parent reply	other threads:[~2015-08-24 17:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19 22:18 [PATCH v2 1/3] ARM: dts: rockchip: add veyron-jaq board Brian Norris
2015-08-19 22:18 ` [PATCH v2 2/3] ARM: dts: rockchip: correct regulator PM properties Brian Norris
2015-08-19 23:35   ` Javier Martinez Canillas
2015-08-24 17:04   ` Heiko Stuebner
2015-08-19 22:18 ` [PATCH v2 3/3] ARM: dts: rockchip: correct regulator power states for suspend Brian Norris
2015-08-19 23:36   ` Javier Martinez Canillas
2015-08-24 17:04   ` Heiko Stuebner [this message]
     [not found] ` <CAHNYxRzWHvy=mv+G6wwO29=9smOCwKh6gBPLbT-TNq0PmP2Xiw@mail.gmail.com>
2015-08-19 22:59   ` [PATCH v2 1/3] ARM: dts: rockchip: add veyron-jaq board Brian Norris
2015-08-19 23:29 ` Javier Martinez Canillas
2015-08-24 17:53   ` Brian Norris
2015-08-24 17:58     ` Heiko Stuebner
2015-08-24 18:01       ` Javier Martinez Canillas
2015-08-24 18:06         ` 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=2616064.1Av4bHmkNF@phil \
    --to=heiko@sntech.de \
    --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).