drm/i915: Per-engine scratch VMA is mandatory
We fail engine initialization if the scratch VMA cannot be created so there is no point in error handle it later. If the initialization ordering gets messed up, we can explode during development just as well. Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Michel Thierry <michel.thierry@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20180119100005.9072-2-tvrtko.ursulin@linux.intel.com
This commit is contained in:
parent
ae504be2e0
commit
10bde236ef
|
@ -1414,7 +1414,7 @@ static int intel_init_workaround_bb(struct intel_engine_cs *engine)
|
|||
unsigned int i;
|
||||
int ret;
|
||||
|
||||
if (GEM_WARN_ON(engine->id != RCS || !engine->scratch))
|
||||
if (GEM_WARN_ON(engine->id != RCS))
|
||||
return -EINVAL;
|
||||
|
||||
switch (INTEL_GEN(engine->i915)) {
|
||||
|
|
Loading…
Reference in New Issue