Lines Matching refs:devices

38 - devices are only "devices"
39     There is no such thing like class-, bus-, physical devices,
43     applications that look for devices in sysfs.
47     - devpath (``/devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.0``)
55         pointing to /sys/devices must always be resolved to their real
80       - devices which do not have "driver"-link just do not have a
94 - Properties of parent devices never belong into a child device.
95     Always look at the parent devices themselves for determining device
104     and this is below: ``/sys/devices.``
109     There are currently three places for classification of devices:
112     symlinks pointing to the unified ``/sys/devices`` tree.
119     The devices belonging to a subsystem will create a symlink in the
120     "devices" directory at ``/sys/subsystem/<name>/devices``,
125     the other, as long as the devices are still reachable by the same
136     contain only disks and not partition devices in the same flat list is
141     for the old layout, where class devices are not created in
142     ``/sys/devices/`` like the bus devices. If the link-resolving of a
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
147     a device in ``/sys/devices/`` is a bug in the application.
152     that class devices are not created in ``/sys/devices.`` If a device
153     directory does not contain directories for child devices, these links
154     may be used to find the child devices in ``/sys/class.`` That is the single
156     element. Assuming the existence of these links for devices which are
157     real child device directories in the ``/sys/devices`` tree is a bug in
161     directories live in ``/sys/devices.``
163 - Position of devices along device chain can change.
165     or the chain of parent devices. The kernel is free to insert devices into