lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 19 Nov 2013 20:02:56 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	Jonghwan Choi <jhbird.choi@...il.com>
Cc:	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	Kukjin Kim <kgene.kim@...sung.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-samsung-soc <linux-samsung-soc@...r.kernel.org>,
	Jonghwan Choi <jhbird.choi@...sung.com>
Subject: Re: [PATCH 2/4] cpufreq: exynos: Consider hibernation in pm notifier

On 19 November 2013 18:59, Jonghwan Choi <jhbird.choi@...il.com> wrote:
> Frequency lock should be considered in suspend/hibernation.

These could turn out to be important logs for future. Please write
with more effort..

> Signed-off-by: Jonghwan Choi <jhbird.choi@...sung.com>
> ---
>  drivers/cpufreq/exynos-cpufreq.c | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/drivers/cpufreq/exynos-cpufreq.c b/drivers/cpufreq/exynos-cpufreq.c
> index f3c2287..cd05b0a 100644
> --- a/drivers/cpufreq/exynos-cpufreq.c
> +++ b/drivers/cpufreq/exynos-cpufreq.c
> @@ -187,6 +187,7 @@ static int exynos_cpufreq_pm_notifier(struct notifier_block *notifier,
>         int ret;
>
>         switch (pm_event) {
> +       case PM_HIBERNATION_PREPARE:
>         case PM_SUSPEND_PREPARE:
>                 mutex_lock(&cpufreq_lock);
>                 frequency_locked = true;
> @@ -198,6 +199,8 @@ static int exynos_cpufreq_pm_notifier(struct notifier_block *notifier,
>
>                 break;
>
> +       case PM_POST_HIBERNATION:
> +       case PM_POST_RESTORE:
>         case PM_POST_SUSPEND:
>                 mutex_lock(&cpufreq_lock);
>                 frequency_locked = false;

@Rafael: So we have few more drivers which are already doing such
stuff (even tegra as well)..
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