Lines Matching full:cpucp

419  * CpuCP Primary Queue Packets
422  * messages to CpuCP, usually either to SET some value into a H/W periphery or
428  * communication from the host's driver to CpuCP will *always* be in
442  * During device initialization phase, the host will pass to CpuCP that address.
451  * Upon receiving the interrupt (#121), CpuCP will read the message from the
452  * DDR. In case the message is a SET operation, CpuCP will first perform the
454  * message is a GET operation, CpuCP will first fill the results section on the
455  * device DDR and then write to the fence object. If an error occurred, CpuCP
464  * so the value being put by the host's driver matches the value read by CpuCP
529  *       structure. The host's driver passes the max size it allows the CpuCP to
547  *       Test packet for CpuCP connectivity. The CPU will put the fence value
562  *       Get EEPROM data from the CpuCP kernel. The buffer is specified in the
565  *       CpuCP to write to the structure, to prevent data corruption in case of
570  *       passes the max size it allows the CpuCP to write to the structure, to
678  *       Get monitors registers dump from the CpuCP kernel.
680  *       which address is passed via the CpuCp packet. In addition, the host's driver
681  *       passes the max size it allows the CpuCP to write to the structure, to prevent
857 		/* For get CpuCP info/EEPROM data/NIC info */
910  * @cpucp_packet_invalid_pkt	-> when cpucp packet is un-supported.
1077  * CpuCP info
1129  * struct cpucp_info - Info from CpuCP that is necessary to the host's driver
1131  * @kernel_version: CpuCP linux kernel version.
1140  * @cpucp_version: CpuCP S/W version.