Oscar Mateo <[email protected]> writes: > Now that we write RING_FORCE_TO_NONPRIV registers directly to hardware, > there is no need to save space for them in the list of context workarounds. > > Signed-off-by: Oscar Mateo <[email protected]> > Cc: Chris Wilson <[email protected]> > Cc: Mika Kuoppala <[email protected]>
Reviewed-by: Mika Kuoppala <[email protected]> > --- > drivers/gpu/drm/i915/i915_drv.h | 8 +------- > 1 file changed, 1 insertion(+), 7 deletions(-) > > diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h > index 799a90a..47a357c 100644 > --- a/drivers/gpu/drm/i915/i915_drv.h > +++ b/drivers/gpu/drm/i915/i915_drv.h > @@ -1954,13 +1954,7 @@ struct i915_wa_reg { > u32 mask; > }; > > -/* > - * RING_MAX_NONPRIV_SLOTS is per-engine but at this point we are only > - * allowing it for RCS as we don't foresee any requirement of having > - * a whitelist for other engines. When it is really required for > - * other engines then the limit need to be increased. > - */ > -#define I915_MAX_WA_REGS (16 + RING_MAX_NONPRIV_SLOTS) > +#define I915_MAX_WA_REGS 16 > > struct i915_workarounds { > struct i915_wa_reg reg[I915_MAX_WA_REGS]; > -- > 1.9.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
