Lines Matching refs:specific

28 device specific extensions in addition to the core PMBus driver, since it is
29 simply unknown what new device specific functionality PMBus device developers
32 To make device specific extensions as scalable as possible, and to avoid having
34 split into core, generic, and device specific code. The core code (in
36 provides support for generic PMBus devices. Device specific code is responsible
37 for device specific initialization and, if needed, maps device specific
51 For this reason, it often makes sense to provide a device specific driver if not
64 The API between core and device specific PMBus code is defined in
83 than 0xff). Support for virtual PMBus commands is device specific and thus has
84 to be implemented in device specific code.
96 Virtual commands have to be handled in device specific driver code. Chip driver
109 for device specific drivers to pass information to the core PMBus driver.
121   command return values with device specific information.
131   specific command, but that a standard PMBus command may exist. Any other
137   which  _must_ be handled in driver specific code. See "Virtual PMBus Commands"
218   This function calls the device specific write_byte function if defined.
225   This function calls the device specific write_byte function if defined to
232   This function calls the device specific write_byte function if defined to
262         u32 flags;              /* Device specific flags */