€•¼à      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ+/translations/zh_CN/admin-guide/sysfs-rules”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ+/translations/zh_TW/admin-guide/sysfs-rules”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ+/translations/it_IT/admin-guide/sysfs-rules”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ+/translations/ja_JP/admin-guide/sysfs-rules”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ+/translations/ko_KR/admin-guide/sysfs-rules”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒPortuguese (Brazilian)”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ+/translations/pt_BR/admin-guide/sysfs-rules”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh–sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ+/translations/sp_SP/admin-guide/sysfs-rules”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ+Rules on how to access information in sysfs”h]”hŒ+Rules on how to access information in sysfs”…””}”(hh¼h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhh·h²hh³ŒE/var/lib/git/docbuild/linux/Documentation/admin-guide/sysfs-rules.rst”h´KubhŒ	paragraph”“”)”}”(hXJ  The kernel-exported sysfs exports internal kernel implementation details
and depends on internal kernel structures and layout. It is agreed upon
by the kernel developers that the Linux kernel does not provide a stable
internal API. Therefore, there are aspects of the sysfs interface that
may not be stable across kernel releases.”h]”hXJ  The kernel-exported sysfs exports internal kernel implementation details
and depends on internal kernel structures and layout. It is agreed upon
by the kernel developers that the Linux kernel does not provide a stable
internal API. Therefore, there are aspects of the sysfs interface that
may not be stable across kernel releases.”…””}”(hhÍh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khh·h²hubhÌ)”}”(hXª  To minimize the risk of breaking users of sysfs, which are in most cases
low-level userspace applications, with a new kernel release, the users
of sysfs must follow some rules to use an as-abstract-as-possible way to
access this filesystem. The current udev and HAL programs already
implement this and users are encouraged to plug, if possible, into the
abstractions these programs provide instead of accessing sysfs directly.”h]”hXª  To minimize the risk of breaking users of sysfs, which are in most cases
low-level userspace applications, with a new kernel release, the users
of sysfs must follow some rules to use an as-abstract-as-possible way to
access this filesystem. The current udev and HAL programs already
implement this and users are encouraged to plug, if possible, into the
abstractions these programs provide instead of accessing sysfs directly.”…””}”(hhÛh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K
hh·h²hubhÌ)”}”(hŒ­But if you really do want or need to access sysfs directly, please follow
the following rules and then your programs should work with future
versions of the sysfs interface.”h]”hŒ­But if you really do want or need to access sysfs directly, please follow
the following rules and then your programs should work with future
versions of the sysfs interface.”…””}”(hhéh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khh·h²hubhŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hX  Do not use libsysfs
  It makes assumptions about sysfs which are not true. Its API does not
  offer any abstraction, it exposes all the kernel driver-core
  implementation details in its own API. Therefore it is not better than
  reading directories and opening the files yourself.
  Also, it is not actively maintained, in the sense of reflecting the
  current kernel development. The goal of providing a stable interface
  to sysfs has failed; it causes more problems than it solves. It
  violates many of the rules in this document.
”h]”hŒdefinition_list”“”)”}”(hhh]”hŒdefinition_list_item”“”)”}”(hX  Do not use libsysfs
It makes assumptions about sysfs which are not true. Its API does not
offer any abstraction, it exposes all the kernel driver-core
implementation details in its own API. Therefore it is not better than
reading directories and opening the files yourself.
Also, it is not actively maintained, in the sense of reflecting the
current kernel development. The goal of providing a stable interface
to sysfs has failed; it causes more problems than it solves. It
violates many of the rules in this document.
”h]”(hŒterm”“”)”}”(hŒDo not use libsysfs”h]”hŒDo not use libsysfs”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´Khj	  ubhŒ
definition”“”)”}”(hhh]”hÌ)”}”(hXó  It makes assumptions about sysfs which are not true. Its API does not
offer any abstraction, it exposes all the kernel driver-core
implementation details in its own API. Therefore it is not better than
reading directories and opening the files yourself.
Also, it is not actively maintained, in the sense of reflecting the
current kernel development. The goal of providing a stable interface
to sysfs has failed; it causes more problems than it solves. It
violates many of the rules in this document.”h]”hXó  It makes assumptions about sysfs which are not true. Its API does not
offer any abstraction, it exposes all the kernel driver-core
implementation details in its own API. Therefore it is not better than
reading directories and opening the files yourself.
Also, it is not actively maintained, in the sense of reflecting the
current kernel development. The goal of providing a stable interface
to sysfs has failed; it causes more problems than it solves. It
violates many of the rules in this document.”…””}”(hj"  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´Khj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hhþubah}”(h]”h ]”h"]”h$]”h&]”uh1hühhùh²hh³Nh´Nubhý)”}”(hXq  sysfs is always at ``/sys``
  Parsing ``/proc/mounts`` is a waste of time. Other mount points are a
  system configuration bug you should not try to solve. For test cases,
  possibly support a ``SYSFS_PATH`` environment variable to overwrite the
  application's behavior, but never try to search for sysfs. Never try
  to mount it, if you are not an early boot script.
”h]”j  )”}”(hhh]”j  )”}”(hXg  sysfs is always at ``/sys``
Parsing ``/proc/mounts`` is a waste of time. Other mount points are a
system configuration bug you should not try to solve. For test cases,
possibly support a ``SYSFS_PATH`` environment variable to overwrite the
application's behavior, but never try to search for sysfs. Never try
to mount it, if you are not an early boot script.
”h]”(j  )”}”(hŒsysfs is always at ``/sys``”h]”(hŒsysfs is always at ”…””}”(hjS  h²hh³Nh´NubhŒliteral”“”)”}”(hŒ``/sys``”h]”hŒ/sys”…””}”(hj]  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjS  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´K$hjO  ubj  )”}”(hhh]”hÌ)”}”(hXJ  Parsing ``/proc/mounts`` is a waste of time. Other mount points are a
system configuration bug you should not try to solve. For test cases,
possibly support a ``SYSFS_PATH`` environment variable to overwrite the
application's behavior, but never try to search for sysfs. Never try
to mount it, if you are not an early boot script.”h]”(hŒParsing ”…””}”(hjt  h²hh³Nh´Nubj\  )”}”(hŒ``/proc/mounts``”h]”hŒ/proc/mounts”…””}”(hj|  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjt  ubhŒ‡ is a waste of time. Other mount points are a
system configuration bug you should not try to solve. For test cases,
possibly support a ”…””}”(hjt  h²hh³Nh´Nubj\  )”}”(hŒ``SYSFS_PATH``”h]”hŒ
SYSFS_PATH”…””}”(hjŽ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjt  ubhŒŸ environment variable to overwrite the
applicationâ€™s behavior, but never try to search for sysfs. Never try
to mount it, if you are not an early boot script.”…””}”(hjt  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K hjq  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hjO  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´K$hjL  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hjH  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hühhùh²hh³Nh´Nubhý)”}”(hX)	  devices are only "devices"
  There is no such thing like class-, bus-, physical devices,
  interfaces, and such that you can rely on in userspace. Everything is
  just simply a "device". Class-, bus-, physical, ... types are just
  kernel implementation details which should not be expected by
  applications that look for devices in sysfs.

  The properties of a device are:

  - devpath (``/devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.0``)

    - identical to the DEVPATH value in the event sent from the kernel
      at device creation and removal
    - the unique key to the device at that point in time
    - the kernel's path to the device directory without the leading
      ``/sys``, and always starting with a slash
    - all elements of a devpath must be real directories. Symlinks
      pointing to /sys/devices must always be resolved to their real
      target and the target path must be used to access the device.
      That way the devpath to the device matches the devpath of the
      kernel used at event time.
    - using or exposing symlink values as elements in a devpath string
      is a bug in the application

  - kernel name (``sda``, ``tty``, ``0000:00:1f.2``, ...)

    - a directory name, identical to the last element of the devpath
    - applications need to handle spaces and characters like ``!`` in
      the name

  - subsystem (``block``, ``tty``, ``pci``, ...)

    - simple string, never a path or a link
    - retrieved by reading the "subsystem"-link and using only the
      last element of the target path

  - driver (``tg3``, ``ata_piix``, ``uhci_hcd``)

    - a simple string, which may contain spaces, never a path or a
      link
    - it is retrieved by reading the "driver"-link and using only the
      last element of the target path
    - devices which do not have "driver"-link just do not have a
      driver; copying the driver value in a child device context is a
      bug in the application

  - attributes

    - the files in the device directory or files below subdirectories
      of the same device directory
    - accessing attributes reached by a symlink pointing to another device,
      like the "device"-link, is a bug in the application

  Everything else is just a kernel driver-core implementation detail
  that should not be assumed to be stable across kernel releases.
