drm/i915: Add means to apply WA conditionally
Subsystems (2)
PATCH 1/1 drm/i915: Add means to apply WA conditionally
We would want to apply some of the workarounds based on a condition to a particular platform or Gen but we may not know all possible controlling parameters in advance hence allow to define open conditions; a WA makes it to the list only if the condition is true.
With the appropriate conditions we can combine all of the workarounds and apply them from a single place irrespective of platform instead of having them in separate functions.
For: VIZ-4090
--- drivers/gpu/drm/i915/intel_ringbuffer.c | 35 +++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+)
drivers/gpu/drm/i915/intel_ringbuffer.c +35 -0
@@ -736,6 +736,41 @@ static int wa_add(struct drm_i915_private *dev_priv,#define WA_WRITE (addr, val) WA_REG(addr, val, 0xffffffff) +#define WA_SET_BIT_MASKED_IF (cond, addr, mask) \ + do { \ + if (cond) { \ + WA_SET_BIT_MASKED(addr, mask); \ + } \ + } while(0) + +#define WA_CLR_BIT_MASKED_IF (cond, addr, mask) \ + do { \ + if (cond) { \ + WA_CLR_BIT_MASKED(addr, mask); \ + } \ + } while(0) + +#define WA_SET_BIT_IF (cond, addr, mask) \ + do { \ + if (cond) { \ + WA_SET_BIT(addr, mask); \ + } \ + } while(0) + +#define WA_CLR_BIT_IF (cond, addr, mask) \ + do { \ + if (cond) { \ + WA_CLR_BIT(addr, mask); \ + } \ + } while(0) + +#define WA_WRITE_IF (cond, addr, val) \ + do { \ + if (cond) { \ + WA_WRITE(addr, val); \ + } \ + } while(0) +static int bdw_init_workarounds (struct intel_engine_cs *ring) {struct drm_device *dev = ring->dev;
Signature · 1 line
2.1.2
Quoted 11 lines · Arun Siluvery
We would want to apply some of the workarounds based on a condition to a particular platform or Gen but we may not know all possible controlling parameters in advance hence allow to define open conditions; a WA makes it to the list only if the condition is true.
With the appropriate conditions we can combine all of the workarounds and apply them from a single place irrespective of platform instead of having them in separate functions.
For: VIZ-4090
Signed-off-by Arun Siluvery <[email protected]>
Imo we should just pull the condition out into proper control flow. Hiding it like that in the macro doesn't seem to buy us anything at all, but obfuscates the code.
-Daniel
Quoted 57 lines
--- drivers/gpu/drm/i915/intel_ringbuffer.c | 35 +++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+)drivers/gpu/drm/i915/intel_ringbuffer.c +35
-0@@ -736,6 +736,41 @@ static int wa_add(struct drm_i915_private *dev_priv,#define WA_WRITE (addr, val) WA_REG(addr, val, 0xffffffff) +#define WA_SET_BIT_MASKED_IF (cond, addr, mask) \ + do { \ + if (cond) { \ + WA_SET_BIT_MASKED(addr, mask); \ + } \ + } while(0) + +#define WA_CLR_BIT_MASKED_IF (cond, addr, mask) \ + do { \ + if (cond) { \ + WA_CLR_BIT_MASKED(addr, mask); \ + } \ + } while(0) + +#define WA_SET_BIT_IF (cond, addr, mask) \ + do { \ + if (cond) { \ + WA_SET_BIT(addr, mask); \ + } \ + } while(0) + +#define WA_CLR_BIT_IF (cond, addr, mask) \ + do { \ + if (cond) { \ + WA_CLR_BIT(addr, mask); \ + } \ + } while(0) + +#define WA_WRITE_IF (cond, addr, val) \ + do { \ + if (cond) { \ + WA_WRITE(addr, val); \ + } \ + } while(0) +static int bdw_init_workarounds (struct intel_engine_cs *ring) {struct drm_device *dev = ring->dev;Signature · 6 lines
2.1.2 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Signature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch
Quoted 10 lines · Daniel Vetter
Quoted 9 lines · Arun Siluvery
We would want to apply some of the workarounds based on a condition to a particular platform or Gen but we may not know all possible controlling parameters in advance hence allow to define open conditions; a WA makes it to the list only if the condition is true.
With the appropriate conditions we can combine all of the workarounds and apply them from a single place irrespective of platform instead of having them in separate functions.
Quoted 6 lines
Quoted 2 lines
For: VIZ-4090
Signed-off-by Arun Siluvery <[email protected]>Imo we should just pull the condition out into proper control flow. Hiding it like that in the macro doesn't seem to buy us anything at all, but obfuscates the code.
No we are not hiding the condition, I thought it would be easier to read it this way, e.g.,
WA_SET_BIT_MASKED_IF(IS_BDW_GT3(dev), WA_REG, WA_MASK);
do you prefer adding if(cond) to each WA?
regards
Arun
Quoted 60 lines
-Daniel
Quoted 57 lines
--- drivers/gpu/drm/i915/intel_ringbuffer.c | 35 +++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+)drivers/gpu/drm/i915/intel_ringbuffer.c +35
-1@@ -736,6 +736,41 @@ static int wa_add(struct drm_i915_private *dev_priv,#define WA_WRITE (addr, val) WA_REG(addr, val, 0xffffffff) +#define WA_SET_BIT_MASKED_IF (cond, addr, mask) \ + do { \ + if (cond) { \ + WA_SET_BIT_MASKED(addr, mask); \ + } \ + } while(0) + +#define WA_CLR_BIT_MASKED_IF (cond, addr, mask) \ + do { \ + if (cond) { \ + WA_CLR_BIT_MASKED(addr, mask); \ + } \ + } while(0) + +#define WA_SET_BIT_IF (cond, addr, mask) \ + do { \ + if (cond) { \ + WA_SET_BIT(addr, mask); \ + } \ + } while(0) + +#define WA_CLR_BIT_IF (cond, addr, mask) \ + do { \ + if (cond) { \ + WA_CLR_BIT(addr, mask); \ + } \ + } while(0) + +#define WA_WRITE_IF (cond, addr, val) \ + do { \ + if (cond) { \ + WA_WRITE(addr, val); \ + } \ + } while(0) +static int bdw_init_workarounds (struct intel_engine_cs *ring) {struct drm_device *dev = ring->dev; --2.1.2
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 22 lines · Arun
Quoted 12 lines · Daniel Vetter
Quoted 10 lines · Arun Siluvery
We would want to apply some of the workarounds based on a condition to a particular platform or Gen but we may not know all possible controlling parameters in advance hence allow to define open conditions; a WA makes it to the list only if the condition is true.
With the appropriate conditions we can combine all of the workarounds and apply them from a single place irrespective of platform instead of having them in separate functions.
Quoted 7 lines
Quoted 2 lines
For: VIZ-4090
Signed-off-by Arun Siluvery <[email protected]>Imo we should just pull the condition out into proper control flow. Hiding it like that in the macro doesn't seem to buy us anything at all, but obfuscates the code.
Quoted 6 lines
No we are not hiding the condition, I thought it would be easier to read it this way, e.g.,
WA_SET_BIT_MASKED_IF(IS_BDW_GT3(dev), WA_REG, WA_MASK);do you prefer adding if(cond) to each WA?
Yes.
-Daniel
Signature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch