Lines Matching refs:driver

5  * Please see Documentation/driver-api/auxiliary_bus.rst for more information.
17 * The registering driver is the entity that allocates memory for the
19 * note that, as opposed to the platform bus, the registering driver is wholly
23 * callback defined by the registering driver. The registering driver should
31 * object(s) are allocated by the registering driver. This layout allows the
41 * is up to the registering driver to manage (e.g. free or keep available) the
44 * The registering driver must unregister all auxiliary devices before its own
45 * driver.remove() is completed. An easy way to ensure this is to use the
50 * to function (if only to return an error) after the registering driver
59 * @name: Match name found by the auxiliary device driver,
64 * KBUILD_MODNAME, creates a match_name that is used for driver binding, and an
66 * the bus subsystem. For example, a driver registering an auxiliary device is
77 * driver. If two auxiliary_devices with the same match_name, eg
87 * bus the parent driver can not tell what other code may have a reference to
145 * struct auxiliary_driver - Definition of an auxiliary bus driver
152 * @driver: Core driver structure.
153 * @id_table: Table of devices this driver should match on the bus.
155 * Auxiliary drivers follow the standard driver model convention, where
162 * auxiliary devices that a driver can bind with.
187 struct device_driver driver;
208 return container_of(drv, struct auxiliary_driver, driver);
233 * module_auxiliary_driver() - Helper macro for registering an auxiliary driver
234 * @__auxiliary_driver: auxiliary driver struct