[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJ0PZbS0WKExdEmW2yepbMQWw=eeZXL8KykTMLqvKN2rCqJDuw@mail.gmail.com>
Date: Wed, 20 Nov 2013 18:45:51 +0900
From: MyungJoo Ham <myungjoo.ham@...sung.com>
To: Jonghwan Choi <jhbird.choi@...il.com>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Kukjin Kim <kgene.kim@...sung.com>,
LKML <linux-kernel@...r.kernel.org>,
Linux Samsung SoC <linux-samsung-soc@...r.kernel.org>,
Jonghwan Choi <jhbird.choi@...sung.com>
Subject: Re: [PATCH 3/4] PM / devfreq: Consider hibernation in pm notifier
On Tue, Nov 19, 2013 at 10:30 PM, Jonghwan Choi <jhbird.choi@...il.com> wrote:
> Frequency lock should be considered in suspend/hibernation.
>
> Signed-off-by: Jonghwan Choi <jhbird.choi@...sung.com>
Signed-off-by: MyungJoo Ham <myungjoo.ham@...sung.com>
Applied in "driver-update" branch.
Do you want this to be synchronously merged with others (1/4, 2/4) or
is it ok to be done asynchronously?
Cheers,
MyungJoo.
> ---
> drivers/devfreq/exynos/exynos4_bus.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/devfreq/exynos/exynos4_bus.c b/drivers/devfreq/exynos/exynos4_bus.c
> index cede6f7..dd6947e 100644
> --- a/drivers/devfreq/exynos/exynos4_bus.c
> +++ b/drivers/devfreq/exynos/exynos4_bus.c
> @@ -962,6 +962,7 @@ static int exynos4_busfreq_pm_notifier_event(struct notifier_block *this,
> int err = 0;
>
> switch (event) {
> + case PM_HIBERNATION_PREPARE:
> case PM_SUSPEND_PREPARE:
> /* Set Fastest and Deactivate DVFS */
> mutex_lock(&data->lock);
> @@ -1005,6 +1006,7 @@ unlock:
> if (err)
> return err;
> return NOTIFY_OK;
> + case PM_POST_HIBERNATION:
> case PM_POST_RESTORE:
> case PM_POST_SUSPEND:
> /* Reactivate */
> --
> 1.8.1.2
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
MyungJoo Ham, Ph.D.
System S/W Lab, S/W Center, Samsung Electronics
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists