Lines Matching +full:chip +full:- +full:selects
9 power-management protocol with a fully defined command language that facilitates
11 protocol is implemented over the industry-standard SMBus serial interface and
12 enables programming, control, and real-time monitoring of compliant power
18 promoted by the PMBus Implementers Forum (PMBus-IF), comprising 30+ adopters
22 commands, and manufacturers can add as many non-standard commands as they like.
23 Also, different PMBUs devices act differently if non-supported commands are
43 PMBus device capabilities auto-detection
46 For generic PMBus devices, code in pmbus.c attempts to auto-detect all supported
47 PMBus commands. Auto-detection is somewhat limited, since there are simply too
50 pages (see the PMBus specification for details on multi-page PMBus devices).
53 all commands can be auto-detected. The data structures in this driver can be
57 Some commands are always auto-detected. This applies to all limit commands
59 Limits and alarm attributes are auto-detected because there are simply too many
70 -----------------------
76 ----------------------
78 Virtual PMBus commands are provided to enable support for non-standard
79 functionality which has been implemented by several chip vendors and is thus
92 - READ commands are read-only; writes are either ignored or return an error.
93 - RESET commands are read/write. Reading reset registers returns zero
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
104 send a virtual command to a chip).
107 ------------------------
113 - For devices supporting its data in Direct Data Format, it provides coefficients
115 provided by chip manufacturers in device datasheets.
116 - Supported chip functionality can be provided to the core driver. This may be
117 necessary for chips which react badly if non-supported commands are executed,
119 - Several function entry points are provided to support overriding and/or
121 non-standard PMBus commands to standard commands, or to augment standard
128 by both the I2C adapter and by the PMBus chip, it is by default enabled.
131 communication with the PMBus chip.
136 Functions provided by chip driver
137 ---------------------------------
140 successful. A return value of -ENODATA indicates that there is no manufacturer
143 chip, and that no attempt should be made to read or write the standard
154 if (status != -ENODATA)
158 return -EINVAL;
161 Chip drivers may provide pointers to the following functions in struct
169 <page> may be -1, which means "current page".
177 Read word from page <page>, phase <phase>, register <reg>. If the chip does not
178 support multiple phases, the phase parameter can be ignored. If the chip
193 <page> may be -1, which means "current page".
200 if a chip driver supports multiple chips, and the chip functionality is not
201 pre-determined. It is currently only used by the generic pmbus driver
205 ---------------------------------
207 Chip drivers are expected to use the following functions to read or write
208 PMBus registers. Chip drivers may also use direct I2C commands. If direct I2C
209 commands are used, the chip driver code must not directly modify the current
219 If the chip does not support multiple phases, the phase parameter is
220 ignored. Otherwise, a phase value of 0xff selects all phases.
228 i2c_smbus_read_word_data(), but selects page and phase first. If the chip does
230 value of 0xff selects all phases.
238 selects page first.
245 selects page first. <page> may be -1, which means "current page".
252 selects page first. <page> may be -1, which means "current page".
258 Execute PMBus "Clear Fault" command on all chip pages.
269 obtain the chip status. Therefore, it must _not_ be called from that function.
278 obtain the chip status. Therefore, it must _not_ be called from that function.
329 -----
338 trying to determine if a chip register exists or not.
343 Some i2c controllers do not support single-byte commands (write commands with
349 Set if the chip is write protected and write protection is not determined
364 chip pmbus controller to a known state after a failed register check.
367 register check. This read may fail, but it will put the chip into a
383 Set if the chip OPERATION command is protected and protection is not
388 Set if the chip VOUT_COMMAND command is protected and protection is not
392 ----------------
398 The ability to actually alter the protection may also depend on the chip
409 for multi-page chips, if the chips strictly follows the PMBus
410 specification, preventing the chip from changing the active page.