Lines Matching refs:specific
29 device specific extensions in addition to the core PMBus driver, since it is
30 simply unknown what new device specific functionality PMBus device developers
33 To make device specific extensions as scalable as possible, and to avoid having
35 split into core, generic, and device specific code. The core code (in
37 provides support for generic PMBus devices. Device specific code is responsible
38 for device specific initialization and, if needed, maps device specific
52 For this reason, it often makes sense to provide a device specific driver if not
65 The API between core and device specific PMBus code is defined in
84 than 0xff). Support for virtual PMBus commands is device specific and thus has
85 to be implemented in device specific code.
97 Virtual commands have to be handled in device specific driver code. Chip driver
110 for device specific drivers to pass information to the core PMBus driver.
122 command return values with device specific information.
141 specific command, but that a standard PMBus command may exist. Any other
147 which *must* be handled in driver specific code. See "Virtual PMBus Commands"
259 This function calls the device specific write_byte function if defined.
268 This function calls the device specific write_byte function if defined to
277 This function calls the device specific write_byte function if defined to
312 u32 flags; /* Device specific flags */