Lines Matching +full:device +full:- +full:specific

2 The Linux Kernel Device Model
16 bus-specific drivers for bridges and devices by consolidating a set of data
19 Traditional driver models implemented some sort of tree-like structure
26 of common callbacks, such as device discovery during bus probing, bus
29 The common device and bridge interface reflects the goals of the modern
30 computer: namely the ability to do seamless device "plug and play", power
32 Microsoft (namely ACPI) ensures that almost every device on almost any bus
33 on an x86-compatible system can work within this paradigm.  Of course,
43 and sometimes by the device-specific drivers.
51 	struct device dev;     /* Generic device interface */
55 Note first that the struct device dev within the struct pci_dev is
56 statically allocated. This means only one allocation on device discovery.
58 Note also that that struct device dev is not necessarily defined at the
63 The PCI bus layer freely accesses the fields of struct device. It knows about
65 device. Individual PCI device drivers that have been converted to the current
66 driver model generally do not and should not touch the fields of struct device,
72 (and not the device layer) accesses the struct device, it is only the bus
93 The auto-mounting of sysfs is typically accomplished by an entry similar to
98 or something similar in the /lib/init/fstab file on Debian-based systems::
104 	# mount -t sysfs sysfs /sys
106 Whenever a device is inserted into the tree, a directory is created for it.
107 This directory may be populated at each layer of discovery - the global layer,
108 the bus layer, or the device layer.
110 The global layer currently creates two files - 'name' and 'power'. The
111 former only reports the name of the device. The latter reports the
112 current power state of the device. It will also be used to set the current
117 for each PCI device.
119 A device-specific driver may also export files in its directory to expose
120 device-specific data or tunable interfaces.