Lines Matching full:commands

21 Unfortunately, while PMBus commands are standardized, there are no mandatory
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
47 PMBus commands. Auto-detection is somewhat limited, since there are simply too
49 which PMBus commands are paged and which commands are replicated across all
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
67 standard PMBus commands and virtual PMBus commands.
69 Standard PMBus commands
72 Standard PMBus commands (commands values 0x00 to 0xff) are defined in the PMBUs
75 Virtual PMBus commands
78 Virtual PMBus commands are provided to enable support for non-standard
82 Virtual PMBus commands start with command value 0x100 and can thus easily be
83 distinguished from standard PMBus commands (which can not have values larger
84 than 0xff). Support for virtual PMBus commands is device specific and thus has
87 Virtual commands are named PMBUS_VIRT_xxx and start with PMBUS_VIRT_BASE. All
88 virtual commands are word sized.
90 There are currently two types of virtual commands.
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
117   necessary for chips which react badly if non-supported commands are executed,
121   non-standard PMBus commands to standard commands, or to augment standard
142 negative return value indicates that the commands does not exist for this
146 As mentioned above, an exception to this rule applies to virtual commands,
147 which *must* be handled in driver specific code. See "Virtual PMBus Commands"
157 	if (command >= PMBUS_VIRT_BASE)	/* For word commands/registers only */
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
218 Set PMBus page register to <page> and <phase> for subsequent commands.
343 Some i2c controllers do not support single-byte commands (write commands with
404   PAGE, ON_OFF_CONFIG and VOUT_COMMAND commands.
406   PAGE commands.