Lines Matching refs:code

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