Lines Matching full:in

1 Rules on how to access information in sysfs
10 To minimize the risk of breaking users of sysfs, which are in most cases
24     implementation details in its own API. Therefore it is not better than
26     Also, it is not actively maintained, in the sense of reflecting the
29     violates many of the rules in this document.
40     interfaces, and such that you can rely on in userspace. Everything is
43     applications that look for devices in sysfs.
49       - identical to the DEVPATH value in the event sent from the kernel
51       - the unique key to the device at that point in time
59       - using or exposing symlink values as elements in a devpath string
60         is a bug in the application
65       - applications need to handle spaces and characters like ``!`` in
81         driver; copying the driver value in a child device context is a
82         bug in the application
86       - the files in the device directory or files below subdirectories
89         like the "device"-link, is a bug in the application
102 - Hierarchy in a single device tree
103     There is only one valid place in sysfs where hierarchy can be examined
105     It is planned that all device directories will end up in the tree
119     The devices belonging to a subsystem will create a symlink in the
129     ``/sys/block`` and ``/sys/class/block`` are not interchangeable is a bug in
135     at the same level, never in a hierarchy. Assuming the block subsystem to
136     contain only disks and not partition devices in the same flat list is
137     a bug in the application.
141     for the old layout, where class devices are not created in
143     device directory does not end in ``/sys/devices/``, you can use the
144     "device"-link to find the parent devices in ``/sys/devices/``, That is the
145     single valid use of the "device"-link; it must never appear in any
147     a device in ``/sys/devices/`` is a bug in the application.
148     Accessing ``/sys/class/net/eth0/device`` is a bug in the application.
152     that class devices are not created in ``/sys/devices.`` If a device
154     may be used to find the child devices in ``/sys/class.`` That is the single
155     valid use of these links; they must never appear in any path as an
157     real child device directories in the ``/sys/devices`` tree is a bug in
161     directories live in ``/sys/devices.``
164     Never depend on a specific parent device position in the devpath,
170     access the chain of parents is a bug in the application.
176     In general, failures to read or write sysfs device attributes shall
187     to error codes result in user-space breakage, it will be fixed, or the
191     the attribute files to remain consistent in the absence of a version
192     attribute change in the context of a given attribute.