Lines Matching refs:FW
91 | ISH Hardware/Firmware(FW) |
109 3.2.1 IPC/FW message types
118 internal queues to sequence messages and send them in order to the FW.
155 Each FW client and a protocol is identified by an UUID. In order to communicate
156 to a FW client, a connection must be established using connect request and
165 the link will be dropped if major FW reset occurs.
173 Each side (host and FW) manages its DMA transfer memory independently. When an
174 ISHTP client from either host or FW side wants to send something, it decides
177 the respective host buffer (TX when host client sends, RX when FW client
182 (that includes RX buffer) and FW responds with DMA_ALLOC_NOTIFY_ACK.
184 if thw host doesn't support DMA, then it won't send DMA allocation, so FW can't
185 send DMA; if FW doesn't support DMA then it won't respond with
188 it's request to do host->ISH DMA transfer; when FW sends DMA_XFER, it means
193 FW), DMA_XFER transfers ownership on the region that contains ISHTP message to
199 Currently, ISH FW decides to send over DMA if ISHTP message is more than 3 IPC
208 bus message protocol. These buffers are required because the FW may have not
214 The host enumeration bus command allow discovery of clients present in the FW.
223 - FW responds with HOST_START_RES_CMD
224 - Host sends HOST_ENUM_REQ_CMD (enumerate FW clients)
225 - FW responds with HOST_ENUM_RES_CMD that includes bitmap of available FW
227 - For each FW ID found in that bitmap host sends
229 - FW responds with HOST_CLIENT_PROPERTIES_RES_CMD. Properties include UUID,
238 - enumerate HID devices under FW ISH client