Lines Matching full:gsc
92 /* copy caller provided gsc message handle if this is polling for a prior msg completion */ in gsccs_send_message()
113 ret = intel_gsc_uc_heci_cmd_submit_nonpriv(>->uc.gsc, in gsccs_send_message()
117 drm_err(&i915->drm, "failed to send gsc PXP msg (%d)\n", ret); in gsccs_send_message()
123 drm_err(&i915->drm, "gsc PXP reply with invalid validity marker\n"); in gsccs_send_message()
128 drm_dbg(&i915->drm, "gsc PXP reply status has error = 0x%08x\n", in gsccs_send_message()
134 drm_dbg(&i915->drm, "gsc PXP reply is busy\n"); in gsccs_send_message()
136 * When the GSC firmware replies with pending bit, it means that the requested in gsccs_send_message()
174 * Keep sending request if GSC firmware was busy. Based on fw specs + in gsccs_send_message_retry_complete()
181 /* Only try again if gsc says so */ in gsccs_send_message_retry_complete()
194 * GSC-fw loading, HuC-fw loading, HuC-fw authentication and in intel_pxp_gsccs_is_ready_for_sessions()
195 * GSC-proxy init flow (requiring an mei component driver) in intel_pxp_gsccs_is_ready_for_sessions()
198 * gsc-proxy init flow (the last set of dependencies that in intel_pxp_gsccs_is_ready_for_sessions()
202 intel_gsc_uc_fw_proxy_init_done(&pxp->ctrl_gt->uc.gsc, true)) in intel_pxp_gsccs_is_ready_for_sessions()
378 * First, ensure the GSC engine is present. in gsccs_allocate_execution_resource()
386 * and another for the batch buffer we submit into GSC engine (that includes the packet). in gsccs_allocate_execution_resource()
387 * NOTE: GSC-CS backend is currently only supported on MTL, so we allocate shmem. in gsccs_allocate_execution_resource()
412 /* initialize host-session-handle (for all i915-to-gsc-firmware PXP cmds) */ in gsccs_allocate_execution_resource()