Lines Matching full:chip

79 functionality which has been implemented by several chip vendors and is thus
97 Virtual commands have to be handled in device specific driver code. Chip driver
99 negative error code if not. The chip driver may return -ENODATA or any other
102 core code will abort if the chip driver returns an error code when reading
104 send a virtual command to a chip).
115   provided by chip manufacturers in device datasheets.
116 - Supported chip functionality can be provided to the core driver. This may be
127 Functions provided by chip driver
134 chip, and that no attempt should be made to read or write the standard
152 Chip drivers may provide pointers to the following functions in struct
168 Read word from page <page>, phase <pase>, register <reg>. If the chip does not
169 support multiple phases, the phase parameter can be ignored. If the chip
191 if a chip driver supports multiple chips, and the chip functionality is not
198 Chip drivers are expected to use the following functions to read or write
199 PMBus registers. Chip drivers may also use direct I2C commands. If direct I2C
200 commands are used, the chip driver code must not directly modify the current
210 If the chip does not support multiple phases, the phase parameter is
219 i2c_smbus_read_word_data(), but selects page and phase first. If the chip does
249 Execute PMBus "Clear Fault" command on all chip pages.
260 obtain the chip status. Therefore, it must _not_ be called from that function.
269 obtain the chip status. Therefore, it must _not_ be called from that function.
316 trying to determine if a chip register exists or not.