Lines Matching full:device

41     just simply a "device". Class-, bus-, physical, ... types are just
45     The properties of a device are:
50         at device creation and removal
51       - the unique key to the device at that point in time
52       - the kernel's path to the device directory without the leading
56         target and the target path must be used to access the device.
57         That way the devpath to the device matches the devpath of the
81         driver; copying the driver value in a child device context is a
86       - the files in the device directory or files below subdirectories
87         of the same device directory
88       - accessing attributes reached by a symlink pointing to another device,
89         like the "device"-link, is a bug in the application
94 - Properties of parent devices never belong into a child device.
95     Always look at the parent devices themselves for determining device
96     context properties. If the device ``eth0`` or ``sda`` does not have a
97     "driver"-link, then this device does not have a driver. Its value is empty.
98     Never copy any property of the parent-device into a child-device. Parent
99     device properties may change dynamically without any notice to the
100     child device.
102 - Hierarchy in a single device tree
105     It is planned that all device directories will end up in the tree
111     not contain any device directories themselves, but only flat lists of
114     device information. It is planned to merge all three
139 - "device"-link and <subsystem>:<kernel name>-links
140     Never depend on the "device"-link. The "device"-link is a workaround
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
146     path as an element. Assuming the existence of the "device"-link for
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
157     real child device directories in the ``/sys/devices`` tree is a bug in
160     It is planned to remove all these links when all class device
163 - Position of devices along device chain can change.
164     Never depend on a specific parent device position in the devpath,
166     the chain. You must always request the parent device you are looking for
168     the device that matches the expected subsystem. Depending on a specific
169     position of a parent device or exposing relative paths using ``../`` to
172 - When reading and writing sysfs device attribute files, avoid dependency
176     In general, failures to read or write sysfs device attributes shall