Lines Matching refs:device

40   just simply a "device". Class-, bus-, physical, ... types are just
44   The properties of a device are:
47         at device creation and removal
48       - the unique key to the device at that point in time
49       - the kernel's path to the device directory without the leading
53         target and the target path must be used to access the device.
54         That way the devpath to the device matches the devpath of the
75         driver; copying the driver value in a child device context is a
79       - the files in the device directory or files below subdirectories
80         of the same device directory
81       - accessing attributes reached by a symlink pointing to another device,
82         like the "device"-link, is a bug in the application
87 - Properties of parent devices never belong into a child device.
88   Always look at the parent devices themselves for determining device
89   context properties. If the device 'eth0' or 'sda' does not have a
90   "driver"-link, then this device does not have a driver. Its value is empty.
91   Never copy any property of the parent-device into a child-device. Parent
92   device properties may change dynamically without any notice to the
93   child device.
95 - Hierarchy in a single device tree
98   It is planned that all device directories will end up in the tree
104   not contain any device directories themselves, but only flat lists of
107   device information. It is planned to merge all three
132 - "device"-link and <subsystem>:<kernel name>-links
133   Never depend on the "device"-link. The "device"-link is a workaround
136   device directory does not end in /sys/devices/, you can use the
137   "device"-link to find the parent devices in /sys/devices/. That is the
138   single valid use of the "device"-link; it must never appear in any
139   path as an element. Assuming the existence of the "device"-link for
140   a device in /sys/devices/ is a bug in the application.
141   Accessing /sys/class/net/eth0/device is a bug in the application.
145   that class devices are not created in /sys/devices. If a device
150   real child device directories in the /sys/devices tree is a bug in
153   It is planned to remove all these links when all class device
156 - Position of devices along device chain can change.
157   Never depend on a specific parent device position in the devpath,
159   the chain. You must always request the parent device you are looking for
161   the device that matches the expected subsystem. Depending on a specific
162   position of a parent device or exposing relative paths using "../" to