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

TOMOYO Linux Cross Reference
Linux/Documentation/ABI/testing/sysfs-devices-state_synced

Version: ~ [ linux-6.12-rc7 ] ~ [ linux-6.11.7 ] ~ [ linux-6.10.14 ] ~ [ linux-6.9.12 ] ~ [ linux-6.8.12 ] ~ [ linux-6.7.12 ] ~ [ linux-6.6.60 ] ~ [ linux-6.5.13 ] ~ [ linux-6.4.16 ] ~ [ linux-6.3.13 ] ~ [ linux-6.2.16 ] ~ [ linux-6.1.116 ] ~ [ linux-6.0.19 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.171 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.229 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.285 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.323 ] ~ [ 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.12 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

Diff markup

Differences between /Documentation/ABI/testing/sysfs-devices-state_synced (Architecture m68k) and /Documentation/ABI/testing/sysfs-devices-state_synced (Architecture sparc64)


  1 What:           /sys/devices/.../state_synced       1 What:           /sys/devices/.../state_synced
  2 Date:           May 2020                            2 Date:           May 2020
  3 Contact:        Saravana Kannan <saravanak@goog      3 Contact:        Saravana Kannan <saravanak@google.com>
  4 Description:                                        4 Description:
  5                 The /sys/devices/.../state_syn      5                 The /sys/devices/.../state_synced attribute is only present for
  6                 devices whose bus types or dri      6                 devices whose bus types or driver provides the .sync_state()
  7                 callback. The number read from      7                 callback. The number read from it (0 or 1) reflects the value
  8                 of the device's 'state_synced'      8                 of the device's 'state_synced' field. A value of 0 means the
  9                 .sync_state() callback hasn't       9                 .sync_state() callback hasn't been called yet. A value of 1
 10                 means the .sync_state() callba     10                 means the .sync_state() callback has been called.
 11                                                    11 
 12                 Generally, if a device has syn     12                 Generally, if a device has sync_state() support and has some of
 13                 the resources it provides enab     13                 the resources it provides enabled at the time the kernel starts
 14                 (Eg: enabled by hardware reset     14                 (Eg: enabled by hardware reset or bootloader or anything that
 15                 run before the kernel starts),     15                 run before the kernel starts), then it'll keep those resources
 16                 enabled and in a state that's      16                 enabled and in a state that's compatible with the state they
 17                 were in at the start of the ke     17                 were in at the start of the kernel. The device will stop doing
 18                 this only when the sync_state(     18                 this only when the sync_state() callback has been called --
 19                 which happens only when all it     19                 which happens only when all its consumer devices are registered
 20                 and have probed successfully.      20                 and have probed successfully. Resources that were left disabled
 21                 at the time the kernel starts      21                 at the time the kernel starts are not affected or limited in
 22                 any way by sync_state() callba     22                 any way by sync_state() callbacks.
 23                                                    23 
 24                 Writing "1" to this file will      24                 Writing "1" to this file will force a call to the device's
 25                 sync_state() function if it ha     25                 sync_state() function if it hasn't been called already. The
 26                 sync_state() call happens inde     26                 sync_state() call happens independent of the state of the
 27                 consumer devices.                  27                 consumer devices.
 28                                                    28 
 29                                                    29 
                                                      

~ [ 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