From: Doug Anderson <dianders@chromium.org>
To: Chris <zyw@rock-chips.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
Mike Turquette <mturquette@linaro.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kumar Gala <galak@codeaurora.org>,
Russell King <linux@arm.linux.org.uk>,
linux-rockchip@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Tony Xie <xxx@rock-chips.com>
Subject: Re: [PATCH 1/4] ARM: rockchip: add suspend and resume for RK3288
Date: Wed, 15 Oct 2014 20:44:40 -0700 [thread overview]
Message-ID: <CAD=FV=Ve4=BuqqrboJ5uyz6+RAxAEvAe+G2myf+BCk8q2+3LGA@mail.gmail.com> (raw)
In-Reply-To: <1413406066-16257-1-git-send-email-zyw@rock-chips.com>
Chris,
On Wed, Oct 15, 2014 at 1:47 PM, <zyw@rock-chips.com> wrote:
> +static const struct platform_suspend_ops rk3288_suspend_ops = {
> + .enter = rk3288_suspend_enter,
> + .valid = suspend_valid_only_mem,
> +};
As per offline discussion, let's add the regulator calls in prepare / finish.
WARNING: multiple messages have this Message-ID (diff)
From: dianders@chromium.org (Doug Anderson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] ARM: rockchip: add suspend and resume for RK3288
Date: Wed, 15 Oct 2014 20:44:40 -0700 [thread overview]
Message-ID: <CAD=FV=Ve4=BuqqrboJ5uyz6+RAxAEvAe+G2myf+BCk8q2+3LGA@mail.gmail.com> (raw)
In-Reply-To: <1413406066-16257-1-git-send-email-zyw@rock-chips.com>
Chris,
On Wed, Oct 15, 2014 at 1:47 PM, <zyw@rock-chips.com> wrote:
> +static const struct platform_suspend_ops rk3288_suspend_ops = {
> + .enter = rk3288_suspend_enter,
> + .valid = suspend_valid_only_mem,
> +};
As per offline discussion, let's add the regulator calls in prepare / finish.
next prev parent reply other threads:[~2014-10-16 3:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 20:46 [PATCH 0/4] add suspend support for RK3288 zyw
2014-10-15 20:46 ` zyw at rock-chips.com
2014-10-15 20:47 ` [PATCH 1/4] ARM: rockchip: add suspend and resume " zyw
2014-10-15 20:47 ` zyw at rock-chips.com
2014-10-15 20:47 ` zyw-TNX95d0MmH7DzftRWevZcw
2014-10-16 3:44 ` Doug Anderson [this message]
2014-10-16 3:44 ` Doug Anderson
2014-10-16 3:44 ` Doug Anderson
2014-10-15 20:48 ` [PATCH 2/4] clk: rockchip: RK3288: add suspend and resume zyw
2014-10-15 20:48 ` zyw at rock-chips.com
2014-10-16 3:34 ` Doug Anderson
2014-10-16 3:34 ` Doug Anderson
2014-10-16 3:34 ` Doug Anderson
2014-10-15 20:49 ` [PATCH 3/4] ARM: dts: add RK3288 suspend support zyw
2014-10-15 20:49 ` zyw at rock-chips.com
2014-10-16 3:43 ` Doug Anderson
2014-10-16 3:43 ` Doug Anderson
2014-10-16 3:43 ` Doug Anderson
2014-10-16 10:20 ` Mark Rutland
2014-10-16 10:20 ` Mark Rutland
2014-10-16 10:20 ` Mark Rutland
2014-10-15 20:50 ` [PATCH 4/4] ARM: rockchip: add pmu-sram sub zyw
2014-10-15 20:50 ` zyw at rock-chips.com
2014-10-15 20:50 ` zyw-TNX95d0MmH7DzftRWevZcw
2014-10-16 3:41 ` Doug Anderson
2014-10-16 3:41 ` Doug Anderson
2014-10-16 3:41 ` Doug Anderson
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=Ve4=BuqqrboJ5uyz6+RAxAEvAe+G2myf+BCk8q2+3LGA@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=heiko@sntech.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mturquette@linaro.org \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=xxx@rock-chips.com \
--cc=zyw@rock-chips.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 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.