Re: [Intel-gfx] [PATCH v5 10/12] drm/i915/guc: Handle default action received over CT

2018-03-27 Thread Daniele Ceraolo Spurio
On 27/03/18 14:05, Michal Wajdeczko wrote: On Tue, 27 Mar 2018 22:03:23 +0200, Michel Thierry wrote: On 3/27/2018 11:25 AM, Daniele Ceraolo Spurio wrote:   On 26/03/18 12:48, Michal Wajdeczko wrote: When running on platform with CTB based GuC communication enabled, GuC to Host event data

Re: [Intel-gfx] [PATCH v5 10/12] drm/i915/guc: Handle default action received over CT

2018-03-27 Thread Michal Wajdeczko
On Tue, 27 Mar 2018 22:03:23 +0200, Michel Thierry wrote: On 3/27/2018 11:25 AM, Daniele Ceraolo Spurio wrote: On 26/03/18 12:48, Michal Wajdeczko wrote: When running on platform with CTB based GuC communication enabled, GuC to Host event data will be delivered as CT request message. Howe

Re: [Intel-gfx] [PATCH v5 10/12] drm/i915/guc: Handle default action received over CT

2018-03-27 Thread Michel Thierry
On 3/27/2018 11:25 AM, Daniele Ceraolo Spurio wrote: On 26/03/18 12:48, Michal Wajdeczko wrote: 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 o

Re: [Intel-gfx] [PATCH v5 10/12] drm/i915/guc: Handle default action received over CT

2018-03-27 Thread Daniele Ceraolo Spurio
On 26/03/18 12:48, Michal Wajdeczko wrote: 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 communicatio