linux-kernel - Re: [PATCH v2 0/4] Add standby support for the recent mvebu SoCs

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] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 25 Jul 2015 17:20:07 +0200
From:	Gregory CLEMENT <gregory.clement@...e-electrons.com>
To:	linux-arm-kernel@...ts.infradead.org
CC:	Jason Cooper <jason@...edaemon.net>, Andrew Lunn <andrew@...n.ch>,
	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
	Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>,
	Maxime Ripard <maxime.ripard@...e-electrons.com>,
	Boris BREZILLON <boris.brezillon@...e-electrons.com>,
	Lior Amsalem <alior@...vell.com>,
	Tawfik Bayouk <tawfik@...vell.com>,
	Nadav Haklai <nadavh@...vell.com>, linux-pm@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/4] Add standby support for the recent mvebu SoCs

Hi,

On 30/06/2015 19:18, Gregory CLEMENT wrote:
> Hi,
> 
> Until now only few mvebu v7 based board supported suspend to ram. This
> suspend to ram mode was unusual because it involved shutting down the
> SoC and relied on a PIC to wake up the system.
> 
> However, most of the recent mvebu SoCs can support the standby
> mode. Unlike for the suspend to ram, nothing special have to be done
> for these SoCs. In this mode the SoCs go in idle mode (but they remain
> powered up) and the devices enter in suspend mode. The support itself
> was added in the patch 2.
> 
> In order to wake-up the interrupt controller driver have been
> updated. As in standby mode the interrupt controller is not shutdown,
> any interrupt can be a wake-up source. So the GIC (patch 3) now used
> the flags IRQCHIP_SKIP_SET_WAKE and IRQCHIP_MASK_ON_SUSPEND.
> 
> A wake up source is supposed to work in suspend _and_ in standby mode
> but for the mvebu SoCs, no interrupt can wake up the system. The last
> patch warns the user about it.
> 
> The first patch is a clean-up found while working on this series
> 
> This series was applied on top of Thomas' series "ARM: mvebu: add
> suspend to RAM support for Armada 38x":
> http://thread.gmane.org/gmane.linux.ports.arm.kernel/420458
> 
> It has been either using rtcwake or by setting the serial line as a
> wake-up source through the sysfs interface.


I applied the series on mvebu/soc

Thanks,

Gregory

> 
> Thanks,
> 
> Gregory
> 
> 
> Gregory CLEMENT (4):
>   ARM: mvebu: Use __init for the PM initialization functions
>   ARM: mvebu: Add standby support
>   ARM: mvebu: Allow using the GIC for wakeup in standby mode
>   ARM: mvebu: Warn about the wake-up sources not taken into account in
>     suspend
> 
>  arch/arm/mach-mvebu/board-v7.c |  7 +++++
>  arch/arm/mach-mvebu/common.h   |  5 ++--
>  arch/arm/mach-mvebu/pm-board.c | 19 +++++++++-----
>  arch/arm/mach-mvebu/pm.c       | 58 +++++++++++++++++++++++++++++++++++++-----
>  4 files changed, 73 insertions(+), 16 deletions(-)
> 


-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
--
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/