Re: [Intel-gfx] [PATCH 2/9] drm/i915: add HAS_FORCEWAKE flag to uncore

2019-03-26 Thread Chris Wilson
Quoting Michal Wajdeczko (2019-03-26 12:47:00) > On Mon, 25 Mar 2019 22:49:33 +0100, Daniele Ceraolo Spurio > wrote: > > > We have several cases where we don't have forcewake (older gens, GVT and > > planned display-only uncore), so, instead of checking every time against > > the various condit

Re: [Intel-gfx] [PATCH 2/9] drm/i915: add HAS_FORCEWAKE flag to uncore

2019-03-26 Thread Michal Wajdeczko
On Mon, 25 Mar 2019 22:49:33 +0100, Daniele Ceraolo Spurio wrote: We have several cases where we don't have forcewake (older gens, GVT and planned display-only uncore), so, instead of checking every time against the various condition, save the info in a flag and use that. Note that this patc

Re: [Intel-gfx] [PATCH 2/9] drm/i915: add HAS_FORCEWAKE flag to uncore

2019-03-25 Thread Paulo Zanoni
Em seg, 2019-03-25 às 14:49 -0700, Daniele Ceraolo Spurio escreveu: > We have several cases where we don't have forcewake (older gens, GVT and > planned display-only uncore), so, instead of checking every time against > the various condition, save the info in a flag and use that. > > Note that thi

[Intel-gfx] [PATCH 2/9] drm/i915: add HAS_FORCEWAKE flag to uncore

2019-03-25 Thread Daniele Ceraolo Spurio
We have several cases where we don't have forcewake (older gens, GVT and planned display-only uncore), so, instead of checking every time against the various condition, save the info in a flag and use that. Note that this patch also change the behavior for gen5 with vpgu enabled, but this is not a