Lines Matching refs:device

5 See the kerneldoc for the struct device.
10 The bus driver that discovers the device uses this to register the
11 device with the core:
13 int device_register(struct device * dev);
22 A device is removed from the core when its reference count goes to
25 struct device * get_device(struct device * dev);
26 void put_device(struct device * dev);
28 get_device() will return a pointer to the struct device passed to it
32 A driver can access the lock in the device structure using: 
34 void lock_device(struct device * dev);
35 void unlock_device(struct device * dev);
42 	ssize_t (*show)(struct device *dev, struct device_attribute *attr,
44 	ssize_t (*store)(struct device *dev, struct device_attribute *attr,
48 Attributes of devices can be exported by a device driver through sysfs.
53 As explained in Documentation/kobject.txt, device attributes must be be
85 This array of groups can then be associated with a device by setting the
86 group pointer in struct device before device_register() is invoked:
92 device attributes and the device_unregister() function will use this pointer
93 to remove the device attributes.
96 device_remove_file() to be called on a device at any time, userspace has
97 strict expectations on when attributes get created.  When a new device is
99 udev) that a new device is available.  If attributes are added after the
100 device is registered, then userspace won't get notified and userspace will
103 This is important for device driver that need to publish additional
104 attributes for a device at driver probe time.  If the device driver simply
105 calls device_create_file() on the device structure passed to it, then