[lkml]   [2017]   [Sep]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectUnderstanding suspend() vs suspend_late() for I2c devices
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?



 \ /
  Last update: 2017-09-19 19:36    [W:0.100 / U:3.820 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site