Lines Matching refs:devices

37 - devices are only "devices"
38   There is no such thing like class-, bus-, physical devices,
42   applications that look for devices in sysfs.
45     o devpath (/devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.0)
52         pointing to /sys/devices must always be resolved to their real
74       - devices which do not have "driver"-link just do not have a
87 - Properties of parent devices never belong into a child device.
88   Always look at the parent devices themselves for determining device
97   and this is below: /sys/devices.
102   There are currently three places for classification of devices:
105   symlinks pointing to the unified /sys/devices tree.
112   The devices belonging to a subsystem will create a symlink in the
113   "devices" directory at /sys/subsystem/<name>/devices.
118   the other, as long as the devices are still reachable by the same
129   contain only disks and not partition devices in the same flat list is
134   for the old layout, where class devices are not created in
135   /sys/devices/ like the bus devices. If the link-resolving of a
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
140   a device in /sys/devices/ is a bug in the application.
145   that class devices are not created in /sys/devices. If a device
146   directory does not contain directories for child devices, these links
147   may be used to find the child devices in /sys/class. That is the single
149   element. Assuming the existence of these links for devices which are
150   real child device directories in the /sys/devices tree is a bug in
154   directories live in /sys/devices.
156 - Position of devices along device chain can change.
158   or the chain of parent devices. The kernel is free to insert devices into