linux-kernel - Re: Understanding suspend() vs suspend

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 Sep 2017 22:30:37 +0200
From:   "Rafael J. Wysocki" <rjw@...ysocki.net>
To:     Rajat Jain <rajatja@...gle.com>
Cc:     "Wysocki, Rafael J" <rafael.j.wysocki@...el.com>,
        Len Brown <len.brown@...el.com>, Pavel Machek <pavel@....cz>,
        linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-i2c@...r.kernel.org,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Jarkko Nikula <jarkko.nikula@...ux.intel.com>,
        Mika Westerberg <mika.westerberg@...ux.intel.com>,
        Wolfram Sang <wsa@...-dreams.de>,
        Furquan Shaikh <furquan@...gle.com>,
        Rajat Jain <rajatxjain@...il.com>
Subject: Re: Understanding suspend() vs suspend_late() for I2c devices

On Tuesday, September 19, 2017 7:35:18 PM CEST Rajat Jain wrote:
> Hello folks,
> 
> I'm trying to understand the valid expectations from i2c drivers
> standpoint, from suspend() callback vs suspend_late() callback. The
> Documentation/power/devices.txt states that:
> 
> ==================================================
> For a number of devices it is convenient to split suspend into the
> "quiesce device" and "save device state" phases, in which cases
> suspend_late is meant to do the latter.
> ==================================================
> 
> 1) So it seems that it is fair expectation from a driver, to be able
> to access its own device and its registers in
> suspend_late()/resume_early() call backs?
> 
> 2) For the drivers that provide a controller to a bus (e.g.
> i2c_adapter drivers), is it correct that they should make sure that
> bus operation continues to stay OK even after their suspend() callback
> is executed?(This is because the drivers for the downstream devices -
> eg i2c_client drivers may want to talk to their device in *their*
> suspend_late() callbacks). So bus operations should be suspended by
> the adapter drivers only in their suspend_late() callback routines,
> and not suspend() routines?

Basically, yes, although there seems to be quite a bit of confusion around
that in i2c.

Generally speaking, a parent (or a supplier) device can only be fully
suspended if all of its child (or consumer) devices already have been
fully suspended.

Accordingly, it is better to suspend all of the bus controllers in the
"late suspend" phase and resume them in the "early resume" one.  Then, the
dependent devices can be suspended either in the "suspend" or in the
"late suspend" phase and the PM core should get the dependencies right
(and analogously for resume).

Thanks,
Rafael