Home
last modified time | relevance | path

Searched refs:GET_INFO (Results 1 – 4 of 4) sorted by relevance

/openbmc/hiomapd/Documentation/
H A Dprotocol.md110 | 2 | [`GET_INFO`](#get_info-command) | ✓ | ✓ | ✓ | Perform protocol …
159 The high-level protocol flow is that the host first issues a `GET_INFO` command
164 Once `GET_INFO` has successfully completed, the host should request the flash
186 When invoking `GET_INFO` the host must provide the BMC its highest supported
193 subsequent `GET_INFO` command.
201 2. `GET_INFO`
207 The arguments to the `GET_INFO` command are considered unversioned and as a
215 unversioned removes the complexity of implementing `GET_INFO` with its version
235 (`RESET`, `GET_INFO` or `ACK`) with an invalid sequence number. For all other
483 ## `GET_INFO` Command
[all …]
/openbmc/linux/drivers/media/pci/saa7164/
H A Dsaa7164-types.h97 GET_INFO = 0x86, enumerator
/openbmc/qemu/hw/cxl/
H A Dcxl-mailbox-utils.c65 #define GET_INFO 0x0 macro
2727 [FIRMWARE_UPDATE][GET_INFO] = { "FIRMWARE_UPDATE_GET_INFO",
/openbmc/linux/drivers/input/misc/
H A Dims-pcu.c695 error = ims_pcu_execute_query(pcu, GET_INFO); in ims_pcu_get_info()