Lines Matching full:code

35 split into core, generic, and device specific code. The core code (in
36 pmbus_core.c) provides generic functionality. The generic code (in pmbus.c)
37 provides support for generic PMBus devices. Device specific code is responsible
40 to PCI code, where generic code is augmented as needed with quirks for all kinds
46 For generic PMBus devices, code in pmbus.c attempts to auto-detect all supported
65 The API between core and device specific PMBus code is defined in
85 to be implemented in device specific code.
97 Virtual commands have to be handled in device specific driver code. Chip driver
98 code returns non-negative values if a virtual command is supported, or a
99 negative error code if not. The chip driver may return -ENODATA or any other
100 Linux error code in this case, though an error code other than -ENODATA is
102 core code will abort if the chip driver returns an error code when reading
103 or writing virtual registers (in other words, the PMBus core code will never
138 which *must* be handled in driver specific code. See "Virtual PMBus Commands"
141 Command execution in the core PMBus driver code is as follows::
197 commands are used, the chip driver code must not directly modify the current