Fixed16.16 wrapper cleanup & wm optimization
Subsystems (2)
cover Fixed16.16 wrapper cleanup & wm optimization
This series Include patches for:
clean fixed16.16 naming & make them consistent reuse intel_compute_linetime_wm in hsw optimize wm calculation code enable/Implement trans wm calculation
Mahesh Kumar (6):
drm/i915: cleanup fixed-point wrappers naming drm/i915/hsw: use intel_compute_linetime_wm function for linetime wm drm/i915/skl+: WM calculation don't require height drm/i915/skl+: unify cpp value in WM calculation drm/i915/skl+: Optimize WM calculation
drm/i915/gen10: Calculate and enable transition WM
drivers/gpu/drm/i915/i915_drv.h | 82 ++++++----- drivers/gpu/drm/i915/intel_drv.h | 1 + drivers/gpu/drm/i915/intel_pm.c | 288 ++++++++++++++++++++++++--------------- 3 files changed, 228 insertions(+), 143 deletions(-)
Signature · 6 lines
2.13.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 1/6 drm/i915: cleanup fixed-point wrappers naming
This patch make naming of fixed-point wrappers consistent operation_<any_post_operation>_<1st operand>_<2nd operand> also shorten the name for fixed_16_16 to fixed16
s/u32_to_fixed_16_16/u32_to_fixed16 s/fixed_16_16_to_u32/fixed16_to_u32 s/fixed_16_16_to_u32_round_up/fixed16_to_u32_round_up s/min_fixed_16_16/min_fixed16 s/max_fixed_16_16/max_fixed16 s/mul_u32_fixed_16_16/mul_u32_fixed16
always do division internal operation in 64 bits:
s/fixed_16_16_div/div_fixed16
s/fixed_16_16_div_64/div_fixed16
Introduce Addition wrappers for fixed16add_fixed16 : takes 2 fixed_16_16_t variable & returns fixed16_16_t add_fixed16_u32 : takes fixed_16_16_t & u32 variable & returns fixed16_16_t
--- drivers/gpu/drm/i915/i915_drv.h | 69 +++++++++++++++++++++++------------------ drivers/gpu/drm/i915/intel_pm.c | 59 +++++++++++++++++------------------ 2 files changed, 67 insertions(+), 61 deletions(-)
drivers/gpu/drm/i915/i915_drv.h +38 -31
@@ -122,7 +122,7 @@ static inline bool is_fixed16_zero(uint_fixed_16_16_t val)return false; } -static inline uint_fixed_16_16_t u32_to_fixed_16_16 (uint32_t val) +static inline uint_fixed_16_16_t u32_to_fixed16 (uint32_t val) {uint_fixed_16_16_t fp;
@@ -132,17 +132,17 @@ static inline uint_fixed_16_16_t u32_to_fixed_16_16(uint32_t val)return fp; } -static inline uint32_t fixed_16_16_to_u32_round_up (uint_fixed_16_16_t fp) +static inline uint32_t fixed16_to_u32_round_up (uint_fixed_16_16_t fp) {return DIV_ROUND_UP (fp.val,1 <<16 ); } -static inline uint32_t fixed_16_16_to_u32 (uint_fixed_16_16_t fp) +static inline uint32_t fixed16_to_u32 (uint_fixed_16_16_t fp) {return fp.val >>16 ; } -static inline uint_fixed_16_16_t min_fixed_16_16 (uint_fixed_16_16_t min1, +static inline uint_fixed_16_16_t min_fixed16 (uint_fixed_16_16_t min1,uint_fixed_16_16_t min2) {uint_fixed_16_16_t min;
@@ -151,7 +151,7 @@ static inline uint_fixed_16_16_t min_fixed_16_16(uint_fixed_16_16_t min1,return min; } -static inline uint_fixed_16_16_t max_fixed_16_16 (uint_fixed_16_16_t max1, +static inline uint_fixed_16_16_t max_fixed16 (uint_fixed_16_16_t max1,uint_fixed_16_16_t max2) {uint_fixed_16_16_t max;
@@ -160,6 +160,14 @@ static inline uint_fixed_16_16_t max_fixed_16_16(uint_fixed_16_16_t max1,return max; } +static inline uint_fixed_16_16_t clamp_u64_to_fixed16 (uint64_t val) +{ +uint_fixed_16_16_t fp; +WARN_ON (val >>32 ); + fp.val =clamp_t (uint32_t, val,0 , ~0 ); +return fp; +} +static inline uint32_t div_round_up_fixed16 (uint_fixed_16_16_t val,uint_fixed_16_16_t d) {
@@ -170,48 +178,31 @@ static inline uint32_t mul_round_up_u32_fixed16(uint32_t val, uint_fixed_16_16_t mul) {uint64_t intermediate_val; -uint32_t result; intermediate_val = (uint64_t ) val * mul.val; intermediate_val =DIV_ROUND_UP_ULL (intermediate_val,1 <<16 );WARN_ON (intermediate_val >>32 ); - result =clamp_t (uint32_t, intermediate_val,0 , ~0 ); -return result; +return clamp_t (uint32_t, intermediate_val,0 , ~0 ); }static inline uint_fixed_16_16_t mul_fixed16 (uint_fixed_16_16_t val,uint_fixed_16_16_t mul) {uint64_t intermediate_val; -uint_fixed_16_16_t fp; intermediate_val = (uint64_t ) val.val * mul.val; intermediate_val = intermediate_val >>16 ; -WARN_ON (intermediate_val >>32 ); - fp.val =clamp_t (uint32_t, intermediate_val,0 , ~0 ); -return fp; -} - -static inline uint_fixed_16_16_t fixed_16_16_div (uint32_t val,uint32_t d) -{ -uint_fixed_16_16_t fp, res; - - fp =u32_to_fixed_16_16 (val); - res.val =DIV_ROUND_UP (fp.val, d); -return res; +return clamp_u64_to_fixed16 (intermediate_val); } -static inline uint_fixed_16_16_t fixed_16_16_div_u64 (uint32_t val,uint32_t d) +static inline uint_fixed_16_16_t div_fixed16 (uint32_t val,uint32_t d) { -uint_fixed_16_16_t res;uint64_t interm_val; interm_val = (uint64_t )val <<16 ; interm_val =DIV_ROUND_UP_ULL (interm_val, d); -WARN_ON (interm_val >>32 ); - res.val = (uint32_t ) interm_val; -return res; +return clamp_u64_to_fixed16 (interm_val); } static inline uint32_t div_round_up_u32_fixed16(uint32_t val,
@@ -225,16 +216,32 @@ static inline uint32_t div_round_up_u32_fixed16(uint32_t val,return clamp_t (uint32_t, interm_val,0 , ~0 ); } -static inline uint_fixed_16_16_t mul_u32_fixed_16_16 (uint32_t val, +static inline uint_fixed_16_16_t mul_u32_fixed16 (uint32_t val,uint_fixed_16_16_t mul) {uint64_t intermediate_val; -uint_fixed_16_16_t fp; intermediate_val = (uint64_t ) val * mul.val; -WARN_ON (intermediate_val >>32 ); - fp.val = (uint32_t ) intermediate_val; -return fp; +return clamp_u64_to_fixed16 (intermediate_val); +} + +static inline uint_fixed_16_16_t add_fixed16 (uint_fixed_16_16_t add1, +uint_fixed_16_16_t add2) +{ +uint64_t interm_sum; + + interm_sum = (uint64_t ) add1.val + add2.val; +return clamp_u64_to_fixed16 (interm_sum); +} + +static inline uint_fixed_16_16_t add_fixed16_u32 (uint_fixed_16_16_t add1, +uint32_t add2) +{ +uint64_t interm_sum; +uint_fixed_16_16_t interm_add2 =u32_to_fixed16 (add2); + + interm_sum = (uint64_t ) add1.val + interm_add2.val; +return clamp_u64_to_fixed16 (interm_sum); }static inline const char *yesno (bool v)
drivers/gpu/drm/i915/intel_pm.c +29 -30
167 lines not on this page · raw message
Signature · 6 lines
2.13.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 1/6] drm/i915: cleanup fixed-point wrappers naming
Mahesh Kumar schreef op di 13-06-2017 om 11:34 [+0530]:
Quoted 11 lines
This patch make naming of fixed-point wrappers consistent operation_<any_post_operation>_<1st operand>_<2nd operand> also shorten the name for
fixed_16_16to fixed16s/u32_to_fixed_16_16/u32_to_fixed16 s/fixed_16_16_to_u32/fixed16_to_u32 s/fixed_16_16_to_u32_round_up/fixed16_to_u32_round_up s/min_fixed_16_16/min_fixed16 s/max_fixed_16_16/max_fixed16 s/mul_u32_fixed_16_16/mul_u32_fixed16
Quoted 8 lines
always do division internal operation in 64 bits:
s/fixed_16_16_div/div_fixed16
s/fixed_16_16_div_64/div_fixed16Introduce Addition wrappers for fixed16
add_fixed16: takes 2fixed_16_16_tvariable & returnsfixed16_16_tadd_fixed16_u32: takesfixed_16_16_t& u32 variable & returnsfixed16_16_t
I think to make it readable, the additions should be done separately.
mul_round_up_u32_fixed16 seems like it should use clamp_u64_to_fixed16, perhaps others too. Maybe do it as a preparation patch so this patch strictly does the renaming for review?
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 1/6] drm/i915: cleanup fixed-point wrappers naming
Quoted 20 lines · Maarten
Mahesh Kumar schreef op di 13-06-2017 om 11:34 [+0530]:
Quoted 11 lines
This patch make naming of fixed-point wrappers consistent operation_<any_post_operation>_<1st operand>_<2nd operand> also shorten the name for
fixed_16_16to fixed16s/u32_to_fixed_16_16/u32_to_fixed16 s/fixed_16_16_to_u32/fixed16_to_u32 s/fixed_16_16_to_u32_round_up/fixed16_to_u32_round_up s/min_fixed_16_16/min_fixed16 s/max_fixed_16_16/max_fixed16 s/mul_u32_fixed_16_16/mul_u32_fixed16
Quoted 8 lines
always do division internal operation in 64 bits:
s/fixed_16_16_div/div_fixed16
s/fixed_16_16_div_64/div_fixed16Introduce Addition wrappers for fixed16
add_fixed16: takes 2fixed_16_16_tvariable & returnsfixed16_16_tadd_fixed16_u32: takesfixed_16_16_t& u32 variable & returnsfixed16_16_t
Quoted 5 lines
I think to make it readable, the additions should be done separately.
mul_round_up_u32_fixed16seems like it should useclamp_u64_to_fixed16, perhaps others too. Maybe do it as a preparation patch so this patch strictly does the renaming for review?
Will break this patch to 3 individual patches.
thanks for review :)
-Mahesh
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 1/6] drm/i915: cleanup fixed-point wrappers naming
Quoted 19 lines · Mahesh Kumar
Quoted 16 lines · Maarten
Mahesh Kumar schreef op di 13-06-2017 om 11:34 [+0530]:
Quoted 15 lines
This patch make naming of fixed-point wrappers consistent operation_<any_post_operation>_<1st operand>_<2nd operand> also shorten the name for
fixed_16_16to fixed16s/u32_to_fixed_16_16/u32_to_fixed16 s/fixed_16_16_to_u32/fixed16_to_u32 s/fixed_16_16_to_u32_round_up/fixed16_to_u32_round_up s/min_fixed_16_16/min_fixed16 s/max_fixed_16_16/max_fixed16 s/mul_u32_fixed_16_16/mul_u32_fixed16
always do division internal operation in 64 bits:
s/fixed_16_16_div/div_fixed16
s/fixed_16_16_div_64/div_fixed16
Quoted 7 lines
Quoted 7 lines
Quoted 4 lines
Introduce Addition wrappers for fixed16
add_fixed16: takes 2fixed_16_16_tvariable & returnsfixed16_16_tadd_fixed16_u32: takesfixed_16_16_t& u32 variable & returnsfixed16_16_tI think to make it readable, the additions should be done separately.
mul_round_up_u32_fixed16seems like it should useclamp_u64_to_fixed16,
In mul_round_up_u32_fixed16 we cann't use clamp_u64_to_fixed16 as this function returns u32, but o/p of clamp_u64_to_fixed16 is fixed_16_16_t
-Mahesh
Quoted 6 lines
Quoted 2 lines
perhaps others too. Maybe do it as a preparation patch so this patch strictly does the renaming for review?
Will break this patch to 3 individual patches.
thanks for review :)
-Mahesh
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 2/6 drm/i915/hsw: use intel_compute_linetime_wm function for linetime wm
In reply to Mahesh Kumarlinetime wm is time taken to fill a single display line with given clock rate, multiplied by 8.
This patch reuses the common code of hsw_compute_linetime_wm & skl_compute_linetime_wm.
--- drivers/gpu/drm/i915/intel_drv.h | 1 + drivers/gpu/drm/i915/intel_pm.c | 23 ++++++++++++++--------- 2 files changed, 15 insertions(+), 9 deletions(-)
drivers/gpu/drm/i915/intel_drv.h +1 -0
@@ -1877,6 +1877,7 @@ bool ilk_disable_lp_wm(struct drm_device *dev);int sanitize_rc6_option (struct drm_i915_private *dev_priv,int enable_rc6);int skl_check_pipe_max_pixel_rate (struct intel_crtc *intel_crtc,struct intel_crtc_state *cstate); +uint32_t intel_compute_linetime_wm (const struct intel_crtc_state *cstate);static inline int intel_enable_rc6 (void ) {return i915.enable_rc6;
drivers/gpu/drm/i915/intel_pm.c +14 -9
@@ -2746,8 +2746,7 @@ hsw_compute_linetime_wm(const struct intel_crtc_state *cstate)/* The WM are computed with base on how long it takes to fill a single * row at the given clock rate, multiplied by 8. * */ - linetime =DIV_ROUND_CLOSEST (adjusted_mode->crtc_htotal *1000 *8 , - adjusted_mode->crtc_clock); + linetime =intel_compute_linetime_wm (cstate); ips_linetime =DIV_ROUND_CLOSEST (adjusted_mode->crtc_htotal *1000 *8 , intel_state->cdclk.logical.cdclk);
@@ -4382,7 +4381,7 @@ static uint_fixed_16_16_t skl_wm_method2(uint32_t pixel_rate, }static uint_fixed_16_16_t -intel_get_linetime_us (struct intel_crtc_state *cstate) +intel_get_linetime_us (const struct intel_crtc_state *cstate) {uint32_t pixel_rate;uint32_t crtc_htotal;
@@ -4604,20 +4603,26 @@ skl_compute_wm_levels(const struct drm_i915_private *dev_priv,return 0 ; } -static uint32_t -skl_compute_linetime_wm (struct intel_crtc_state *cstate) +uint32_t intel_compute_linetime_wm (const struct intel_crtc_state *cstate) { -struct drm_atomic_state *state = cstate->base.state; -struct drm_i915_private *dev_priv =to_i915 (state->dev);uint_fixed_16_16_t linetime_us; -uint32_t linetime_wm; linetime_us =intel_get_linetime_us (cstate);if (is_fixed16_zero (linetime_us))return 0 ; - linetime_wm =fixed16_to_u32_round_up (mul_u32_fixed16 (8 , linetime_us)); +return fixed16_to_u32_round_up (mul_u32_fixed16 (8 , linetime_us)); +} + +static uint32_t +skl_compute_linetime_wm (struct intel_crtc_state *cstate) +{ +struct drm_atomic_state *state = cstate->base.state; +struct drm_i915_private *dev_priv =to_i915 (state->dev); +uint32_t linetime_wm; + + linetime_wm =intel_compute_linetime_wm (cstate);/* Display WA #1135: bxt. */ if (IS_BROXTON (dev_priv) && dev_priv->ipc_enabled)
Signature · 6 lines
2.13.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 2/6] drm/i915/hsw: use intel_compute_linetime_wm function for linetime wm
Mahesh Kumar schreef op di 13-06-2017 om 11:34 [+0530]:
Quoted 18 lines
linetime wm is time taken to fill a single display line with given clock
rate, multiplied by 8.
This patch reuses the common code ofhsw_compute_linetime_wm&skl_compute_linetime_wm.Signed-off-by Mahesh Kumar <[email protected]>---
drivers/gpu/drm/i915/intel_drv.h | 1 + drivers/gpu/drm/i915/intel_pm.c | 23 ++++++++++++++---------2 files changed, 15 insertions(+), 9 deletions(-)drivers/gpu/drm/i915/intel_drv.h +0
-0@@ -1877,6 +1877,7 @@ bool ilk_disable_lp_wm(struct drm_device *dev);
Quoted 6 lines
int
sanitize_rc6_option(struct drm_i915_private *dev_priv, int enable_rc6);
intskl_check_pipe_max_pixel_rate(struct intel_crtc *intel_crtc, struct intel_crtc_state *cstate); +uint32_tintel_compute_linetime_wm(const struct intel_crtc_state *cstate);
This function is only used inside intel_pm.c, so should only be declared there. :)
~Maarten
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 2/6] drm/i915/hsw: use intel_compute_linetime_wm function for linetime wm
Quoted 13 lines · Maarten
Mahesh Kumar schreef op di 13-06-2017 om 11:34 [+0530]:
Quoted 12 lines
linetime wm is time taken to fill a single display line with given clock
rate, multiplied by 8.
This patch reuses the common code ofhsw_compute_linetime_wm&skl_compute_linetime_wm.Signed-off-by Mahesh Kumar <[email protected]>--- drivers/gpu/drm/i915/intel_drv.h | 1 + drivers/gpu/drm/i915/intel_pm.c | 23 ++++++++++++++--------- 2 files changed, 15 insertions(+), 9 deletions(-)
Quoted 14 lines
drivers/gpu/drm/i915/intel_drv.h bool ilk_disable_lp_wm(struct drm_device *dev); · line 1882
Quoted 12 lines
drivers/gpu/drm/i915/intel_drv.h +1
-0@@ -1877,6 +1877,7 @@ bool ilk_disable_lp_wm(struct drm_device *dev);int sanitize_rc6_option (struct drm_i915_private *dev_priv,int enable_rc6);int skl_check_pipe_max_pixel_rate (struct intel_crtc *intel_crtc,struct intel_crtc_state *cstate); +uint32_t intel_compute_linetime_wm (const struct intel_crtc_state *cstate);This function is only used inside
intel_pm.c, so should only be declared there. :)
ok will reorganize..
-Mahesh
Quoted 2 lines
~Maarten
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 2/6] drm/i915/hsw: use intel_compute_linetime_wm function for linetime wm
In reply to Mahesh KumarQuoted 28 lines · Mahesh Kumar
linetime wm is time taken to fill a single display line with given clock rate, multiplied by 8.
This patch reuses the common code ofhsw_compute_linetime_wm&skl_compute_linetime_wm.Signed-off-by Mahesh Kumar <[email protected]>--- drivers/gpu/drm/i915/intel_drv.h | 1 + drivers/gpu/drm/i915/intel_pm.c | 23 ++++++++++++++--------- 2 files changed, 15 insertions(+), 9 deletions(-)drivers/gpu/drm/i915/intel_drv.h +1
-0@@ -1877,6 +1877,7 @@ bool ilk_disable_lp_wm(struct drm_device *dev);int sanitize_rc6_option (struct drm_i915_private *dev_priv,int enable_rc6);int skl_check_pipe_max_pixel_rate (struct intel_crtc *intel_crtc,struct intel_crtc_state *cstate); +uint32_t intel_compute_linetime_wm (const struct intel_crtc_state *cstate);static inline int intel_enable_rc6 (void ) {return i915.enable_rc6;drivers/gpu/drm/i915/intel_pm.c +0
-0
drivers/gpu/drm/i915/intel_pm.c hsw_compute_linetime_wm(const struct intel_crtc_state *cstate) · line 2749
Quoted 6 lines
drivers/gpu/drm/i915/intel_pm.c +1
-2@@ -2746,8 +2746,7 @@ hsw_compute_linetime_wm(const struct intel_crtc_state *cstate)/* The WM are computed with base on how long it takes to fill a single * row at the given clock rate, multiplied by 8. * */ - linetime =DIV_ROUND_CLOSEST (adjusted_mode->crtc_htotal *1000 *8 , - adjusted_mode->crtc_clock); + linetime =intel_compute_linetime_wm (cstate);
HSW/BDW spec says "The WM_LINETIME register Line Time field (bits 8:0) is not adjusted for panel fitter down scaling.", so NAK.
Quoted 22 lines
drivers/gpu/drm/i915/intel_pm.c +2
-5ips_linetime =DIV_ROUND_CLOSEST (adjusted_mode->crtc_htotal *1000 *8 , intel_state->cdclk.logical.cdclk);@@ -4382,7 +4381,7 @@ static uint_fixed_16_16_t skl_wm_method2(uint32_t pixel_rate, }static uint_fixed_16_16_t -intel_get_linetime_us (struct intel_crtc_state *cstate) +intel_get_linetime_us (const struct intel_crtc_state *cstate) {uint32_t pixel_rate;uint32_t crtc_htotal;@@ -4604,20 +4603,26 @@ skl_compute_wm_levels(const struct drm_i915_private *dev_priv,return 0 ; } -static uint32_t -skl_compute_linetime_wm (struct intel_crtc_state *cstate) +uint32_t intel_compute_linetime_wm (const struct intel_crtc_state *cstate) { -struct drm_atomic_state *state = cstate->base.state; -struct drm_i915_private *dev_priv =to_i915 (state->dev);
drivers/gpu/drm/i915/intel_pm.c skl_compute_wm_levels(const struct drm_i915_private *dev_priv, · line 4615
Quoted 10 lines
drivers/gpu/drm/i915/intel_pm.c +1
-2uint_fixed_16_16_t linetime_us; -uint32_t linetime_wm; linetime_us =intel_get_linetime_us (cstate);if (is_fixed16_zero (linetime_us))return 0 ; - linetime_wm =fixed16_to_u32_round_up (mul_u32_fixed16 (8 , linetime_us)); +return fixed16_to_u32_round_up (mul_u32_fixed16 (8 , linetime_us));
Am I the only one that finds this fixed16 stuff totally illegible? This is also inefficient since it's doing multiple divisions where one would suffice. I'd prefer people just wrote the code the in the obvious (and more optimal) way.
Quoted 20 lines
drivers/gpu/drm/i915/intel_pm.c +10
-0+} + +static uint32_t +skl_compute_linetime_wm (struct intel_crtc_state *cstate) +{ +struct drm_atomic_state *state = cstate->base.state; +struct drm_i915_private *dev_priv =to_i915 (state->dev); +uint32_t linetime_wm; + + linetime_wm =intel_compute_linetime_wm (cstate);/* Display WA #1135: bxt. */ if (IS_BROXTON (dev_priv) && dev_priv->ipc_enabled)Signature · 6 lines
2.13.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Signature · 6 lines
Ville Syrjälä Intel OTC _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 2/6] drm/i915/hsw: use intel_compute_linetime_wm function for linetime wm
Hi,
Quoted 29 lines · Ville Syrjälä
Quoted 28 lines · Mahesh Kumar
linetime wm is time taken to fill a single display line with given clock rate, multiplied by 8.
This patch reuses the common code ofhsw_compute_linetime_wm&skl_compute_linetime_wm.Signed-off-by Mahesh Kumar <[email protected]>--- drivers/gpu/drm/i915/intel_drv.h | 1 + drivers/gpu/drm/i915/intel_pm.c | 23 ++++++++++++++--------- 2 files changed, 15 insertions(+), 9 deletions(-)drivers/gpu/drm/i915/intel_drv.h +1
-0@@ -1877,6 +1877,7 @@ bool ilk_disable_lp_wm(struct drm_device *dev);int sanitize_rc6_option (struct drm_i915_private *dev_priv,int enable_rc6);int skl_check_pipe_max_pixel_rate (struct intel_crtc *intel_crtc,struct intel_crtc_state *cstate); +uint32_t intel_compute_linetime_wm (const struct intel_crtc_state *cstate);static inline int intel_enable_rc6 (void ) {return i915.enable_rc6;drivers/gpu/drm/i915/intel_pm.c +0
-0@@ -2746,8 +2746,7 @@ hsw_compute_linetime_wm(const struct intel_crtc_state *cstate)
Quoted 8 lines
drivers/gpu/drm/i915/intel_pm.c hsw_compute_linetime_wm(const struct intel_crtc_state *cstate) · line 2749
Quoted 6 lines
drivers/gpu/drm/i915/intel_pm.c +1
-2/* The WM are computed with base on how long it takes to fill a single * row at the given clock rate, multiplied by 8. * */ - linetime =DIV_ROUND_CLOSEST (adjusted_mode->crtc_htotal *1000 *8 , - adjusted_mode->crtc_clock); + linetime =intel_compute_linetime_wm (cstate);HSW/BDW spec says "The
WM_LINETIMEregister Line Time field (bits 8:0) is not adjusted for panel fitter down scaling.", so NAK.
ok...
Quoted 31 lines
Quoted 31 lines
drivers/gpu/drm/i915/intel_pm.c +2
-6ips_linetime =DIV_ROUND_CLOSEST (adjusted_mode->crtc_htotal *1000 *8 , intel_state->cdclk.logical.cdclk);@@ -4382,7 +4381,7 @@ static uint_fixed_16_16_t skl_wm_method2(uint32_t pixel_rate, }static uint_fixed_16_16_t -intel_get_linetime_us (struct intel_crtc_state *cstate) +intel_get_linetime_us (const struct intel_crtc_state *cstate) {uint32_t pixel_rate;uint32_t crtc_htotal;@@ -4604,20 +4603,26 @@ skl_compute_wm_levels(const struct drm_i915_private *dev_priv,return 0 ; } -static uint32_t -skl_compute_linetime_wm (struct intel_crtc_state *cstate) +uint32_t intel_compute_linetime_wm (const struct intel_crtc_state *cstate) { -struct drm_atomic_state *state = cstate->base.state; -struct drm_i915_private *dev_priv =to_i915 (state->dev);uint_fixed_16_16_t linetime_us; -uint32_t linetime_wm; linetime_us =intel_get_linetime_us (cstate);if (is_fixed16_zero (linetime_us))return 0 ;
Quoted 6 lines
drivers/gpu/drm/i915/intel_pm.c skl_compute_wm_levels(const struct drm_i915_private *dev_priv, · line 4615
Quoted 2 lines
drivers/gpu/drm/i915/intel_pm.c +1
-1- linetime_wm =fixed16_to_u32_round_up (mul_u32_fixed16 (8 , linetime_us)); +return fixed16_to_u32_round_up (mul_u32_fixed16 (8 , linetime_us));Am I the only one that finds this fixed16 stuff totally illegible? This is also inefficient since it's doing multiple divisions where one would suffice. I'd prefer people just wrote the code the in the obvious (and more optimal) way.
better late than never. let's discuss & optimize fixed16 :)
-Mahesh
Quoted 17 lines
Quoted 17 lines
drivers/gpu/drm/i915/intel_pm.c +10
-0+} + +static uint32_t +skl_compute_linetime_wm (struct intel_crtc_state *cstate) +{ +struct drm_atomic_state *state = cstate->base.state; +struct drm_i915_private *dev_priv =to_i915 (state->dev); +uint32_t linetime_wm; + + linetime_wm =intel_compute_linetime_wm (cstate);/* Display WA #1135: bxt. */ if (IS_BROXTON (dev_priv) && dev_priv->ipc_enabled)Signature · 1 line
2.13.0
Quoted 4 lines
Quoted 4 lines
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 3/6 drm/i915/skl+: WM calculation don't require height
In reply to Mahesh Kumarheight of plane was require to swap width/height in case of 90/270 rotation. Now src structure contains already swapped values, So we don't have to calculate height of the plane.
--- drivers/gpu/drm/i915/intel_pm.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)
drivers/gpu/drm/i915/intel_pm.c +1 -3
@@ -4441,7 +4441,7 @@ static int skl_compute_plane_wm(const struct drm_i915_private *dev_priv,uint32_t plane_bytes_per_line;uint32_t res_blocks, res_lines;uint8_t cpp; -uint32_t width =0 , height =0 ; +uint32_t width =0 ;uint32_t plane_pixel_rate;uint_fixed_16_16_t y_tile_minimum;uint32_t y_min_scanlines;
@@ -4468,7 +4468,6 @@ static int skl_compute_plane_wm(const struct drm_i915_private *dev_priv,if (plane->id ==PLANE_CURSOR ) { width = intel_pstate->base.crtc_w; - height = intel_pstate->base.crtc_h; }else {/* * Src coordinates are already rotated by 270 degrees for
@@ -4476,7 +4475,6 @@ static int skl_compute_plane_wm(const struct drm_i915_private *dev_priv,* GTT mapping), hence no need to account for rotation here. */ width =drm_rect_width (&intel_pstate->base.src) >>16 ; - height =drm_rect_height (&intel_pstate->base.src) >>16 ; } cpp = fb->format->cpp[0 ];
Signature · 6 lines
2.13.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 4/6 drm/i915/skl+: unify cpp value in WM calculation
In reply to Mahesh Kumaruse same cpp value in different phase of plane WM caluclation.
--- drivers/gpu/drm/i915/intel_pm.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-)
drivers/gpu/drm/i915/intel_pm.c +2 -4
@@ -4477,13 +4477,11 @@ static int skl_compute_plane_wm(const struct drm_i915_private *dev_priv, width =drm_rect_width (&intel_pstate->base.src) >>16 ; } - cpp = fb->format->cpp[0 ]; + cpp = (fb->format->format ==DRM_FORMAT_NV12 ) ? fb->format->cpp[1 ] : + fb->format->cpp[0 ]; plane_pixel_rate =skl_adjusted_plane_pixel_rate (cstate, intel_pstate);if (drm_rotation_90_or_270 (pstate->rotation)) { -int cpp = (fb->format->format ==DRM_FORMAT_NV12 ) ? - fb->format->cpp[1 ] : - fb->format->cpp[0 ];switch (cpp) {case 1 :
Signature · 6 lines
2.13.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 5/6 drm/i915/skl+: Optimize WM calculation
In reply to Mahesh KumarPlane configuration parameters doesn't change for each WM-level calculation. Currently we compute same parameters 8 times for each wm-level.
This patch optimizes it by calculating these parameters in beginning & reuse during each level-wm calculation.
--- drivers/gpu/drm/i915/i915_drv.h | 13 ++++ drivers/gpu/drm/i915/intel_pm.c | 169 ++++++++++++++++++++++------------------ 2 files changed, 107 insertions(+), 75 deletions(-)
drivers/gpu/drm/i915/i915_drv.h +13 -0
@@ -1777,6 +1777,19 @@ struct skl_wm_level {uint8_t plane_res_l; }; +/* Stores plane specific WM parameters */ +struct skl_wm_params { +bool x_tiled, y_tiled; +uint32_t width; +uint8_t cpp; +uint32_t plane_pixel_rate; +uint32_t y_min_scanlines; +uint32_t plane_bytes_per_line; +uint_fixed_16_16_t plane_blocks_per_line; +uint_fixed_16_16_t y_tile_minimum; +uint32_t linetime_us; +}; +/* * This struct helps tracking the state needed for runtime PM, which puts the * device in PCI D3 state. Notice that when this happens, nothing on the
drivers/gpu/drm/i915/intel_pm.c +94 -75
249 lines not on this page · raw message
Signature · 6 lines
2.13.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 6/6 drm/i915/gen10: Calculate and enable transition WM
In reply to Mahesh KumarGEN > 9 require transition WM to be programmed if IPC is enabled. This patch calculates & enable transition WM for supported platforms. If transition WM is enabled, Plane read requests are sent at high priority until filling above the transition watermark, then the requests are sent at lower priority until dropping below the level-0 WM. The lower priority requests allow other memory clients to have better memory access.
transition minimum is the minimum amount needed for trans_wm to work to ensure the demote does not happen before enough data has been read to meet the level 0 watermark requirements.
transition amount is configurable value. Higher values will tend to cause longer periods of high priority reads followed by longer periods of lower priority reads. Tuning to lower values will tend to cause shorter periods of high and lower priority reads.
Keeping transition amount to 0 in this patch.
--- drivers/gpu/drm/i915/intel_pm.c | 51 ++++++++++++++++++++++++++++++++++++++--- 1 file changed, 48 insertions(+), 3 deletions(-)
drivers/gpu/drm/i915/intel_pm.c +48 -3
@@ -4163,6 +4163,15 @@ skl_enable_plane_wm_levels(const struct drm_i915_private *dev_priv, level_wm->plane_en = true; } } + +/* +* Unsupported GEN will have plane_res_b = 0 & transition WM for +* them will get disabled here. +*/ +if (wm->trans_wm.plane_res_b && wm->trans_wm.plane_res_b < plane_ddb) + wm->trans_wm.plane_en = true; +else + wm->trans_wm.plane_en = false; } static int
@@ -4639,13 +4648,48 @@ skl_compute_linetime_wm(struct intel_crtc_state *cstate) }static void skl_compute_transition_wm (struct intel_crtc_state *cstate, +struct skl_wm_params *wp, +struct skl_wm_level *wm_l0,struct skl_wm_level *trans_wm/* out */ ) { +struct drm_device *dev = cstate->base.crtc->dev; +const struct drm_i915_private *dev_priv =to_i915 (dev); +uint16_t trans_min, trans_y_tile_min; +uint16_t trans_amount =0 ;/* This is configurable amount */ +uint16_t trans_offset_b, res_blocks; +if (!cstate->base.active)return ; -/* Until we know more, just disable transition WMs */ - trans_wm->plane_en = false; +/* Transition WM are not recommended by HW team for GEN9 */ +if (INTEL_GEN (dev_priv) <=9 ) +return ; + +/* Transition WM don't have any impact if ipc is disabled */ +if (!dev_priv->ipc_enabled) +return ; + +if (INTEL_GEN (dev_priv) >=10 ) + trans_min =4 ; + + trans_offset_b = trans_min + trans_amount; + trans_y_tile_min = (uint16_t )mul_round_up_u32_fixed16 (2 , + wp->y_tile_minimum); + +if (wp->y_tiled) { + res_blocks =max (wm_l0->plane_res_b, trans_y_tile_min) + + trans_offset_b; + }else { + res_blocks = wm_l0->plane_res_b + trans_offset_b; + } + + res_blocks +=1 ; + +/* WA BUG:1938466 add one block for non y-tile planes */ +if (!wp->y_tiled &&IS_CNL_REVID (dev_priv,CNL_REVID_A0 ,CNL_REVID_A0 )) + res_blocks +=1 ; + + trans_wm->plane_res_b = res_blocks; } static int skl_build_pipe_wm(struct intel_crtc_state *cstate,
@@ -4684,7 +4728,8 @@ static int skl_build_pipe_wm(struct intel_crtc_state *cstate, &wm_params, wm);if (ret)return ret; -skl_compute_transition_wm (cstate, &wm->trans_wm); +skl_compute_transition_wm (cstate, &wm_params, &wm->wm[0 ], + &wm->trans_wm); } pipe_wm->linetime =skl_compute_linetime_wm (cstate);
Signature · 6 lines
2.13.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 6/6] drm/i915/gen10: Calculate and enable transition WM
Hey,
Mahesh Kumar schreef op di 13-06-2017 om 11:34 [+0530]:
Quoted 72 lines
GEN > 9 require transition WM to be programmed if IPC is enabled. This patch calculates & enable transition WM for supported platforms. If transition WM is enabled, Plane read requests are sent at high priority until filling above the transition watermark, then the requests are sent at lower priority until dropping below the level-0 WM.
The lower priority requests allow other memory clients to have better memory access.transition minimum is the minimum amount needed for
trans_wmto work to
ensure the demote does not happen before enough data has been read to
meet the level 0 watermark requirements.transition amount is configurable value. Higher values will tend to cause longer periods of high priority reads followed by longer
periods of lower priority reads. Tuning to lower values will tend to cause shorter periods of high and lower priority reads.Keeping transition amount to 0 in this patch.
Signed-off-by Mahesh Kumar <[email protected]>---
drivers/gpu/drm/i915/intel_pm.c | 51
++++++++++++++++++++++++++++++++++++++---1 file changed, 48 insertions(+), 3 deletions(-)drivers/gpu/drm/i915/intel_pm.c +3
-0@@ -4163,6 +4163,15 @@ skl_enable_plane_wm_levels(const structdrm_i915_private *dev_priv, level_wm->plane_en = true; } } + +/* +* Unsupported GEN will have plane_res_b = 0 & transition WM for
drivers/gpu/drm/i915/intel_pm.c +3
-0+* them will get disabled here. +*/ + if (wm->trans_wm.plane_res_b && wm->trans_wm.plane_res_b <
plane_ddb)drivers/gpu/drm/i915/intel_pm.c +3
-0+ wm->trans_wm.plane_en = true; + else + wm->trans_wm.plane_en = false;}
static intdrivers/gpu/drm/i915/intel_pm.c +0
-0@@ -4639,13 +4648,48 @@ skl_compute_linetime_wm(struct intel_crtc_state *cstate) }
static void skl_compute_transition_wm(structintel_crtc_state*cstate,drivers/gpu/drm/i915/intel_pm.c +2
-0+ struct skl_wm_params *wp, + struct skl_wm_level *wm_l0,struct
skl_wm_level*trans_wm/* out */)
{drivers/gpu/drm/i915/intel_pm.c +6
-0+struct drm_device *dev = cstate->base.crtc->dev; +const struct drm_i915_private *dev_priv =to_i915 (dev); +uint16_t trans_min, trans_y_tile_min; +uint16_t trans_amount =0 ;/* This is configurable amount */ +uint16_t trans_offset_b, res_blocks; +if (!cstate->base.active)
return;
drivers/gpu/drm/i915/intel_pm.c skl_compute_linetime_wm(struct intel_crtc_state *cstate) · line 4670
Quoted 9 lines
drivers/gpu/drm/i915/intel_pm.c +7
-2-/* Until we know more, just disable transition WMs */ - trans_wm->plane_en = false; +/* Transition WM are not recommended by HW team for GEN9 */ +if (INTEL_GEN (dev_priv) <=9 ) +return ; + +/* Transition WM don't have any impact if ipc is disabled */ +if (!dev_priv->ipc_enabled) +return ;
ipc_enabled is never set, so this patch on its own doesn't do much. :)
Otherwise series looks good, I didn't check the math on this patch, but the series doesn't regress KBL.
For patch 3 and 4:
For patch 5 and 6:
Quoted 37 lines
drivers/gpu/drm/i915/intel_pm.c +6
-0+if (INTEL_GEN (dev_priv) >=10 ) + trans_min =4 ; + + trans_offset_b = trans_min + trans_amount; + trans_y_tile_min = (uint16_t) mul_round_up_u32_fixed16(2, + wp-Quoted 1 line
y_tile_minimum);drivers/gpu/drm/i915/intel_pm.c +3
-0+ +if (wp->y_tiled) { + res_blocks = max(wm_l0->plane_res_b,
trans_y_tile_min) +drivers/gpu/drm/i915/intel_pm.c +9
-0+ trans_offset_b; + } else { + res_blocks = wm_l0->plane_res_b + trans_offset_b; + } + + res_blocks +=1 ; + +/* WA BUG:1938466 add one block for non y-tile planes */ + if (!wp->y_tiled && IS_CNL_REVID(dev_priv, CNL_REVID_A0,
CNL_REVID_A0))drivers/gpu/drm/i915/intel_pm.c +3
-0+ res_blocks +=1 ; + + trans_wm->plane_res_b = res_blocks;}
static int skl_build_pipe_wm(structintel_crtc_state*cstate,drivers/gpu/drm/i915/intel_pm.c +2
-1@@ -4684,7 +4728,8 @@ static int skl_build_pipe_wm(structintel_crtc_state *cstate, &wm_params, wm); if (ret) return ret; -skl_compute_transition_wm (cstate, &wm->trans_wm); +skl_compute_transition_wm (cstate, &wm_params, &wm- >wm[0], + &wm->trans_wm); }
Quoted 2 lines
pipe_wm->linetime=skl_compute_linetime_wm(cstate);
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 6/6] drm/i915/gen10: Calculate and enable transition WM
Hi,
Quoted 76 lines · Maarten
Hey,
Mahesh Kumar schreef op di 13-06-2017 om 11:34 [+0530]:
Quoted 73 lines
GEN > 9 require transition WM to be programmed if IPC is enabled. This patch calculates & enable transition WM for supported platforms. If transition WM is enabled, Plane read requests are sent at high priority until filling above the transition watermark, then the requests are sent at lower priority until dropping below the level-0 WM.
The lower priority requests allow other memory clients to have better memory access.transition minimum is the minimum amount needed for
trans_wmto work to
ensure the demote does not happen before enough data has been read to
meet the level 0 watermark requirements.transition amount is configurable value. Higher values will tend to cause longer periods of high priority reads followed by longer
periods of lower priority reads. Tuning to lower values will tend to cause shorter periods of high and lower priority reads.Keeping transition amount to 0 in this patch.
Signed-off-by Mahesh Kumar <[email protected]>--- drivers/gpu/drm/i915/intel_pm.c | 51 ++++++++++++++++++++++++++++++++++++++--- 1 file changed, 48 insertions(+), 3 deletions(-)drivers/gpu/drm/i915/intel_pm.c +3
-0@@ -4163,6 +4163,15 @@ skl_enable_plane_wm_levels(const struct drm_i915_private *dev_priv, level_wm->plane_en = true; } } + +/* +* Unsupported GEN will have plane_res_b = 0 & transition WM for
drivers/gpu/drm/i915/intel_pm.c +3
-0+* them will get disabled here. +*/ + if (wm->trans_wm.plane_res_b && wm->trans_wm.plane_res_b <
plane_ddb)drivers/gpu/drm/i915/intel_pm.c +11
-2+ wm->trans_wm.plane_en = true; + else + wm->trans_wm.plane_en = false; } static int@@ -4639,13 +4648,48 @@ skl_compute_linetime_wm(struct intel_crtc_state *cstate) }static void skl_compute_transition_wm (struct intel_crtc_state *cstate, +struct skl_wm_params *wp, +struct skl_wm_level *wm_l0,struct skl_wm_level *trans_wm/* out */ ) { +struct drm_device *dev = cstate->base.crtc->dev; +const struct drm_i915_private *dev_priv =to_i915 (dev); +uint16_t trans_min, trans_y_tile_min; +uint16_t trans_amount =0 ;/* This is configurable amount */ +uint16_t trans_offset_b, res_blocks; +if (!cstate->base.active)return ; -/* Until we know more, just disable transition WMs */ - trans_wm->plane_en = false;
Quoted 8 lines
drivers/gpu/drm/i915/intel_pm.c skl_compute_linetime_wm(struct intel_crtc_state *cstate) · line 4670
Quoted 7 lines
drivers/gpu/drm/i915/intel_pm.c +7
-0+/* Transition WM are not recommended by HW team for GEN9 */ +if (INTEL_GEN (dev_priv) <=9 ) +return ; + +/* Transition WM don't have any impact if ipc is disabled */ +if (!dev_priv->ipc_enabled) +return ;
ipc_enabledis never set, so this patch on its own doesn't do much. :)
If I enable IPC, I observed many fifo underrun in only fi-glk, that's the reason I didn't push IPC patch. I'll debug further for under-run in glk with IPC & post that patch later.
thanks for review :)
-Mahesh
Quoted 43 lines
Otherwise series looks good, I didn't check the math on this patch, but the series doesn't regress KBL.
For patch 3 and 4:
Reviewed-by Maarten Lankhorst <[email protected]>For patch 5 and 6:
Quoted 34 lines
drivers/gpu/drm/i915/intel_pm.c +9
-0+if (INTEL_GEN (dev_priv) >=10 ) + trans_min =4 ; + + trans_offset_b = trans_min + trans_amount; + trans_y_tile_min = (uint16_t )mul_round_up_u32_fixed16 (2 , + wp- > y_tile_minimum); + +if (wp->y_tiled) { + res_blocks = max(wm_l0->plane_res_b,
trans_y_tile_min) +drivers/gpu/drm/i915/intel_pm.c +9
-0+ trans_offset_b; + } else { + res_blocks = wm_l0->plane_res_b + trans_offset_b; + } + + res_blocks +=1 ; + +/* WA BUG:1938466 add one block for non y-tile planes */ + if (!wp->y_tiled && IS_CNL_REVID(dev_priv, CNL_REVID_A0,
CNL_REVID_A0))drivers/gpu/drm/i915/intel_pm.c +4
-1+ res_blocks +=1 ; + + trans_wm->plane_res_b = res_blocks; } static int skl_build_pipe_wm(struct intel_crtc_state *cstate,@@ -4684,7 +4728,8 @@ static int skl_build_pipe_wm(struct intel_crtc_state *cstate, &wm_params, wm);if (ret)return ret; -skl_compute_transition_wm (cstate, &wm->trans_wm); + skl_compute_transition_wm(cstate, &wm_params, &wm-
Quoted 5 lines
Quoted 5 lines
drivers/gpu/drm/i915/intel_pm.c +1
-0> wm[0], + &wm->trans_wm); }pipe_wm->linetime = skl_compute_linetime_wm(cstate);
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI✓ Fi.CI.BAT: success for Fixed16.16 wrapper cleanup & wm optimization
In reply to Mahesh Kumar== Series Details ==
== Series Details ==
Series: Fixed16.16 wrapper cleanup & wm optimization
URL : https://patchwork.freedesktop.org/series/25692/
State : success
== Summary ==
Series 25692v1 Fixed16.16 wrapper cleanup & wm optimization
https://patchwork.freedesktop.org/api/1.0/series/25692/revisions/1/mbox/
fi-bdw-5557u total:278 pass:267 dwarn:0 dfail:0 fail:0 skip:11 time:450s fi-bdw-gvtdvm total:278 pass:256 dwarn:8 dfail:0 fail:0 skip:14 time:433s fi-bsw-n3050 total:278 pass:242 dwarn:0 dfail:0 fail:0 skip:36 time:580s fi-bxt-j4205 total:278 pass:259 dwarn:0 dfail:0 fail:0 skip:19 time:506s fi-byt-j1900 total:278 pass:254 dwarn:0 dfail:0 fail:0 skip:24 time:486s fi-byt-n2820 total:278 pass:250 dwarn:0 dfail:0 fail:0 skip:28 time:488s fi-glk-2a total:278 pass:259 dwarn:0 dfail:0 fail:0 skip:19 time:583s fi-hsw-4770 total:278 pass:262 dwarn:0 dfail:0 fail:0 skip:16 time:436s fi-hsw-4770r total:278 pass:262 dwarn:0 dfail:0 fail:0 skip:16 time:408s fi-ilk-650 total:278 pass:228 dwarn:0 dfail:0 fail:0 skip:50 time:418s fi-ivb-3520m total:278 pass:260 dwarn:0 dfail:0 fail:0 skip:18 time:489s fi-ivb-3770 total:278 pass:260 dwarn:0 dfail:0 fail:0 skip:18 time:462s fi-kbl-7500u total:278 pass:260 dwarn:0 dfail:0 fail:0 skip:18 time:469s fi-kbl-7560u total:278 pass:268 dwarn:0 dfail:0 fail:0 skip:10 time:567s fi-kbl-r total:278 pass:259 dwarn:1 dfail:0 fail:0 skip:18 time:574s fi-skl-6260u total:278 pass:268 dwarn:0 dfail:0 fail:0 skip:10 time:459s fi-skl-6700hq total:278 pass:228 dwarn:1 dfail:0 fail:27 skip:22 time:409s fi-skl-6700k total:278 pass:256 dwarn:4 dfail:0 fail:0 skip:18 time:467s fi-skl-6770hq total:278 pass:268 dwarn:0 dfail:0 fail:0 skip:10 time:479s fi-skl-gvtdvm total:278 pass:265 dwarn:0 dfail:0 fail:0 skip:13 time:440s fi-snb-2520m total:278 pass:250 dwarn:0 dfail:0 fail:0 skip:28 time:541s fi-snb-2600 total:278 pass:249 dwarn:0 dfail:0 fail:0 skip:29 time:403s
4f89fbd3f94f4ba47f779909a2c7bcd1cfb958ad drm-tip: 2017y-06m-12d-19h-18m-52s UTC integration manifest 43dd5fc drm/i915/gen10: Calculate and enable transition WM
e2a1084 drm/i915/skl+: Optimize WM calculation
473b847 drm/i915/skl+: unify cpp value in WM calculation
c467933 drm/i915/skl+: WM calculation don't require height
6788da2 drm/i915/hsw: use intel_compute_linetime_wm function for linetime wm
52e9ecd drm/i915: cleanup fixed-point wrappers naming
== Logs ==
For more details see: https://intel-gfx-ci.01.org/CI/Patchwork_4937/
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx