~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

TOMOYO Linux Cross Reference
Linux/Documentation/power/drivers-testing.rst

Version: ~ [ linux-6.11.5 ] ~ [ linux-6.10.14 ] ~ [ linux-6.9.12 ] ~ [ linux-6.8.12 ] ~ [ linux-6.7.12 ] ~ [ linux-6.6.58 ] ~ [ linux-6.5.13 ] ~ [ linux-6.4.16 ] ~ [ linux-6.3.13 ] ~ [ linux-6.2.16 ] ~ [ linux-6.1.114 ] ~ [ linux-6.0.19 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.169 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.228 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.284 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.322 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.336 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.337 ] ~ [ linux-4.4.302 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.9 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

  1 ====================================================
  2 Testing suspend and resume support in device drivers
  3 ====================================================
  4 
  5         (C) 2007 Rafael J. Wysocki <rjw@sisk.pl>, GPL
  6 
  7 1. Preparing the test system
  8 ============================
  9 
 10 Unfortunately, to effectively test the support for the system-wide suspend and
 11 resume transitions in a driver, it is necessary to suspend and resume a fully
 12 functional system with this driver loaded.  Moreover, that should be done
 13 several times, preferably several times in a row, and separately for hibernation
 14 (aka suspend to disk or STD) and suspend to RAM (STR), because each of these
 15 cases involves slightly different operations and different interactions with
 16 the machine's BIOS.
 17 
 18 Of course, for this purpose the test system has to be known to suspend and
 19 resume without the driver being tested.  Thus, if possible, you should first
 20 resolve all suspend/resume-related problems in the test system before you start
 21 testing the new driver.  Please see Documentation/power/basic-pm-debugging.rst
 22 for more information about the debugging of suspend/resume functionality.
 23 
 24 2. Testing the driver
 25 =====================
 26 
 27 Once you have resolved the suspend/resume-related problems with your test system
 28 without the new driver, you are ready to test it:
 29 
 30 a) Build the driver as a module, load it and try the test modes of hibernation
 31    (see: Documentation/power/basic-pm-debugging.rst, 1).
 32 
 33 b) Load the driver and attempt to hibernate in the "reboot", "shutdown" and
 34    "platform" modes (see: Documentation/power/basic-pm-debugging.rst, 1).
 35 
 36 c) Compile the driver directly into the kernel and try the test modes of
 37    hibernation.
 38 
 39 d) Attempt to hibernate with the driver compiled directly into the kernel
 40    in the "reboot", "shutdown" and "platform" modes.
 41 
 42 e) Try the test modes of suspend (see:
 43    Documentation/power/basic-pm-debugging.rst, 2).  [As far as the STR tests are
 44    concerned, it should not matter whether or not the driver is built as a
 45    module.]
 46 
 47 f) Attempt to suspend to RAM using the s2ram tool with the driver loaded
 48    (see: Documentation/power/basic-pm-debugging.rst, 2).
 49 
 50 Each of the above tests should be repeated several times and the STD tests
 51 should be mixed with the STR tests.  If any of them fails, the driver cannot be
 52 regarded as suspend/resume-safe.

~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

kernel.org | git.kernel.org | LWN.net | Project Home | SVN repository | Mail admin

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

sflogo.php