”h]”j  )”}”(hhh]”j  )”}”(hXÕ  devices are only "devices"
There is no such thing like class-, bus-, physical devices,
interfaces, and such that you can rely on in userspace. Everything is
just simply a "device". Class-, bus-, physical, ... types are just
kernel implementation details which should not be expected by
applications that look for devices in sysfs.

The properties of a device are:

- devpath (``/devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.0``)

  - identical to the DEVPATH value in the event sent from the kernel
    at device creation and removal
  - the unique key to the device at that point in time
  - the kernel's path to the device directory without the leading
    ``/sys``, and always starting with a slash
  - all elements of a devpath must be real directories. Symlinks
    pointing to /sys/devices must always be resolved to their real
    target and the target path must be used to access the device.
    That way the devpath to the device matches the devpath of the
    kernel used at event time.
  - using or exposing symlink values as elements in a devpath string
    is a bug in the application

- kernel name (``sda``, ``tty``, ``0000:00:1f.2``, ...)

  - a directory name, identical to the last element of the devpath
  - applications need to handle spaces and characters like ``!`` in
    the name

- subsystem (``block``, ``tty``, ``pci``, ...)

  - simple string, never a path or a link
  - retrieved by reading the "subsystem"-link and using only the
    last element of the target path

- driver (``tg3``, ``ata_piix``, ``uhci_hcd``)

  - a simple string, which may contain spaces, never a path or a
    link
  - it is retrieved by reading the "driver"-link and using only the
    last element of the target path
  - devices which do not have "driver"-link just do not have a
    driver; copying the driver value in a child device context is a
    bug in the application

- attributes

  - the files in the device directory or files below subdirectories
    of the same device directory
  - accessing attributes reached by a symlink pointing to another device,
    like the "device"-link, is a bug in the application

Everything else is just a kernel driver-core implementation detail
that should not be assumed to be stable across kernel releases.
”h]”(j  )”}”(hŒdevices are only "devices"”h]”hŒdevices are only â€œdevicesâ€”…””}”(hjÉ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´K\hjÅ  ubj  )”}”(hhh]”(hÌ)”}”(hX/  There is no such thing like class-, bus-, physical devices,
interfaces, and such that you can rely on in userspace. Everything is
just simply a "device". Class-, bus-, physical, ... types are just
kernel implementation details which should not be expected by
applications that look for devices in sysfs.”h]”hX3  There is no such thing like class-, bus-, physical devices,
interfaces, and such that you can rely on in userspace. Everything is
just simply a â€œdeviceâ€. Class-, bus-, physical, ... types are just
kernel implementation details which should not be expected by
applications that look for devices in sysfs.”…””}”(hjÚ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K'hj×  ubhÌ)”}”(hŒThe properties of a device are:”h]”hŒThe properties of a device are:”…””}”(hjè  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K-hj×  ubhø)”}”(hhh]”(hý)”}”(hXÅ  devpath (``/devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.0``)

- identical to the DEVPATH value in the event sent from the kernel
  at device creation and removal
- the unique key to the device at that point in time
- the kernel's path to the device directory without the leading
  ``/sys``, and always starting with a slash
- all elements of a devpath must be real directories. Symlinks
  pointing to /sys/devices must always be resolved to their real
  target and the target path must be used to access the device.
  That way the devpath to the device matches the devpath of the
  kernel used at event time.
- using or exposing symlink values as elements in a devpath string
  is a bug in the application
”h]”(hÌ)”}”(hŒ?devpath (``/devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.0``)”h]”(hŒ	devpath (”…””}”(hjý  h²hh³Nh´Nubj\  )”}”(hŒ5``/devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.0``”h]”hŒ1/devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.0”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjý  ubhŒ)”…””}”(hjý  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K/hjù  ubhø)”}”(hhh]”(hý)”}”(hŒ_identical to the DEVPATH value in the event sent from the kernel
at device creation and removal”h]”hÌ)”}”(hŒ_identical to the DEVPATH value in the event sent from the kernel
at device creation and removal”h]”hŒ_identical to the DEVPATH value in the event sent from the kernel
at device creation and removal”…””}”(hj$  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K1hj   ubah}”(h]”h ]”h"]”h$]”h&]”uh1hühj  ubhý)”}”(hŒ2the unique key to the device at that point in time”h]”hÌ)”}”(hj:  h]”hŒ2the unique key to the device at that point in time”…””}”(hj<  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K3hj8  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hühj  ubhý)”}”(hŒhthe kernel's path to the device directory without the leading
``/sys``, and always starting with a slash”h]”hÌ)”}”(hŒhthe kernel's path to the device directory without the leading
``/sys``, and always starting with a slash”h]”(hŒ@the kernelâ€™s path to the device directory without the leading
”…””}”(hjS  h²hh³Nh´Nubj\  )”}”(hŒ``/sys``”h]”hŒ/sys”…””}”(hj[  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjS  ubhŒ", and always starting with a slash”…””}”(hjS  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K4hjO  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hühj  ubhý)”}”(hX  all elements of a devpath must be real directories. Symlinks
pointing to /sys/devices must always be resolved to their real
target and the target path must be used to access the device.
That way the devpath to the device matches the devpath of the
kernel used at event time.”h]”hÌ)”}”(hX  all elements of a devpath must be real directories. Symlinks
pointing to /sys/devices must always be resolved to their real
target and the target path must be used to access the device.
That way the devpath to the device matches the devpath of the
kernel used at event time.”h]”hX  all elements of a devpath must be real directories. Symlinks
pointing to /sys/devices must always be resolved to their real
target and the target path must be used to access the device.
That way the devpath to the device matches the devpath of the
kernel used at event time.”…””}”(hj}  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K6hjy  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hühj  ubhý)”}”(hŒ]using or exposing symlink values as elements in a devpath string
is a bug in the application
”h]”hÌ)”}”(hŒ\using or exposing symlink values as elements in a devpath string
is a bug in the application”h]”hŒ\using or exposing symlink values as elements in a devpath string
is a bug in the application”…””}”(hj•  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K;hj‘  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hühj  ubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1h÷h³hÊh´K1hjù  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hühjö  ubhý)”}”(hŒÅkernel name (``sda``, ``tty``, ``0000:00:1f.2``, ...)

- a directory name, identical to the last element of the devpath
- applications need to handle spaces and characters like ``!`` in
  the name
”h]”(hÌ)”}”(hŒ5kernel name (``sda``, ``tty``, ``0000:00:1f.2``, ...)”h]”(hŒkernel name (”…””}”(hj»  h²hh³Nh´Nubj\  )”}”(hŒ``sda``”h]”hŒsda”…””}”(hjÃ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hj»  ubhŒ, ”…””}”(hj»  h²hh³Nh´Nubj\  )”}”(hŒ``tty``”h]”hŒtty”…””}”(hjÕ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hj»  ubhŒ, ”…””}”hj»  sbj\  )”}”(hŒ``0000:00:1f.2``”h]”hŒ0000:00:1f.2”…””}”(hjç  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hj»  ubhŒ, ...)”…””}”(hj»  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K>hj·  ubhø)”}”(hhh]”(hý)”}”(hŒ>a directory name, identical to the last element of the devpath”h]”hÌ)”}”(hj  h]”hŒ>a directory name, identical to the last element of the devpath”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K@hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hühjÿ  ubhý)”}”(hŒIapplications need to handle spaces and characters like ``!`` in
the name
”h]”hÌ)”}”(hŒHapplications need to handle spaces and characters like ``!`` in
the name”h]”(hŒ7applications need to handle spaces and characters like ”…””}”(hj  h²hh³Nh´Nubj\  )”}”(hŒ``!``”h]”hŒ!”…””}”(hj%  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hj  ubhŒ in
the name”…””}”(hj  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KAhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hühjÿ  ubeh}”(h]”h ]”h"]”h$]”h&]”j¯  j°  uh1h÷h³hÊh´K@hj·  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hühjö  ubhý)”}”(hŒ·subsystem (``block``, ``tty``, ``pci``, ...)

