From mboxrd@z Thu Jan 1 00:00:00 1970 From: oneukum@suse.com (Oliver Neukum) Date: Thu, 19 May 2016 14:01:01 +0200 Subject: [PSCI DISCUSS] How to implement standby and suspend-to-ram by PSCI In-Reply-To: References: <572C9BF2.9010004@arm.com> <1463486036.19237.9.camel@suse.com> Message-ID: <1463659261.14323.3.camel@suse.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, 2016-05-19 at 10:27 +0000, Hongbo Zhang wrote: > > For the pm module of the core kernel a low power state is a sleep > > state if even one of three conditions is met: > > > > a) a device that can be used for input is not a source of wake ups > > b) tasks need to be frozen to enter it > > c) the display goes off, while it should be on > > > > Generally runtime PM is better if you can get the same results. > > Going to a system sleep state is a necessary evil. > As I just explained in previous reply, many devices in our Soc cannot > be physically clock or power gated, all the non-wakeup devices can > only be gated off at same time by a PM module, so runtime PM doesn't > fit for us well. You are looking for a contradiction where none is to be found. We have PM domains which allow you to model common clocks and gates. You simply use the driver core and it will use the common gate when every device is idle. Obviously this is also true when the system is suspended. But not necessarily only when the system is suspended. Regards Oliver