Lines Matching refs:auxiliary_device

26 Each auxiliary_device represents a part of its parent functionality. The
28 auxiliary_device within other domain-specific structures and the use of .ops
43 provide access to a shared object allocated by the auxiliary_device's
44 registering driver. The registering driver for the auxiliary_device(s) and the
53 driver allocates and registers an auxiliary_device for each physical
59 functions. For each sub function an auxiliary_device is created. A PCI sub
65 before a driver binds to an auxiliary_device.
77 An auxiliary_device represents a part of its parent device's functionality. It
82 Registering an auxiliary_device is a two-step process. First call
83 auxiliary_device_init(), which checks several aspects of the auxiliary_device
86 The second step in registering an auxiliary_device is to perform a call to
90 Unregistering an auxiliary_device is also a two-step process to mirror the
96 struct auxiliary_device {
107 The auxiliary_device.dev.type.release or auxiliary_device.dev.release must be
108 populated with a non-NULL pointer to successfully register the auxiliary_device.
110 The auxiliary_device.dev.parent must also be populated.
116 auxiliary_device and register it on the auxiliary bus. It is important to note
121 auxiliary_device. It also contains a pointer to the shared object(s), which
125 from the pointer to the auxiliary_device, that is passed during the call to the
129 The memory for the auxiliary_device is freed only in its release() callback
133 than, the lifespan of the memory for the auxiliary_device. The auxiliary_driver
135 auxiliary_device is still registered on the auxiliary bus. It is up to the
137 shared object beyond the life of the auxiliary_device.
153 int (*probe)(struct auxiliary_device *,
155 void (*remove)(struct auxiliary_device *);
156 void (*shutdown)(struct auxiliary_device *);
157 int (*suspend)(struct auxiliary_device *, pm_message_t);
158 int (*resume)(struct auxiliary_device *);
172 extend the scope of an auxiliary_device is to encapsulate it within a domain-
174 auxiliary_device and any associated shared data/callbacks needed to establish
182 struct auxiliary_device auxdev;
183 void (*connect)(struct auxiliary_device *auxdev);
184 void (*disconnect)(struct auxiliary_device *auxdev);
188 The parent device then registers the auxiliary_device by calling
191 auxiliary_device that, combined with the parent's KBUILD_MODNAME, creates a
203 void (*send)(struct auxiliary_device *auxdev);
204 void (*receive)(struct auxiliary_device *auxdev);