Lines Matching full:vpu
59 * VPU status values.
79 * Host <-> VPU IPC channels.
105 * VPU private data mask.
106 * Reserved for the VPU to store private data about the job (or inline command)
129 * 1. For queues using native fences, VPU expects that all jobs in the queue
134 * 2. Native fence queues are only supported on VPU 40xx onwards.
190 * VPU does nothing other than consuming the inline command object.
195 * VPU waits for the fence current value to reach monitored value.
197 * the fence to be satisfied, VPU blocks fetching of the next objects in the queue.
204 * VPU sets the fence current value to the provided value. If new current value
205 * is equal to or higher than monitored value, VPU sends fence signalled notification
228 /**< Address of VPU commands batch buffer */
345 /* Written by VPU after adding a log entry. Initialised by host to 0. */
347 /* Incremented by VPU every time the VPU writes the 0th entry; initialised by host to 0. */
351 * It is written by host before passing buffer to VPU. VPU should consider it read-only.
362 /* VPU timestamp must be an invariant timer tick (not impacted by DVFS) */
435 * Host <-> VPU IPC messages types.
502 * each group. The VPU will write the description of groups and counters to
516 * Register a doorbell to notify VPU of new work. The doorbell may later be
533 * Dump VPU state. To be used for debug purposes only.
582 * VPU will return an error result if metric collection cannot be started,
606 * Asynchronous event sent from the VPU to the host either when the current
607 * metric buffer is full or when the VPU has collected a multiple of
746 * started. If the VPU device does not support multiple metric streamer instances,
754 * If > 0 the VPU will send a VPU_JSM_MSG_METRIC_STREAMER_NOTIFICATION message
755 * after every @notify_sample_count samples is collected or dropped by the VPU.
756 * If set to UINT_MAX the VPU will only generate a notification when the metric
757 * buffer is full. If set to 0 the VPU will never generate a notification.
762 * Address and size of the buffer where the VPU will write metric data. The
763 * VPU writes all counters from enabled metric groups one after another. If
764 * there is no space left to write data at the next sample period the VPU
767 * If @next_buffer_addr is NULL the VPU will stop collecting metric data.
773 * buffer is full. If the address is NULL the VPU will stop collecting metric
790 * Provide VPU FW with buffers to write metric data.
797 * Address and size of the buffer where the VPU will write metric data.
805 * the size of the current buffer is unchanged. The VPU will return an update
810 * current buffer address. The VPU will immediately switch data collection to
811 * the new buffer. Then the VPU will return an update in the
818 * buffer is full. If the address is NULL the VPU will stop collecting metric
823 * that both addresses make sense even if the VPU just switched to writing samples
959 * For normal priority band, specifies the target VPU percentage
1085 * The entry contains the VPU timestamp, operation type and data.
1086 * The host should provide the notify index value of log buffer to VPU. This is a
1091 * VPU will handle one log buffer for each of supported engines.
1092 * VPU should allow the logging to consume one host_ssid.
1103 * VPU log buffer virtual address.
1121 * @brief The scheduling log notification is generated by VPU when it writes
1122 * an event into the log buffer at the notify_index. VPU notifies host with
1124 * message from VPU to host.
1137 * Host will request the suspend of contexts and VPU will;
1146 * Same structure used when VPU notifies host of completion of a context suspend
1149 * complete, VPU will not access any data relating to this command queue until
1162 * Suspend fence value - reported by the VPU suspend context
1171 * - VPU will resume all work on this context
1187 * After a HWS engine reset, all scheduling is stopped on VPU until a engine resume.
1286 * Data sent from the VPU to the host in all metric streamer response messages
1299 * Some VPU implementations may align sample_size to more than 8 bytes.
1359 * If the VPU uses fixed size strings, all characters from the end of the name
1367 * Right after this structure, the VPU writes name and description of
1398 * If the VPU uses fixed size strings, all characters from the end of the name
1410 * Right after this structure, the VPU writes name, description
1418 * VPU_JSM_MSG_DYNDBG_CONTROL are used to control the VPU FW Dynamic Debug
1452 * 1: VPU_JSM_MSG_PWR_D0I3_ENTER_DONE is sent after VPU state save is complete
1520 * to allow proper handling of VPU cache operations.
1531 * back by VPU in the response message.
1534 /* Request return code set by the VPU, see VPU_JSM_STATUS_* defines. */