drm/i915/guc: Handle default action received over CT
When running on platform with CTB based GuC communication enabled, GuC to Host event data will be delivered as CT request message. However, content of the data[1] of this CT message follows format of the scratch register used in MMIO based communication, so some code reuse is still possible. v2: filter disabled messages (Daniele) Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com> Cc: Oscar Mateo <oscar.mateo@intel.com> Reviewed-by: Michel Thierry <michel.thierry@intel.com> #1 Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com> Acked-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Link: https://patchwork.freedesktop.org/patch/msgid/20180327214124.70680-1-michal.wajdeczko@intel.com
This commit is contained in:

committed by
Chris Wilson

parent
6c77a2b058
commit
b6b0166d49
@@ -416,6 +416,14 @@ void intel_guc_to_host_event_handler_mmio(struct intel_guc *guc)
|
||||
I915_WRITE(SOFT_SCRATCH(15), val & ~msg);
|
||||
spin_unlock(&guc->irq_lock);
|
||||
|
||||
intel_guc_to_host_process_recv_msg(guc, msg);
|
||||
}
|
||||
|
||||
void intel_guc_to_host_process_recv_msg(struct intel_guc *guc, u32 msg)
|
||||
{
|
||||
/* Make sure to handle only enabled messages */
|
||||
msg &= guc->msg_enabled_mask;
|
||||
|
||||
if (msg & (INTEL_GUC_RECV_MSG_FLUSH_LOG_BUFFER |
|
||||
INTEL_GUC_RECV_MSG_CRASH_DUMP_POSTED))
|
||||
intel_guc_log_handle_flush_event(&guc->log);
|
||||
|
Reference in New Issue
Block a user