From: "Heiko Stübner" <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Cc: Chris Zhong <zyw-TNX95d0MmH7DzftRWevZcw@public.gmane.org>,
dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
amstan-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org
Subject: Re: [PATCH v3 1/3] ARM: rockchip: rename osc_switch_to_32k variable
Date: Thu, 06 Aug 2015 13:11:49 +0200 [thread overview]
Message-ID: <39971049.CiZJKWC18V@diego> (raw)
In-Reply-To: <2128609.Kb18M8K28F@diego>
Am Mittwoch, 5. August 2015, 00:50:39 schrieb Heiko Stübner:
> The variable name is misleading, as the deep suspend mode always switches
> the main supplying clock to the 32kHz source. Additionally the main
> oscillator remain running in some cases, which this var indicates.
>
> So rename it to osc_disable to clarity.
>
> Signed-off-by: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
applied all 3 patches with Chris' and Doug's tags to my soc branch
prev parent reply other threads:[~2015-08-06 11:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 22:50 [PATCH v3 1/3] ARM: rockchip: rename osc_switch_to_32k variable Heiko Stübner
2015-08-04 22:51 ` [PATCH v3 2/3] ARM: rockchip: set correct stabilization thresholds in suspend Heiko Stübner
2015-08-05 10:41 ` Chris Zhong
2015-08-06 1:54 ` Doug Anderson
2015-08-04 22:51 ` [PATCH v3 3/3] ARM: rockchip: enable PMU_GPIOINT_WAKEUP_EN when entering shallow suspend Heiko Stübner
2015-08-05 10:51 ` Chris Zhong
2015-08-06 1:55 ` Doug Anderson
[not found] ` <CAD=FV=W0L_0iM+15BAUfTA2ij5Ac90aVW9JZYyDhHMDNT2ZUMg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-08-06 11:10 ` Heiko Stübner
2015-08-05 10:36 ` [PATCH v3 1/3] ARM: rockchip: rename osc_switch_to_32k variable Chris Zhong
2015-08-05 23:45 ` Doug Anderson
2015-08-06 11:11 ` Heiko Stübner [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=39971049.CiZJKWC18V@diego \
--to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
--cc=amstan-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=zyw-TNX95d0MmH7DzftRWevZcw@public.gmane.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