- simple string, never a path or a link
- retrieved by reading the "subsystem"-link and using only the
  last element of the target path
”h]”(hÌ)”}”(hŒ,subsystem (``block``, ``tty``, ``pci``, ...)”h]”(hŒsubsystem (”…””}”(hjS  h²hh³Nh´Nubj\  )”}”(hŒ	``block``”h]”hŒblock”…””}”(hj[  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjS  ubhŒ, ”…””}”(hjS  h²hh³Nh´Nubj\  )”}”(hŒ``tty``”h]”hŒtty”…””}”(hjm  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjS  ubhŒ, ”…””}”hjS  sbj\  )”}”(hŒ``pci``”h]”hŒpci”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjS  ubhŒ, ...)”…””}”(hjS  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KDhjO  ubhø)”}”(hhh]”(hý)”}”(hŒ%simple string, never a path or a link”h]”hÌ)”}”(hjœ  h]”hŒ%simple string, never a path or a link”…””}”(hjž  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KFhjš  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hühj—  ubhý)”}”(hŒ]retrieved by reading the "subsystem"-link and using only the
last element of the target path
”h]”hÌ)”}”(hŒ\retrieved by reading the "subsystem"-link and using only the
last element of the target path”h]”hŒ`retrieved by reading the â€œsubsystemâ€-link and using only the
last element of the target path”…””}”(hjµ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KGhj±  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hühj—  ubeh}”(h]”h ]”h"]”h$]”h&]”j¯  j°  uh1h÷h³hÊh´KFhjO  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hühjö  ubhý)”}”(hXp  driver (``tg3``, ``ata_piix``, ``uhci_hcd``)

- a simple string, which may contain spaces, never a path or a
  link
- it is retrieved by reading the "driver"-link and using only the
  last element of the target path
- devices which do not have "driver"-link just do not have a
  driver; copying the driver value in a child device context is a
  bug in the application
”h]”(hÌ)”}”(hŒ,driver (``tg3``, ``ata_piix``, ``uhci_hcd``)”h]”(hŒdriver (”…””}”(hjÙ  h²hh³Nh´Nubj\  )”}”(hŒ``tg3``”h]”hŒtg3”…””}”(hjá  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjÙ  ubhŒ, ”…””}”(hjÙ  h²hh³Nh´Nubj\  )”}”(hŒ``ata_piix``”h]”hŒata_piix”…””}”(hjó  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjÙ  ubhŒ, ”…””}”hjÙ  sbj\  )”}”(hŒ``uhci_hcd``”h]”hŒuhci_hcd”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjÙ  ubhŒ)”…””}”(hjÙ  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KJhjÕ  ubhø)”}”(hhh]”(hý)”}”(hŒAa simple string, which may contain spaces, never a path or a
link”h]”hÌ)”}”(hŒAa simple string, which may contain spaces, never a path or a
link”h]”hŒAa simple string, which may contain spaces, never a path or a
link”…””}”(hj$  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KLhj   ubah}”(h]”h ]”h"]”h$]”h&]”uh1hühj  ubhý)”}”(hŒ_it is retrieved by reading the "driver"-link and using only the
last element of the target path”h]”hÌ)”}”(hŒ_it is retrieved by reading the "driver"-link and using only the
last element of the target path”h]”hŒcit is retrieved by reading the â€œdriverâ€-link and using only the
last element of the target path”…””}”(hj<  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KNhj8  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hühj  ubhý)”}”(hŒ’devices which do not have "driver"-link just do not have a
driver; copying the driver value in a child device context is a
bug in the application
”h]”hÌ)”}”(hŒ‘devices which do not have "driver"-link just do not have a
driver; copying the driver value in a child device context is a
bug in the application”h]”hŒ•devices which do not have â€œdriverâ€-link just do not have a
driver; copying the driver value in a child device context is a
bug in the application”…””}”(hjT  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KPhjP  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hühj  ubeh}”(h]”h ]”h"]”h$]”h&]”j¯  j°  uh1h÷h³hÊh´KLhjÕ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hühjö  ubhý)”}”(hŒëattributes

- the files in the device directory or files below subdirectories
  of the same device directory
- accessing attributes reached by a symlink pointing to another device,
  like the "device"-link, is a bug in the application
”h]”(hÌ)”}”(hŒ
attributes”h]”hŒ
attributes”…””}”(hjx  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KThjt  ubhø)”}”(hhh]”(hý)”}”(hŒ\the files in the device directory or files below subdirectories
of the same device directory”h]”hÌ)”}”(hŒ\the files in the device directory or files below subdirectories
of the same device directory”h]”hŒ\the files in the device directory or files below subdirectories
of the same device directory”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KVhj‰  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hühj†  ubhý)”}”(hŒzaccessing attributes reached by a symlink pointing to another device,
like the "device"-link, is a bug in the application
”h]”hÌ)”}”(hŒyaccessing attributes reached by a symlink pointing to another device,
like the "device"-link, is a bug in the application”h]”hŒ}accessing attributes reached by a symlink pointing to another device,
like the â€œdeviceâ€-link, is a bug in the application”…””}”(hj¥  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KXhj¡  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hühj†  ubeh}”(h]”h ]”h"]”h$]”h&]”j¯  j°  uh1h÷h³hÊh´KVhjt  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hühjö  ubeh}”(h]”h ]”h"]”h$]”h&]”j¯  j°  uh1h÷h³hÊh´K/hj×  ubhÌ)”}”(hŒ‚Everything else is just a kernel driver-core implementation detail
that should not be assumed to be stable across kernel releases.”h]”hŒ‚Everything else is just a kernel driver-core implementation detail
that should not be assumed to be stable across kernel releases.”…””}”(hjË  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K[hj×  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hjÅ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´K\hjÂ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj¾  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hühhùh²hh³Nh´Nubhý)”}”(hX»  Properties of parent devices never belong into a child device.
  Always look at the parent devices themselves for determining device
  context properties. If the device ``eth0`` or ``sda`` does not have a
  "driver"-link, then this device does not have a driver. Its value is empty.
  Never copy any property of the parent-device into a child-device. Parent
  device properties may change dynamically without any notice to the
  child device.
”h]”j  )”}”(hhh]”j  )”}”(hX¯  Properties of parent devices never belong into a child device.
Always look at the parent devices themselves for determining device
context properties. If the device ``eth0`` or ``sda`` does not have a
"driver"-link, then this device does not have a driver. Its value is empty.
Never copy any property of the parent-device into a child-device. Parent
device properties may change dynamically without any notice to the
child device.
”h]”(j  )”}”(hŒ>Properties of parent devices never belong into a child device.”h]”hŒ>Properties of parent devices never belong into a child device.”…””}”(hjü  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´Kdhjø  ubj  )”}”(hhh]”hÌ)”}”(hXo  Always look at the parent devices themselves for determining device
context properties. If the device ``eth0`` or ``sda`` does not have a
"driver"-link, then this device does not have a driver. Its value is empty.
Never copy any property of the parent-device into a child-device. Parent
device properties may change dynamically without any notice to the
child device.”h]”(hŒfAlways look at the parent devices themselves for determining device
context properties. If the device ”…””}”(hj  h²hh³Nh´Nubj\  )”}”(hŒ``eth0``”h]”hŒeth0”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hj  ubhŒ or ”…””}”(hj  h²hh³Nh´Nubj\  )”}”(hŒ``sda``”h]”hŒsda”…””}”(hj'  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hj  ubhŒú does not have a
â€œdriverâ€-link, then this device does not have a driver. Its value is empty.
Never copy any property of the parent-device into a child-device. Parent
device properties may change dynamically without any notice to the
child device.”…””}”(hj  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K_hj
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hjø  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´Kdhjõ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hjñ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hühhùh²hh³Nh´Nubhý)”}”(hŒîHierarchy in a single device tree
  There is only one valid place in sysfs where hierarchy can be examined
  and this is below: ``/sys/devices.``
  It is planned that all device directories will end up in the tree
  below this directory.
”h]”j  )”}”(hhh]”j  )”}”(hŒæHierarchy in a single device tree
There is only one valid place in sysfs where hierarchy can be examined
and this is below: ``/sys/devices.``
It is planned that all device directories will end up in the tree
below this directory.
”h]”(j  )”}”(hŒ!Hierarchy in a single device tree”h]”hŒ!Hierarchy in a single device tree”…””}”(hjb  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´Kjhj^  ubj  )”}”(hhh]”hÌ)”}”(hŒÃThere is only one valid place in sysfs where hierarchy can be examined
and this is below: ``/sys/devices.``
It is planned that all device directories will end up in the tree
below this directory.”h]”(hŒZThere is only one valid place in sysfs where hierarchy can be examined
and this is below: ”…””}”(hjs  h²hh³Nh´Nubj\  )”}”(hŒ``/sys/devices.``”h]”hŒ/sys/devices.”…””}”(hj{  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjs  ubhŒX
It is planned that all device directories will end up in the tree
below this directory.”…””}”(hjs  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kghjp  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj^  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´Kjhj[  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hjW  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hühhùh²hh³Nh´Nubhý)”}”(hXÖ  Classification by subsystem
  There are currently three places for classification of devices:
  ``/sys/block,`` ``/sys/class`` and ``/sys/bus.`` It is planned that these will
  not contain any device directories themselves, but only flat lists of
  symlinks pointing to the unified ``/sys/devices`` tree.
  All three places have completely different rules on how to access
  device information. It is planned to merge all three
  classification directories into one place at ``/sys/subsystem``,
  following the layout of the bus directories. All buses and
  classes, including the converted block subsystem, will show up
  there.
  The devices belonging to a subsystem will create a symlink in the
  "devices" directory at ``/sys/subsystem/<name>/devices``,

  If ``/sys/subsystem`` exists, ``/sys/bus``, ``/sys/class`` and ``/sys/block``
  can be ignored. If it does not exist, you always have to scan all three
  places, as the kernel is free to move a subsystem from one place to
  the other, as long as the devices are still reachable by the same
  subsystem name.

  Assuming ``/sys/class/<subsystem>`` and ``/sys/bus/<subsystem>``, or
  ``/sys/block`` and ``/sys/class/block`` are not interchangeable is a bug in
  the application.
”h]”j  )”}”(hhh]”j  )”}”(hX®  Classification by subsystem
There are currently three places for classification of devices:
``/sys/block,`` ``/sys/class`` and ``/sys/bus.`` It is planned that these will
not contain any device directories themselves, but only flat lists of
symlinks pointing to the unified ``/sys/devices`` tree.
All three places have completely different rules on how to access
device information. It is planned to merge all three
classification directories into one place at ``/sys/subsystem``,
following the layout of the bus directories. All buses and
classes, including the converted block subsystem, will show up
there.
The devices belonging to a subsystem will create a symlink in the
"devices" directory at ``/sys/subsystem/<name>/devices``,

If ``/sys/subsystem`` exists, ``/sys/bus``, ``/sys/class`` and ``/sys/block``
can be ignored. If it does not exist, you always have to scan all three
places, as the kernel is free to move a subsystem from one place to
the other, as long as the devices are still reachable by the same
subsystem name.

Assuming ``/sys/class/<subsystem>`` and ``/sys/bus/<subsystem>``, or
``/sys/block`` and ``/sys/class/block`` are not interchangeable is a bug in
the application.
”h]”(j  )”}”(hŒClassification by subsystem”h]”hŒClassification by subsystem”…””}”(hj¶  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´K‚hj²  ubj  )”}”(hhh]”(hÌ)”}”(hXÁ  There are currently three places for classification of devices:
``/sys/block,`` ``/sys/class`` and ``/sys/bus.`` It is planned that these will
not contain any device directories themselves, but only flat lists of
symlinks pointing to the unified ``/sys/devices`` tree.
All three places have completely different rules on how to access
device information. It is planned to merge all three
classification directories into one place at ``/sys/subsystem``,
following the layout of the bus directories. All buses and
classes, including the converted block subsystem, will show up
there.
The devices belonging to a subsystem will create a symlink in the
"devices" directory at ``/sys/subsystem/<name>/devices``,”h]”(hŒ@There are currently three places for classification of devices:
”…””}”(hjÇ  h²hh³Nh´Nubj\  )”}”(hŒ``/sys/block,``”h]”hŒ/sys/block,”…””}”(hjÏ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjÇ  ubhŒ ”…””}”(hjÇ  h²hh³Nh´Nubj\  )”}”(hŒ``/sys/class``”h]”hŒ
/sys/class”…””}”(hjá  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjÇ  ubhŒ and ”…””}”(hjÇ  h²hh³Nh´Nubj\  )”}”(hŒ``/sys/bus.``”h]”hŒ	/sys/bus.”…””}”(hjó  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjÇ  ubhŒ† It is planned that these will
not contain any device directories themselves, but only flat lists of
symlinks pointing to the unified ”…””}”(hjÇ  h²hh³Nh´Nubj\  )”}”(hŒ``/sys/devices``”h]”hŒ/sys/devices”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjÇ  ubhŒ« tree.
All three places have completely different rules on how to access
device information. It is planned to merge all three
classification directories into one place at ”…””}”(hjÇ  h²hh³Nh´Nubj\  )”}”(hŒ``/sys/subsystem``”h]”hŒ/sys/subsystem”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjÇ  ubhŒà,
following the layout of the bus directories. All buses and
classes, including the converted block subsystem, will show up
there.
The devices belonging to a subsystem will create a symlink in the
â€œdevicesâ€ directory at ”…””}”(hjÇ  h²hh³Nh´Nubj\  )”}”(hŒ!``/sys/subsystem/<name>/devices``”h]”hŒ/sys/subsystem/<name>/devices”…””}”(hj)  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjÇ  ubhŒ,”…””}”(hjÇ  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KmhjÄ  ubhÌ)”}”(hX+  If ``/sys/subsystem`` exists, ``/sys/bus``, ``/sys/class`` and ``/sys/block``
can be ignored. If it does not exist, you always have to scan all three
places, as the kernel is free to move a subsystem from one place to
the other, as long as the devices are still reachable by the same
subsystem name.”h]”(hŒIf ”…””}”(hjA  h²hh³Nh´Nubj\  )”}”(hŒ``/sys/subsystem``”h]”hŒ/sys/subsystem”…””}”(hjI  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjA  ubhŒ	 exists, ”…””}”(hjA  h²hh³Nh´Nubj\  )”}”(hŒ``/sys/bus``”h]”hŒ/sys/bus”…””}”(hj[  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjA  ubhŒ, ”…””}”(hjA  h²hh³Nh´Nubj\  )”}”(hŒ``/sys/class``”h]”hŒ
/sys/class”…””}”(hjm  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjA  ubhŒ and ”…””}”(hjA  h²hh³Nh´Nubj\  )”}”(hŒ``/sys/block``”h]”hŒ
/sys/block”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjA  ubhŒÞ
can be ignored. If it does not exist, you always have to scan all three
places, as the kernel is free to move a subsystem from one place to
the other, as long as the devices are still reachable by the same
subsystem name.”…””}”(hjA  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KzhjÄ  ubhÌ)”}”(hŒ¡Assuming ``/sys/class/<subsystem>`` and ``/sys/bus/<subsystem>``, or
``/sys/block`` and ``/sys/class/block`` are not interchangeable is a bug in
the application.”h]”(hŒ	Assuming ”…””}”(hj—  h²hh³Nh´Nubj\  )”}”(hŒ``/sys/class/<subsystem>``”h]”hŒ/sys/class/<subsystem>”…””}”(hjŸ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hj—  ubhŒ and ”…””}”(hj—  h²hh³Nh´Nubj\  )”}”(hŒ``/sys/bus/<subsystem>``”h]”hŒ/sys/bus/<subsystem>”…””}”(hj±  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hj—  ubhŒ, or
”…””}”(hj—  h²hh³Nh´Nubj\  )”}”(hŒ``/sys/block``”h]”hŒ
/sys/block”…””}”(hjÃ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hj—  ubhŒ and ”…””}”hj—  sbj\  )”}”(hŒ``/sys/class/block``”h]”hŒ/sys/class/block”…””}”(hjÕ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hj—  ubhŒ5 are not interchangeable is a bug in
the application.”…””}”(hj—  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K€hjÄ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj²  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´K‚hj¯  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj«  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hühhùh²hh³Nh´Nubhý)”}”(hX;  Block
  The converted block subsystem at ``/sys/class/block`` or
  ``/sys/subsystem/block`` will contain the links for disks and partitions
  at the same level, never in a hierarchy. Assuming the block subsystem to
  contain only disks and not partition devices in the same flat list is
  a bug in the application.
”h]”j  )”}”(hhh]”j  )”}”(hX1  Block
The converted block subsystem at ``/sys/class/block`` or
``/sys/subsystem/block`` will contain the links for disks and partitions
at the same level, never in a hierarchy. Assuming the block subsystem to
contain only disks and not partition devices in the same flat list is
a bug in the application.
”h]”(j  )”}”(hŒBlock”h]”hŒBlock”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´K‰hj  ubj  )”}”(hhh]”hÌ)”}”(hX*  The converted block subsystem at ``/sys/class/block`` or
``/sys/subsystem/block`` will contain the links for disks and partitions
at the same level, never in a hierarchy. Assuming the block subsystem to
contain only disks and not partition devices in the same flat list is
a bug in the application.”h]”(hŒ!The converted block subsystem at ”…””}”(hj!  h²hh³Nh´Nubj\  )”}”(hŒ``/sys/class/block``”h]”hŒ/sys/class/block”…””}”(hj)  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hj!  ubhŒ or
”…””}”(hj!  h²hh³Nh´Nubj\  )”}”(hŒ``/sys/subsystem/block``”h]”hŒ/sys/subsystem/block”…””}”(hj;  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hj!  ubhŒÙ will contain the links for disks and partitions
at the same level, never in a hierarchy. Assuming the block subsystem to
contain only disks and not partition devices in the same flat list is
a bug in the application.”…””}”(hj!  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K…hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´K‰hj	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hühhùh²hh³Nh´Nubhý)”}”(hXY  "device"-link and <subsystem>:<kernel name>-links
  Never depend on the "device"-link. The "device"-link is a workaround
  for the old layout, where class devices are not created in
  ``/sys/devices/`` like the bus devices. If the link-resolving of a
  device directory does not end in ``/sys/devices/``, you can use the
  "device"-link to find the parent devices in ``/sys/devices/``, That is the
  single valid use of the "device"-link; it must never appear in any
  path as an element. Assuming the existence of the "device"-link for
  a device in ``/sys/devices/`` is a bug in the application.
  Accessing ``/sys/class/net/eth0/device`` is a bug in the application.

  Never depend on the class-specific links back to the ``/sys/class``
  directory.  These links are also a workaround for the design mistake
  that class devices are not created in ``/sys/devices.`` If a device
  directory does not contain directories for child devices, these links
  may be used to find the child devices in ``/sys/class.`` That is the single
  valid use of these links; they must never appear in any path as an
  element. Assuming the existence of these links for devices which are
  real child device directories in the ``/sys/devices`` tree is a bug in
  the application.

  It is planned to remove all these links when all class device
  directories live in ``/sys/devices.``
”h]”j  )”}”(hhh]”j  )”}”(hX1  "device"-link and <subsystem>:<kernel name>-links
Never depend on the "device"-link. The "device"-link is a workaround
for the old layout, where class devices are not created in
``/sys/devices/`` like the bus devices. If the link-resolving of a
device directory does not end in ``/sys/devices/``, you can use the
"device"-link to find the parent devices in ``/sys/devices/``, That is the
single valid use of the "device"-link; it must never appear in any
path as an element. Assuming the existence of the "device"-link for
a device in ``/sys/devices/`` is a bug in the application.
Accessing ``/sys/class/net/eth0/device`` is a bug in the application.

Never depend on the class-specific links back to the ``/sys/class``
directory.  These links are also a workaround for the design mistake
that class devices are not created in ``/sys/devices.`` If a device
directory does not contain directories for child devices, these links
may be used to find the child devices in ``/sys/class.`` That is the single
valid use of these links; they must never appear in any path as an
element. Assuming the existence of these links for devices which are
real child device directories in the ``/sys/devices`` tree is a bug in
the application.

It is planned to remove all these links when all class device
directories live in ``/sys/devices.``
”h]”(j  )”}”(hŒ1"device"-link and <subsystem>:<kernel name>-links”h]”hŒ5â€œdeviceâ€-link and <subsystem>:<kernel name>-links”…””}”(hjv  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´K¡hjr  ubj  )”}”(hhh]”(hÌ)”}”(hXY  Never depend on the "device"-link. The "device"-link is a workaround
for the old layout, where class devices are not created in
``/sys/devices/`` like the bus devices. If the link-resolving of a
device directory does not end in ``/sys/devices/``, you can use the
"device"-link to find the parent devices in ``/sys/devices/``, That is the
single valid use of the "device"-link; it must never appear in any
path as an element. Assuming the existence of the "device"-link for
a device in ``/sys/devices/`` is a bug in the application.
Accessing ``/sys/class/net/eth0/device`` is a bug in the application.”h]”(hŒˆNever depend on the â€œdeviceâ€-link. The â€œdeviceâ€-link is a workaround
for the old layout, where class devices are not created in
”…””}”(hj‡  h²hh³Nh´Nubj\  )”}”(hŒ``/sys/devices/``”h]”hŒ/sys/devices/”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hj‡  ubhŒS like the bus devices. If the link-resolving of a
device directory does not end in ”…””}”(hj‡  h²hh³Nh´Nubj\  )”}”(hŒ``/sys/devices/``”h]”hŒ/sys/devices/”…””}”(hj¡  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hj‡  ubhŒB, you can use the
â€œdeviceâ€-link to find the parent devices in ”…””}”(hj‡  h²hh³Nh´Nubj\  )”}”(hŒ``/sys/devices/``”h]”hŒ/sys/devices/”…””}”(hj³  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hj‡  ubhŒ©, That is the
single valid use of the â€œdeviceâ€-link; it must never appear in any
path as an element. Assuming the existence of the â€œdeviceâ€-link for
a device in ”…””}”(hj‡  h²hh³Nh´Nubj\  )”}”(hŒ``/sys/devices/``”h]”hŒ/sys/devices/”…””}”(hjÅ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hj‡  ubhŒ( is a bug in the application.
Accessing ”…””}”(hj‡  h²hh³Nh´Nubj\  )”}”(hŒ``/sys/class/net/eth0/device``”h]”hŒ/sys/class/net/eth0/device”…””}”(hj×  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hj‡  ubhŒ is a bug in the application.”…””}”(hj‡  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KŒhj„  ubhÌ)”}”(hX>  Never depend on the class-specific links back to the ``/sys/class``
directory.  These links are also a workaround for the design mistake
that class devices are not created in ``/sys/devices.`` If a device
directory does not contain directories for child devices, these links
may be used to find the child devices in ``/sys/class.`` That is the single
valid use of these links; they must never appear in any path as an
element. Assuming the existence of these links for devices which are
real child device directories in the ``/sys/devices`` tree is a bug in
the application.”h]”(hŒ5Never depend on the class-specific links back to the ”…””}”(hjï  h²hh³Nh´Nubj\  )”}”(hŒ``/sys/class``”h]”hŒ
/sys/class”…””}”(hj÷  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjï  ubhŒl
directory.  These links are also a workaround for the design mistake
that class devices are not created in ”…””}”(hjï  h²hh³Nh´Nubj\  )”}”(hŒ``/sys/devices.``”h]”hŒ/sys/devices.”…””}”(hj	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjï  ubhŒ| If a device
directory does not contain directories for child devices, these links
may be used to find the child devices in ”…””}”(hjï  h²hh³Nh´Nubj\  )”}”(hŒ``/sys/class.``”h]”hŒ/sys/class.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjï  ubhŒÁ That is the single
valid use of these links; they must never appear in any path as an
element. Assuming the existence of these links for devices which are
real child device directories in the ”…””}”(hjï  h²hh³Nh´Nubj\  )”}”(hŒ``/sys/devices``”h]”hŒ/sys/devices”…””}”(hj-  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjï  ubhŒ" tree is a bug in
the application.”…””}”(hjï  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K–hj„  ubhÌ)”}”(hŒcIt is planned to remove all these links when all class device
directories live in ``/sys/devices.``”h]”(hŒRIt is planned to remove all these links when all class device
directories live in ”…””}”(hjE  h²hh³Nh´Nubj\  )”}”(hŒ``/sys/devices.``”h]”hŒ/sys/devices.”…””}”(hjM  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hjE  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K hj„  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hjr  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´K¡hjo  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hjk  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hühhùh²hh³Nh´Nubhý)”}”(hX$  Position of devices along device chain can change.
  Never depend on a specific parent device position in the devpath,
  or the chain of parent devices. The kernel is free to insert devices into
  the chain. You must always request the parent device you are looking for
  by its subsystem value. You need to walk up the chain until you find
  the device that matches the expected subsystem. Depending on a specific
  position of a parent device or exposing relative paths using ``../`` to
  access the chain of parents is a bug in the application.
”h]”j  )”}”(hhh]”j  )”}”(hX  Position of devices along device chain can change.
Never depend on a specific parent device position in the devpath,
or the chain of parent devices. The kernel is free to insert devices into
the chain. You must always request the parent device you are looking for
by its subsystem value. You need to walk up the chain until you find
the device that matches the expected subsystem. Depending on a specific
position of a parent device or exposing relative paths using ``../`` to
access the chain of parents is a bug in the application.
”h]”(j  )”}”(hŒ2Position of devices along device chain can change.”h]”hŒ2Position of devices along device chain can change.”…””}”(hj„  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´Kªhj€  ubj  )”}”(hhh]”hÌ)”}”(hXâ  Never depend on a specific parent device position in the devpath,
or the chain of parent devices. The kernel is free to insert devices into
the chain. You must always request the parent device you are looking for
by its subsystem value. You need to walk up the chain until you find
the device that matches the expected subsystem. Depending on a specific
position of a parent device or exposing relative paths using ``../`` to
access the chain of parents is a bug in the application.”h]”(hXŸ  Never depend on a specific parent device position in the devpath,
or the chain of parent devices. The kernel is free to insert devices into
the chain. You must always request the parent device you are looking for
by its subsystem value. You need to walk up the chain until you find
the device that matches the expected subsystem. Depending on a specific
position of a parent device or exposing relative paths using ”…””}”(hj•  h²hh³Nh´Nubj\  )”}”(hŒ``../``”h]”hŒ../”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hj•  ubhŒ< to
access the chain of parents is a bug in the application.”…””}”(hj•  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K¤hj’  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj€  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´Kªhj}  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hjy  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hühhùh²hh³Nh´Nubhý)”}”(hXÄ  When reading and writing sysfs device attribute files, avoid dependency
  on specific error codes wherever possible. This minimizes coupling to
  the error handling implementation within the kernel.

  In general, failures to read or write sysfs device attributes shall
  propagate errors wherever possible. Common errors include, but are not
  limited to:

      ``-EIO``: The read or store operation is not supported, typically
      returned by the sysfs system itself if the read or store pointer
      is ``NULL``.

      ``-ENXIO``: The read or store operation failed

  Error codes will not be changed without good reason, and should a change
  to error codes result in user-space breakage, it will be fixed, or the
  the offending change will be reverted.

  Userspace applications can, however, expect the format and contents of
  the attribute files to remain consistent in the absence of a version
  attribute change in the context of a given attribute.”h]”j  )”}”(hhh]”j  )”}”(hX¦  When reading and writing sysfs device attribute files, avoid dependency
on specific error codes wherever possible. This minimizes coupling to
the error handling implementation within the kernel.

In general, failures to read or write sysfs device attributes shall
propagate errors wherever possible. Common errors include, but are not
limited to:

    ``-EIO``: The read or store operation is not supported, typically
    returned by the sysfs system itself if the read or store pointer
    is ``NULL``.

    ``-ENXIO``: The read or store operation failed

Error codes will not be changed without good reason, and should a change
to error codes result in user-space breakage, it will be fixed, or the
the offending change will be reverted.

Userspace applications can, however, expect the format and contents of
the attribute files to remain consistent in the absence of a version
attribute change in the context of a given attribute.”h]”(j  )”}”(hŒGWhen reading and writing sysfs device attribute files, avoid dependency”h]”hŒGWhen reading and writing sysfs device attribute files, avoid dependency”…””}”(hjØ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´K¿hjÔ  ubj  )”}”(hhh]”(hÌ)”}”(hŒzon specific error codes wherever possible. This minimizes coupling to
the error handling implementation within the kernel.”h]”hŒzon specific error codes wherever possible. This minimizes coupling to
the error handling implementation within the kernel.”…””}”(hjé  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K­hjæ  ubhÌ)”}”(hŒ–In general, failures to read or write sysfs device attributes shall
propagate errors wherever possible. Common errors include, but are not
limited to:”h]”hŒ–In general, failures to read or write sysfs device attributes shall
propagate errors wherever possible. Common errors include, but are not
limited to:”…””}”(hj÷  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K°hjæ  ubhŒblock_quote”“”)”}”(hŒÀ``-EIO``: The read or store operation is not supported, typically
returned by the sysfs system itself if the read or store pointer
is ``NULL``.

``-ENXIO``: The read or store operation failed
”h]”(hÌ)”}”(hŒ``-EIO``: The read or store operation is not supported, typically
returned by the sysfs system itself if the read or store pointer
is ``NULL``.”h]”(j\  )”}”(hŒ``-EIO``”h]”hŒ-EIO”…””}”(hj	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hj	  ubhŒ~: The read or store operation is not supported, typically
returned by the sysfs system itself if the read or store pointer
is ”…””}”(hj	  h²hh³Nh´Nubj\  )”}”(hŒ``NULL``”h]”hŒNULL”…””}”(hj!	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hj	  ubhŒ.”…””}”(hj	  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K´hj	  ubhÌ)”}”(hŒ.``-ENXIO``: The read or store operation failed”h]”(j\  )”}”(hŒ
``-ENXIO``”h]”hŒ-ENXIO”…””}”(hj=	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j[  hj9	  ubhŒ$: The read or store operation failed”…””}”(hj9	  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K¸hj	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j	  h³hÊh´K´hjæ  ubhÌ)”}”(hŒ¶Error codes will not be changed without good reason, and should a change
to error codes result in user-space breakage, it will be fixed, or the
the offending change will be reverted.”h]”hŒ¶Error codes will not be changed without good reason, and should a change
to error codes result in user-space breakage, it will be fixed, or the
the offending change will be reverted.”…””}”(hj[	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kºhjæ  ubhÌ)”}”(hŒÁUserspace applications can, however, expect the format and contents of
the attribute files to remain consistent in the absence of a version
attribute change in the context of a given attribute.”h]”hŒÁUserspace applications can, however, expect the format and contents of
the attribute files to remain consistent in the absence of a version
attribute change in the context of a given attribute.”…””}”(hji	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K¾hjæ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hjÔ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´K¿hjÑ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hjÍ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hühhùh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”j¯  j°  uh1h÷h³hÊh´Khh·h²hubeh}”(h]”Œ+rules-on-how-to-access-information-in-sysfs”ah ]”h"]”Œ+rules on how to access information in sysfs”ah$]”h&]”uh1hµhhh²hh³hÊh´Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”hÊuh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(hºNŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”Œentry”Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jÀ	  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”hÊŒ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”jš	  j—	  sŒ	nametypes”}”jš	  ‰sh}”j—	  h·sŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nh²hub.