drm/i915: Redo VLV/CHV watermark code
Subsystems (2)
cover drm/i915: Redo VLV/CHV watermark code
From: Ville Syrjälä <[email protected]>
The main motivation behind this series is to get the display to be stable on CHV. Some new memory power savings features got enabled on later steppings/BIOS versions which caused all kinds of display troubles with our current code.
There are still a few known (at least known to me) display blink issues left after this series, but those have something to do with the PHY, and I'll post another series to address them.
Vidya Srinivas (1):
drm/i915: Program PFI credits for VLV
Ville Syrjälä (11):
drm/i915: Reduce CHV DDL multiplier to 16/8 drm/i915: Kill DRAIN_LATENCY_PRECISION_* defines drm/i915: Simplify VLV drain latency computation drm/i915: Hide VLV DDL precision handling
drm/i915: Reorganize VLV DDL setup
drm/i915: Pass plane to vlv_compute_drain_latency() drm/i915: Read out display FIFO size on VLV/CHV drm/i915: Make sure PND deadline mode is enabled on VLV/CHV drm/i915: Rewrite VLV/CHV watermark code
drm/i915: Support maxfifo with two planes on CHV drm/i915: Enable the maxfifo PM5 mode when appropriate on CHV
drivers/gpu/drm/i915/i915_drv.h | 20 ++ drivers/gpu/drm/i915/i915_reg.h | 32 ++- drivers/gpu/drm/i915/intel_display.c | 33 +++ drivers/gpu/drm/i915/intel_pm.c | 537 ++++++++++++++++++++--------------- 4 files changed, 385 insertions(+), 237 deletions(-)
Signature · 6 lines
2.0.5 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 1/12 drm/i915: Reduce CHV DDL multiplier to 16/8
From: Ville Syrjälä <[email protected]>
Apparently we must yet halve the DDL drain latency from what we're using currently. This little nugget is not in any spec, but came down through the grapevine.
This makes the displays a bit more stable. Not quite fully stable but at least they don't fall over immediately on driver load.
--- drivers/gpu/drm/i915/i915_reg.h | 1 + drivers/gpu/drm/i915/intel_pm.c | 6 +++--- 2 files changed, 4 insertions(+), 3 deletions(-)
drivers/gpu/drm/i915/i915_reg.h +1 -0
@@ -4166,6 +4166,7 @@ enum skl_disp_power_wells {#define DSPFW_PLANEA_WM1_HI_MASK (1<<0)/* drain latency register values*/ +#define DRAIN_LATENCY_PRECISION_8 8#define DRAIN_LATENCY_PRECISION_16 16#define DRAIN_LATENCY_PRECISION_32 32#define DRAIN_LATENCY_PRECISION_64 64
drivers/gpu/drm/i915/intel_pm.c +3 -3
@@ -728,8 +728,8 @@ static bool vlv_compute_drain_latency(struct drm_crtc *crtc, entries =DIV_ROUND_UP (clock,1000 ) * pixel_size;if (IS_CHERRYVIEW (dev)) - *prec_mult = (entries >128 ) ?DRAIN_LATENCY_PRECISION_32 : -DRAIN_LATENCY_PRECISION_16 ; + *prec_mult = (entries >32 ) ?DRAIN_LATENCY_PRECISION_16 : +DRAIN_LATENCY_PRECISION_8 ;else *prec_mult = (entries >128 ) ?DRAIN_LATENCY_PRECISION_64 :DRAIN_LATENCY_PRECISION_32 ;
@@ -759,7 +759,7 @@ static void vlv_update_drain_latency(struct drm_crtc *crtc)enum pipe pipe = intel_crtc->pipe;int plane_prec, prec_mult, plane_dl;const int high_precision =IS_CHERRYVIEW (dev) ? -DRAIN_LATENCY_PRECISION_32 :DRAIN_LATENCY_PRECISION_64 ; +DRAIN_LATENCY_PRECISION_16 :DRAIN_LATENCY_PRECISION_64 ; plane_dl = I915_READ(VLV_DDL(pipe)) & ~(DDL_PLANE_PRECISION_HIGH | DRAIN_LATENCY_MASK | DDL_CURSOR_PRECISION_HIGH |
Signature · 6 lines
2.0.5 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 01/12] drm/i915: Reduce CHV DDL multiplier to 16/8
Quoted 44 lines · On 02/10/2015 05:28 AM, [email protected] wrote:
From: Ville Syrjälä <[email protected]>
Apparently we must yet halve the DDL drain latency from what we're using currently. This little nugget is not in any spec, but came down through the grapevine.
This makes the displays a bit more stable. Not quite fully stable but at least they don't fall over immediately on driver load.
Signed-off-by Ville Syrjälä <[email protected]>--- drivers/gpu/drm/i915/i915_reg.h | 1 + drivers/gpu/drm/i915/intel_pm.c | 6 +++--- 2 files changed, 4 insertions(+), 3 deletions(-)drivers/gpu/drm/i915/i915_reg.h +1
-0@@ -4166,6 +4166,7 @@ enum skl_disp_power_wells {#define DSPFW_PLANEA_WM1_HI_MASK (1<<0)/* drain latency register values*/ +#define DRAIN_LATENCY_PRECISION_8 8#define DRAIN_LATENCY_PRECISION_16 16#define DRAIN_LATENCY_PRECISION_32 32#define DRAIN_LATENCY_PRECISION_64 64drivers/gpu/drm/i915/intel_pm.c +2
-2@@ -728,8 +728,8 @@ static bool vlv_compute_drain_latency(struct drm_crtc *crtc, entries =DIV_ROUND_UP (clock,1000 ) * pixel_size;if (IS_CHERRYVIEW (dev)) - *prec_mult = (entries >128 ) ?DRAIN_LATENCY_PRECISION_32 : -DRAIN_LATENCY_PRECISION_16 ; + *prec_mult = (entries >32 ) ?DRAIN_LATENCY_PRECISION_16 : +DRAIN_LATENCY_PRECISION_8 ;else *prec_mult = (entries >128 ) ?DRAIN_LATENCY_PRECISION_64 :DRAIN_LATENCY_PRECISION_32 ;
drivers/gpu/drm/i915/intel_pm.c static void vlv_update_drain_latency(struct drm_crtc *crtc) · line 765
Quoted 8 lines
drivers/gpu/drm/i915/intel_pm.c +1
-1@@ -759,7 +759,7 @@ static void vlv_update_drain_latency(struct drm_crtc *crtc)enum pipe pipe = intel_crtc->pipe;int plane_prec, prec_mult, plane_dl;const int high_precision =IS_CHERRYVIEW (dev) ? -DRAIN_LATENCY_PRECISION_32 :DRAIN_LATENCY_PRECISION_64 ; +DRAIN_LATENCY_PRECISION_16 :DRAIN_LATENCY_PRECISION_64 ; plane_dl = I915_READ(VLV_DDL(pipe)) & ~(DDL_PLANE_PRECISION_HIGH | DRAIN_LATENCY_MASK | DDL_CURSOR_PRECISION_HIGH |
You're also changing the entries threshold; is that due to the reduced drain latency precsion also?
Would be good to file a bspec bug on this so we don't lose it.
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 01/12] drm/i915: Reduce CHV DDL multiplier to 16/8
Quoted 50 lines · Jesse Barnes
Quoted 49 lines · On 02/10/2015 05:28 AM, [email protected] wrote:
From: Ville Syrjälä <[email protected]>
Apparently we must yet halve the DDL drain latency from what we're using currently. This little nugget is not in any spec, but came down through the grapevine.
This makes the displays a bit more stable. Not quite fully stable but at least they don't fall over immediately on driver load.
Signed-off-by Ville Syrjälä <[email protected]>--- drivers/gpu/drm/i915/i915_reg.h | 1 + drivers/gpu/drm/i915/intel_pm.c | 6 +++--- 2 files changed, 4 insertions(+), 3 deletions(-)drivers/gpu/drm/i915/i915_reg.h +1
-0@@ -4166,6 +4166,7 @@ enum skl_disp_power_wells {#define DSPFW_PLANEA_WM1_HI_MASK (1<<0)/* drain latency register values*/ +#define DRAIN_LATENCY_PRECISION_8 8#define DRAIN_LATENCY_PRECISION_16 16#define DRAIN_LATENCY_PRECISION_32 32#define DRAIN_LATENCY_PRECISION_64 64drivers/gpu/drm/i915/intel_pm.c +3
-3@@ -728,8 +728,8 @@ static bool vlv_compute_drain_latency(struct drm_crtc *crtc, entries =DIV_ROUND_UP (clock,1000 ) * pixel_size;if (IS_CHERRYVIEW (dev)) - *prec_mult = (entries >128 ) ?DRAIN_LATENCY_PRECISION_32 : -DRAIN_LATENCY_PRECISION_16 ; + *prec_mult = (entries >32 ) ?DRAIN_LATENCY_PRECISION_16 : +DRAIN_LATENCY_PRECISION_8 ;else *prec_mult = (entries >128 ) ?DRAIN_LATENCY_PRECISION_64 :DRAIN_LATENCY_PRECISION_32 ;@@ -759,7 +759,7 @@ static void vlv_update_drain_latency(struct drm_crtc *crtc)enum pipe pipe = intel_crtc->pipe;int plane_prec, prec_mult, plane_dl;const int high_precision =IS_CHERRYVIEW (dev) ? -DRAIN_LATENCY_PRECISION_32 :DRAIN_LATENCY_PRECISION_64 ; +DRAIN_LATENCY_PRECISION_16 :DRAIN_LATENCY_PRECISION_64 ;
Quoted 8 lines
drivers/gpu/drm/i915/intel_pm.c static void vlv_update_drain_latency(struct drm_crtc *crtc) · line 765
Quoted 3 lines
drivers/gpu/drm/i915/intel_pm.c +0
-0plane_dl = I915_READ(VLV_DDL(pipe)) & ~(DDL_PLANE_PRECISION_HIGH | DRAIN_LATENCY_MASK | DDL_CURSOR_PRECISION_HIGH |You're also changing the entries threshold; is that due to the reduced drain latency precsion also?
Would be good to file a bspec bug on this so we don't lose it.
The spec just says we should choose the precision so that we don't exceed 7bits in the final value. So the 128 was just needleslly large and we were just throwing away a useful bit by choosing to use the smaller precision factor when we didn't have to. But I'm killing off these constants anyway in a later patch to make the code less confusing.
Quoted 2 lines
Reviewed-by Jesse Barnes <[email protected]>
Signature · 6 lines
Ville Syrjälä Intel OTC _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
A message that is not in the archive (sent off-list or not yet received): [email protected]
Re: [PATCH 01/12] drm/i915: Reduce CHV DDL multiplier to 16/8
Quoted 45 lines
From: Ville Syrjälä<[email protected]>
Apparently we must yet halve the DDL drain latency from what we're using currently. This little nugget is not in any spec, but came down through the grapevine.
This makes the displays a bit more stable. Not quite fully stable but at least they don't fall over immediately on driver load.
Signed-off-by Ville Syrjälä<[email protected]>--- drivers/gpu/drm/i915/i915_reg.h | 1 + drivers/gpu/drm/i915/intel_pm.c | 6 +++--- 2 files changed, 4 insertions(+), 3 deletions(-)drivers/gpu/drm/i915/i915_reg.h +1
-0@@ -4166,6 +4166,7 @@ enum skl_disp_power_wells {#define DSPFW_PLANEA_WM1_HI_MASK (1<<0)/* drain latency register values*/ +#define DRAIN_LATENCY_PRECISION_8 8#define DRAIN_LATENCY_PRECISION_16 16#define DRAIN_LATENCY_PRECISION_32 32#define DRAIN_LATENCY_PRECISION_64 64drivers/gpu/drm/i915/intel_pm.c +2
-2@@ -728,8 +728,8 @@ static bool vlv_compute_drain_latency(struct drm_crtc *crtc, entries =DIV_ROUND_UP (clock,1000 ) * pixel_size;if (IS_CHERRYVIEW (dev)) - *prec_mult = (entries >128 ) ?DRAIN_LATENCY_PRECISION_32 : -DRAIN_LATENCY_PRECISION_16 ; + *prec_mult = (entries >32 ) ?DRAIN_LATENCY_PRECISION_16 : +DRAIN_LATENCY_PRECISION_8 ;else *prec_mult = (entries >128 ) ?DRAIN_LATENCY_PRECISION_64 :DRAIN_LATENCY_PRECISION_32 ;
drivers/gpu/drm/i915/intel_pm.c static void vlv_update_drain_latency(struct drm_crtc *crtc) · line 762
Quoted 4 lines
drivers/gpu/drm/i915/intel_pm.c +0
-1@@ -759,7 +759,7 @@ static void vlv_update_drain_latency(struct drm_crtc *crtc)enum pipe pipe = intel_crtc->pipe;int plane_prec, prec_mult, plane_dl; const int high_precision = IS_CHERRYVIEW(dev) ? -DRAIN_LATENCY_PRECISION_32 :DRAIN_LATENCY_PRECISION_64 ;
The spec says that the drain latency precision are 32 and 16. But just to be safe and have a stable environment, we further divide the calculated DDL by 2 but precision remains the same 32 and 16.
Thanks and Regards,
Arun R Murthy
-------------------
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 2/12 drm/i915: Kill DRAIN_LATENCY_PRECISION_* defines
In reply to [email protected]From: Ville Syrjälä <[email protected]>
Kill the silly DRAIN_LATENCY_PRECISION_* defines and just use the raw number instead.
--- drivers/gpu/drm/i915/i915_reg.h | 4 ---- drivers/gpu/drm/i915/intel_pm.c | 12 ++++-------- 2 files changed, 4 insertions(+), 12 deletions(-)
drivers/gpu/drm/i915/i915_reg.h +0 -4
@@ -4166,10 +4166,6 @@ enum skl_disp_power_wells {#define DSPFW_PLANEA_WM1_HI_MASK (1<<0)/* drain latency register values*/ -#define DRAIN_LATENCY_PRECISION_8 8 -#define DRAIN_LATENCY_PRECISION_16 16 -#define DRAIN_LATENCY_PRECISION_32 32 -#define DRAIN_LATENCY_PRECISION_64 64#define VLV_DDL (pipe) (VLV_DISPLAY_BASE + 0x70050 + 4 * (pipe))#define DDL_CURSOR_PRECISION_HIGH (1<<31)#define DDL_CURSOR_PRECISION_LOW (0<<31)
drivers/gpu/drm/i915/intel_pm.c +4 -8
@@ -728,11 +728,9 @@ static bool vlv_compute_drain_latency(struct drm_crtc *crtc, entries =DIV_ROUND_UP (clock,1000 ) * pixel_size;if (IS_CHERRYVIEW (dev)) - *prec_mult = (entries >32 ) ?DRAIN_LATENCY_PRECISION_16 : -DRAIN_LATENCY_PRECISION_8 ; + *prec_mult = (entries >32 ) ?16 :8 ;else - *prec_mult = (entries >128 ) ?DRAIN_LATENCY_PRECISION_64 : -DRAIN_LATENCY_PRECISION_32 ; + *prec_mult = (entries >128 ) ?64 :32 ; *drain_latency = (64 * (*prec_mult) *4 ) / entries;if (*drain_latency >DRAIN_LATENCY_MASK )
@@ -758,8 +756,7 @@ static void vlv_update_drain_latency(struct drm_crtc *crtc)int drain_latency;enum pipe pipe = intel_crtc->pipe;int plane_prec, prec_mult, plane_dl; -const int high_precision =IS_CHERRYVIEW (dev) ? -DRAIN_LATENCY_PRECISION_16 :DRAIN_LATENCY_PRECISION_64 ; +const int high_precision =IS_CHERRYVIEW (dev) ?16 :64 ; plane_dl = I915_READ(VLV_DDL(pipe)) & ~(DDL_PLANE_PRECISION_HIGH | DRAIN_LATENCY_MASK | DDL_CURSOR_PRECISION_HIGH |
@@ -957,8 +954,7 @@ static void valleyview_update_sprite_wm(struct drm_plane *plane,int plane_prec;int sprite_dl;int prec_mult; -const int high_precision =IS_CHERRYVIEW (dev) ? -DRAIN_LATENCY_PRECISION_32 :DRAIN_LATENCY_PRECISION_64 ; +const int high_precision =IS_CHERRYVIEW (dev) ?16 :64 ; sprite_dl =I915_READ (VLV_DDL (pipe)) & ~(DDL_SPRITE_PRECISION_HIGH (sprite) | (DRAIN_LATENCY_MASK <<DDL_SPRITE_SHIFT (sprite)));
Signature · 6 lines
2.0.5 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 02/12] drm/i915: Kill DRAIN_LATENCY_PRECISION_* defines
Review static void valleyview_update_sprite_wm(struct
Quoted 1 line · On 02/10/2015 05:28 AM, [email protected] wrote:
(quoted diff) +0
-0@@ -957,8 +954,7 @@ static void valleyview_update_sprite_wm(struct
drm_plane *plane,
drivers/gpu/drm/i915/intel_pm.c static void valleyview_update_sprite_wm(struct drm_plane *plane, · line 960
Quoted 10 lines
drivers/gpu/drm/i915/intel_pm.c +1
-2int plane_prec;int sprite_dl;int prec_mult; -const int high_precision =IS_CHERRYVIEW (dev) ? -DRAIN_LATENCY_PRECISION_32 :DRAIN_LATENCY_PRECISION_64 ; +const int high_precision =IS_CHERRYVIEW (dev) ?16 :64 ; sprite_dl =I915_READ (VLV_DDL (pipe)) & ~(DDL_SPRITE_PRECISION_HIGH (sprite) | (DRAIN_LATENCY_MASK <<DDL_SPRITE_SHIFT (sprite)));
This hunk changes things; did it belong in the earlier patch?
With that explained:
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 02/12] drm/i915: Kill DRAIN_LATENCY_PRECISION_* defines
Quoted 10 lines · Jesse Barnes
Review static void valleyview_update_sprite_wm(struct
Quoted 1 line · On 02/10/2015 05:28 AM, [email protected] wrote:
(quoted diff) +0
-0@@ -957,8 +954,7 @@ static void valleyview_update_sprite_wm(struct
drm_plane*plane,Quoted 7 lines
drivers/gpu/drm/i915/intel_pm.c +1
-2int plane_prec;int sprite_dl;int prec_mult; -const int high_precision =IS_CHERRYVIEW (dev) ? -DRAIN_LATENCY_PRECISION_32 :DRAIN_LATENCY_PRECISION_64 ; +const int high_precision =IS_CHERRYVIEW (dev) ?16 :64 ;
Quoted 5 lines
drivers/gpu/drm/i915/intel_pm.c static void valleyview_update_sprite_wm(struct drm_plane *plane, · line 960
Quoted 3 lines
drivers/gpu/drm/i915/intel_pm.c +0
-0sprite_dl =I915_READ (VLV_DDL (pipe)) & ~(DDL_SPRITE_PRECISION_HIGH (sprite) | (DRAIN_LATENCY_MASK <<DDL_SPRITE_SHIFT (sprite)));This hunk changes things; did it belong in the earlier patch?
Yeah that should have been part of patch 1 already. I'll respin.
Quoted 3 lines
With that explained:
Reviewed-by Jesse Barnes <[email protected]>
Signature · 6 lines
Ville Syrjälä Intel OTC _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 3/12 drm/i915: Simplify VLV drain latency computation
In reply to [email protected]From: Ville Syrjälä <[email protected]>
The current drain lantency computation relies on hardcoded limits to determine when the to use the low vs. high precision multiplier. Rewrite the code to use a more straightforward approach.
--- drivers/gpu/drm/i915/intel_pm.c | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-)
drivers/gpu/drm/i915/intel_pm.c +7 -4
@@ -727,12 +727,15 @@ static bool vlv_compute_drain_latency(struct drm_crtc *crtc,return false; entries =DIV_ROUND_UP (clock,1000 ) * pixel_size; -if (IS_CHERRYVIEW (dev)) - *prec_mult = (entries >32 ) ?16 :8 ; -else - *prec_mult = (entries >128 ) ?64 :32 ; + + *prec_mult =IS_CHERRYVIEW (dev) ?16 :64 ; *drain_latency = (64 * (*prec_mult) *4 ) / entries; +if (*drain_latency >DRAIN_LATENCY_MASK ) { + *prec_mult /=2 ; + *drain_latency = (64 * (*prec_mult) *4 ) / entries; + } +if (*drain_latency >DRAIN_LATENCY_MASK ) *drain_latency =DRAIN_LATENCY_MASK ;
Signature · 6 lines
2.0.5 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 03/12] drm/i915: Simplify VLV drain latency computation
Quoted 26 lines · On 02/10/2015 05:28 AM, [email protected] wrote:
From: Ville Syrjälä <[email protected]>
The current drain lantency computation relies on hardcoded limits to determine when the to use the low vs. high precision multiplier. Rewrite the code to use a more straightforward approach.
Signed-off-by Ville Syrjälä <[email protected]>--- drivers/gpu/drm/i915/intel_pm.c | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-)drivers/gpu/drm/i915/intel_pm.c +2
-4@@ -727,12 +727,15 @@ static bool vlv_compute_drain_latency(struct drm_crtc *crtc,return false; entries =DIV_ROUND_UP (clock,1000 ) * pixel_size; -if (IS_CHERRYVIEW (dev)) - *prec_mult = (entries >32 ) ?16 :8 ; -else - *prec_mult = (entries >128 ) ?64 :32 ; + + *prec_mult =IS_CHERRYVIEW (dev) ?16 :64 ;
drivers/gpu/drm/i915/intel_pm.c static bool vlv_compute_drain_latency(struct drm_crtc *crtc, · line 741
Quoted 10 lines
drivers/gpu/drm/i915/intel_pm.c +5
-0*drain_latency = (64 * (*prec_mult) *4 ) / entries; +if (*drain_latency >DRAIN_LATENCY_MASK ) { + *prec_mult /=2 ; + *drain_latency = (64 * (*prec_mult) *4 ) / entries; + } +if (*drain_latency >DRAIN_LATENCY_MASK ) *drain_latency =DRAIN_LATENCY_MASK ;
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 4/12 drm/i915: Hide VLV DDL precision handling
In reply to [email protected]From: Ville Syrjälä <[email protected]>
Move the DDL precision handling into vlv_compute_drain_latency() so the callers don't have to duplicate the same code to deal with it.
--- drivers/gpu/drm/i915/i915_reg.h | 8 ++--- drivers/gpu/drm/i915/intel_pm.c | 74 +++++++++++++++-------------------------- 2 files changed, 28 insertions(+), 54 deletions(-)
drivers/gpu/drm/i915/i915_reg.h +2 -6
@@ -4167,15 +4167,11 @@ enum skl_disp_power_wells {/* drain latency register values*/ #define VLV_DDL (pipe) (VLV_DISPLAY_BASE + 0x70050 + 4 * (pipe)) -#define DDL_CURSOR_PRECISION_HIGH (1<<31) -#define DDL_CURSOR_PRECISION_LOW (0<<31)#define DDL_CURSOR_SHIFT 24 -#define DDL_SPRITE_PRECISION_HIGH (sprite) (1<<(15+8*(sprite))) -#define DDL_SPRITE_PRECISION_LOW (sprite) (0<<(15+8*(sprite)))#define DDL_SPRITE_SHIFT (sprite) (8+8*(sprite)) -#define DDL_PLANE_PRECISION_HIGH (1<<7) -#define DDL_PLANE_PRECISION_LOW (0<<7)#define DDL_PLANE_SHIFT 0 +#define DDL_PRECISION_HIGH (1<<7) +#define DDL_PRECISION_LOW (0<<7)#define DRAIN_LATENCY_MASK 0x7f/* FIFO watermark sizes etc */
drivers/gpu/drm/i915/intel_pm.c +26 -48
123 lines not on this page · raw message
Signature · 6 lines
2.0.5 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 04/12] drm/i915: Hide VLV DDL precision handling
Quoted 4 lines · On 02/10/2015 05:28 AM, [email protected] wrote:
From: Ville Syrjälä <[email protected]>
Move the DDL precision handling into
vlv_compute_drain_latency()so the callers don't have to duplicate the same code to deal with it.
A little painful due to the addition of the #define changes, but I think it's right, and will actually be easier to fix if wrong anyway due to the removal of duplication.
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 5/12 drm/i915: Reorganize VLV DDL setup
In reply to [email protected]From: Ville Syrjälä <[email protected]>
Introduce struct vlv_wm_values to house VLV watermark/drain latency values. We start by using it when computing the drain latency values.
--- drivers/gpu/drm/i915/i915_drv.h | 9 ++++++++ drivers/gpu/drm/i915/intel_pm.c | 46 +++++++++++++++++++++++++++-------------- 2 files changed, 40 insertions(+), 15 deletions(-)
drivers/gpu/drm/i915/i915_drv.h +9 -0
@@ -1514,6 +1514,14 @@ struct ilk_wm_values {enum intel_ddb_partitioning partitioning; }; +struct vlv_wm_values { +struct { +uint8_t cursor; +uint8_t sprite[2 ]; +uint8_t primary; + } ddl[3 ]; +}; +struct skl_ddb_entry {uint16_t start, end;/* in number of blocks, 'end' is exclusive */ };
@@ -1870,6 +1878,7 @@ struct drm_i915_private {union {struct ilk_wm_values hw;struct skl_wm_values skl_hw; +struct vlv_wm_values vlv; }; } wm;
drivers/gpu/drm/i915/intel_pm.c +31 -15
83 lines not on this page · raw message
Signature · 6 lines
2.0.5 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 05/12] drm/i915: Reorganize VLV DDL setup
Quoted 120 lines · On 02/10/2015 05:28 AM, [email protected] wrote:
From: Ville Syrjälä <[email protected]>
Introduce struct
vlv_wm_valuesto house VLV watermark/drain latency values. We start by using it when computing the drain latency values.Signed-off-by Ville Syrjälä <[email protected]>--- drivers/gpu/drm/i915/i915_drv.h | 9 ++++++++ drivers/gpu/drm/i915/intel_pm.c | 46 +++++++++++++++++++++++++++-------------- 2 files changed, 40 insertions(+), 15 deletions(-)drivers/gpu/drm/i915/i915_drv.h +9
-0@@ -1514,6 +1514,14 @@ struct ilk_wm_values {enum intel_ddb_partitioning partitioning; }; +struct vlv_wm_values { +struct { +uint8_t cursor; +uint8_t sprite[2 ]; +uint8_t primary; + } ddl[3 ]; +}; +struct skl_ddb_entry {uint16_t start, end;/* in number of blocks, 'end' is exclusive */ };@@ -1870,6 +1878,7 @@ struct drm_i915_private {union {struct ilk_wm_values hw;struct skl_wm_values skl_hw; +struct vlv_wm_values vlv; }; } wm;drivers/gpu/drm/i915/intel_pm.c +26
-14@@ -711,6 +711,21 @@ static bool g4x_compute_srwm(struct drm_device *dev, display, cursor); } +static void vlv_write_wm_values (struct intel_crtc *crtc, +const struct vlv_wm_values *wm) +{ +struct drm_i915_private *dev_priv =to_i915 (crtc->base.dev); +enum pipe pipe = crtc->pipe; + +I915_WRITE (VLV_DDL (pipe), + (wm->ddl[pipe].cursor <<DDL_CURSOR_SHIFT ) | + (wm->ddl[pipe].sprite[1 ] <<DDL_SPRITE_SHIFT (1 )) | + (wm->ddl[pipe].sprite[0 ] <<DDL_SPRITE_SHIFT (0 )) | + (wm->ddl[pipe].primary <<DDL_PLANE_SHIFT )); + + dev_priv->wm.vlv = *wm; +} +static uint8_t vlv_compute_drain_latency (struct drm_crtc *crtc,int pixel_size) {@@ -757,20 +772,19 @@ static void vlv_update_drain_latency(struct drm_crtc *crtc)struct intel_crtc *intel_crtc =to_intel_crtc (crtc);int pixel_size;enum pipe pipe = intel_crtc->pipe; -int plane_dl; +struct vlv_wm_values wm = dev_priv->wm.vlv; - plane_dl =I915_READ (VLV_DDL (pipe)) & - ~(((DDL_PRECISION_HIGH |DRAIN_LATENCY_MASK ) <<DDL_CURSOR_SHIFT ) | - ((DDL_PRECISION_HIGH |DRAIN_LATENCY_MASK ) <<DDL_PLANE_SHIFT )); + wm.ddl[pipe].primary =0 ; + wm.ddl[pipe].cursor =0 ;if (!intel_crtc_active (crtc)) { -I915_WRITE (VLV_DDL (pipe), plane_dl); +vlv_write_wm_values (intel_crtc, &wm);return ; }/* Primary plane Drain Latency */ pixel_size = crtc->primary->fb->bits_per_pixel /8 ;/* BPP */ - plane_dl =vlv_compute_drain_latency (crtc, pixel_size) <<DDL_PLANE_SHIFT ; + wm.ddl[pipe].primary =vlv_compute_drain_latency (crtc, pixel_size);/* Cursor Drain Latency * BPP is always 4 for cursor @@ -779,9 +793,10 @@ static void vlv_update_drain_latency(struct drm_crtc *crtc)/* Program cursor DL only if it is enabled */ if (intel_crtc->cursor_base) - plane_dl |=vlv_compute_drain_latency (crtc, pixel_size) <<DDL_CURSOR_SHIFT ; + wm.ddl[pipe].cursor = +vlv_compute_drain_latency (crtc, pixel_size); -I915_WRITE (VLV_DDL (pipe), plane_dl); +vlv_write_wm_values (intel_crtc, &wm); }#define single_plane_enabled (mask) is_power_of_2(mask)@@ -939,17 +954,18 @@ static void valleyview_update_sprite_wm(struct drm_plane *plane, {struct drm_device *dev = crtc->dev;struct drm_i915_private *dev_priv = dev->dev_private; -int pipe =to_intel_plane (plane)->pipe; +struct intel_crtc *intel_crtc =to_intel_crtc (crtc); +enum pipe pipe = intel_crtc->pipe;int sprite =to_intel_plane (plane)->plane; -int sprite_dl; - - sprite_dl =I915_READ (VLV_DDL (pipe)) & - ~((DDL_PRECISION_HIGH |DRAIN_LATENCY_MASK ) <<DDL_SPRITE_SHIFT (sprite)); +struct vlv_wm_values wm = dev_priv->wm.vlv;if (enabled) - sprite_dl |=vlv_compute_drain_latency (crtc, pixel_size) <<DDL_SPRITE_SHIFT (sprite);
drivers/gpu/drm/i915/intel_pm.c static void valleyview_update_sprite_wm(struct drm_plane *plane, · line 971
Quoted 10 lines
drivers/gpu/drm/i915/intel_pm.c +5
-1+ wm.ddl[pipe].sprite[sprite] = +vlv_compute_drain_latency (crtc, pixel_size); + else + wm.ddl[pipe].sprite[sprite] = 0; -I915_WRITE (VLV_DDL (pipe), sprite_dl); +vlv_write_wm_values (intel_crtc, &wm); }static void g4x_update_wm (struct drm_crtc *crtc)
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 6/12 drm/i915: Pass plane to vlv_compute_drain_latency()
In reply to [email protected]From: Ville Syrjälä <[email protected]>
Now that we have drm_planes for the cursor and primary we can move the pixel_size handling into vlv_compute_drain_latency() and just pass the appropriate plane to it.
--- drivers/gpu/drm/i915/intel_pm.c | 42 ++++++++++++++++------------------------- 1 file changed, 16 insertions(+), 26 deletions(-)
drivers/gpu/drm/i915/intel_pm.c +16 -26
@@ -727,16 +727,26 @@ static void vlv_write_wm_values(struct intel_crtc *crtc, }static uint8_t vlv_compute_drain_latency (struct drm_crtc *crtc, -int pixel_size) +struct drm_plane *plane) {struct drm_device *dev = crtc->dev; -int entries, prec_mult, drain_latency; -int clock =to_intel_crtc (crtc)->config->base.adjusted_mode.crtc_clock; +struct intel_crtc *intel_crtc =to_intel_crtc (crtc); +int entries, prec_mult, drain_latency, pixel_size; +int clock = intel_crtc->config->base.adjusted_mode.crtc_clock;const int high_precision =IS_CHERRYVIEW (dev) ?16 :64 ; +/* +* FIXME the plane might have an fb +* but be invisible (eg. due to clipping) +*/ +if (!intel_crtc->active || !plane->fb) +return 0 ; +if (WARN (clock ==0 ,"Pixel clock is zero!\n" ))return 0 ; + pixel_size =drm_format_plane_cpp (plane->fb->pixel_format,0 ); +if (WARN (pixel_size ==0 ,"Pixel size is zero!\n" ))return 0 ;
@@ -770,31 +780,11 @@ static void vlv_update_drain_latency(struct drm_crtc *crtc)struct drm_device *dev = crtc->dev;struct drm_i915_private *dev_priv = dev->dev_private;struct intel_crtc *intel_crtc =to_intel_crtc (crtc); -int pixel_size;enum pipe pipe = intel_crtc->pipe;struct vlv_wm_values wm = dev_priv->wm.vlv; - wm.ddl[pipe].primary =0 ; - wm.ddl[pipe].cursor =0 ; - -if (!intel_crtc_active (crtc)) { -vlv_write_wm_values (intel_crtc, &wm); -return ; - } - -/* Primary plane Drain Latency */ - pixel_size = crtc->primary->fb->bits_per_pixel /8 ;/* BPP */ - wm.ddl[pipe].primary =vlv_compute_drain_latency (crtc, pixel_size); - -/* Cursor Drain Latency -* BPP is always 4 for cursor -*/ - pixel_size =4 ; - -/* Program cursor DL only if it is enabled */ -if (intel_crtc->cursor_base) - wm.ddl[pipe].cursor = -vlv_compute_drain_latency (crtc, pixel_size); + wm.ddl[pipe].primary =vlv_compute_drain_latency (crtc, crtc->primary); + wm.ddl[pipe].cursor =vlv_compute_drain_latency (crtc, crtc->cursor);vlv_write_wm_values (intel_crtc, &wm); }
@@ -961,7 +951,7 @@ static void valleyview_update_sprite_wm(struct drm_plane *plane,if (enabled) wm.ddl[pipe].sprite[sprite] = -vlv_compute_drain_latency (crtc, pixel_size); +vlv_compute_drain_latency (crtc, plane);else wm.ddl[pipe].sprite[sprite] =0 ;
Signature · 6 lines
2.0.5 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 06/12] drm/i915: Pass plane to vlv_compute_drain_latency()
Quoted 81 lines · On 02/10/2015 05:28 AM, [email protected] wrote:
From: Ville Syrjälä <[email protected]>
Now that we have
drm_planesfor the cursor and primary we can move thepixel_sizehandling intovlv_compute_drain_latency()and just pass the appropriate plane to it.Signed-off-by Ville Syrjälä <[email protected]>--- drivers/gpu/drm/i915/intel_pm.c | 42 ++++++++++++++++------------------------- 1 file changed, 16 insertions(+), 26 deletions(-)drivers/gpu/drm/i915/intel_pm.c +15
-25@@ -727,16 +727,26 @@ static void vlv_write_wm_values(struct intel_crtc *crtc, }static uint8_t vlv_compute_drain_latency (struct drm_crtc *crtc, -int pixel_size) +struct drm_plane *plane) {struct drm_device *dev = crtc->dev; -int entries, prec_mult, drain_latency; -int clock =to_intel_crtc (crtc)->config->base.adjusted_mode.crtc_clock; +struct intel_crtc *intel_crtc =to_intel_crtc (crtc); +int entries, prec_mult, drain_latency, pixel_size; +int clock = intel_crtc->config->base.adjusted_mode.crtc_clock;const int high_precision =IS_CHERRYVIEW (dev) ?16 :64 ; +/* +* FIXME the plane might have an fb +* but be invisible (eg. due to clipping) +*/ +if (!intel_crtc->active || !plane->fb) +return 0 ; +if (WARN (clock ==0 ,"Pixel clock is zero!\n" ))return 0 ; + pixel_size =drm_format_plane_cpp (plane->fb->pixel_format,0 ); +if (WARN (pixel_size ==0 ,"Pixel size is zero!\n" ))return 0 ;@@ -770,31 +780,11 @@ static void vlv_update_drain_latency(struct drm_crtc *crtc)struct drm_device *dev = crtc->dev;struct drm_i915_private *dev_priv = dev->dev_private;struct intel_crtc *intel_crtc =to_intel_crtc (crtc); -int pixel_size;enum pipe pipe = intel_crtc->pipe;struct vlv_wm_values wm = dev_priv->wm.vlv; - wm.ddl[pipe].primary =0 ; - wm.ddl[pipe].cursor =0 ; - -if (!intel_crtc_active (crtc)) { -vlv_write_wm_values (intel_crtc, &wm); -return ; - } - -/* Primary plane Drain Latency */ - pixel_size = crtc->primary->fb->bits_per_pixel /8 ;/* BPP */ - wm.ddl[pipe].primary =vlv_compute_drain_latency (crtc, pixel_size); - -/* Cursor Drain Latency -* BPP is always 4 for cursor -*/ - pixel_size =4 ; - -/* Program cursor DL only if it is enabled */ -if (intel_crtc->cursor_base) - wm.ddl[pipe].cursor = -vlv_compute_drain_latency (crtc, pixel_size); + wm.ddl[pipe].primary =vlv_compute_drain_latency (crtc, crtc->primary); + wm.ddl[pipe].cursor =vlv_compute_drain_latency (crtc, crtc->cursor);vlv_write_wm_values (intel_crtc, &wm); }
drivers/gpu/drm/i915/intel_pm.c static void valleyview_update_sprite_wm(struct drm_plane *plane, · line 957
Quoted 8 lines
drivers/gpu/drm/i915/intel_pm.c +1
-1@@ -961,7 +951,7 @@ static void valleyview_update_sprite_wm(struct drm_plane *plane,if (enabled) wm.ddl[pipe].sprite[sprite] = -vlv_compute_drain_latency (crtc, pixel_size); +vlv_compute_drain_latency (crtc, plane);else wm.ddl[pipe].sprite[sprite] =0 ;
Nice.
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 06/12] drm/i915: Pass plane to vlv_compute_drain_latency()
Quoted 82 lines · Jesse Barnes
Quoted 81 lines · On 02/10/2015 05:28 AM, [email protected] wrote:
From: Ville Syrjälä <[email protected]>
Now that we have
drm_planesfor the cursor and primary we can move thepixel_sizehandling intovlv_compute_drain_latency()and just pass the appropriate plane to it.Signed-off-by Ville Syrjälä <[email protected]>--- drivers/gpu/drm/i915/intel_pm.c | 42 ++++++++++++++++------------------------- 1 file changed, 16 insertions(+), 26 deletions(-)drivers/gpu/drm/i915/intel_pm.c +15
-25@@ -727,16 +727,26 @@ static void vlv_write_wm_values(struct intel_crtc *crtc, }static uint8_t vlv_compute_drain_latency (struct drm_crtc *crtc, -int pixel_size) +struct drm_plane *plane) {struct drm_device *dev = crtc->dev; -int entries, prec_mult, drain_latency; -int clock =to_intel_crtc (crtc)->config->base.adjusted_mode.crtc_clock; +struct intel_crtc *intel_crtc =to_intel_crtc (crtc); +int entries, prec_mult, drain_latency, pixel_size; +int clock = intel_crtc->config->base.adjusted_mode.crtc_clock;const int high_precision =IS_CHERRYVIEW (dev) ?16 :64 ; +/* +* FIXME the plane might have an fb +* but be invisible (eg. due to clipping) +*/ +if (!intel_crtc->active || !plane->fb) +return 0 ; +if (WARN (clock ==0 ,"Pixel clock is zero!\n" ))return 0 ; + pixel_size =drm_format_plane_cpp (plane->fb->pixel_format,0 ); +if (WARN (pixel_size ==0 ,"Pixel size is zero!\n" ))return 0 ;@@ -770,31 +780,11 @@ static void vlv_update_drain_latency(struct drm_crtc *crtc)struct drm_device *dev = crtc->dev;struct drm_i915_private *dev_priv = dev->dev_private;struct intel_crtc *intel_crtc =to_intel_crtc (crtc); -int pixel_size;enum pipe pipe = intel_crtc->pipe;struct vlv_wm_values wm = dev_priv->wm.vlv; - wm.ddl[pipe].primary =0 ; - wm.ddl[pipe].cursor =0 ; - -if (!intel_crtc_active (crtc)) { -vlv_write_wm_values (intel_crtc, &wm); -return ; - } - -/* Primary plane Drain Latency */ - pixel_size = crtc->primary->fb->bits_per_pixel /8 ;/* BPP */ - wm.ddl[pipe].primary =vlv_compute_drain_latency (crtc, pixel_size); - -/* Cursor Drain Latency -* BPP is always 4 for cursor -*/ - pixel_size =4 ; - -/* Program cursor DL only if it is enabled */ -if (intel_crtc->cursor_base) - wm.ddl[pipe].cursor = -vlv_compute_drain_latency (crtc, pixel_size); + wm.ddl[pipe].primary =vlv_compute_drain_latency (crtc, crtc->primary); + wm.ddl[pipe].cursor =vlv_compute_drain_latency (crtc, crtc->cursor);vlv_write_wm_values (intel_crtc, &wm); }@@ -961,7 +951,7 @@ static void valleyview_update_sprite_wm(struct drm_plane *plane,
Quoted 10 lines
drivers/gpu/drm/i915/intel_pm.c static void valleyview_update_sprite_wm(struct drm_plane *plane, · line 957
Quoted 8 lines
drivers/gpu/drm/i915/intel_pm.c +1
-1if (enabled) wm.ddl[pipe].sprite[sprite] = -vlv_compute_drain_latency (crtc, pixel_size); +vlv_compute_drain_latency (crtc, plane);else wm.ddl[pipe].sprite[sprite] =0 ;Nice.
Actually this is going to have issues now that atomic is partially in. We'd need to look at plane->state->fb now, but that steps on the same turf as Matt's latest patches.
Quoted 2 lines
Reviewed-by Jesse Barnes <[email protected]>
Signature · 6 lines
Ville Syrjälä Intel OTC _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 06/12] drm/i915: Pass plane to vlv_compute_drain_latency()
Quoted 94 lines · Ville Syrjälä
Quoted 82 lines · Jesse Barnes
Quoted 81 lines · On 02/10/2015 05:28 AM, [email protected] wrote:
From: Ville Syrjälä <[email protected]>
Now that we have
drm_planesfor the cursor and primary we can move thepixel_sizehandling intovlv_compute_drain_latency()and just pass the appropriate plane to it.Signed-off-by Ville Syrjälä <[email protected]>--- drivers/gpu/drm/i915/intel_pm.c | 42 ++++++++++++++++------------------------- 1 file changed, 16 insertions(+), 26 deletions(-)drivers/gpu/drm/i915/intel_pm.c +15
-25@@ -727,16 +727,26 @@ static void vlv_write_wm_values(struct intel_crtc *crtc, }static uint8_t vlv_compute_drain_latency (struct drm_crtc *crtc, -int pixel_size) +struct drm_plane *plane) {struct drm_device *dev = crtc->dev; -int entries, prec_mult, drain_latency; -int clock =to_intel_crtc (crtc)->config->base.adjusted_mode.crtc_clock; +struct intel_crtc *intel_crtc =to_intel_crtc (crtc); +int entries, prec_mult, drain_latency, pixel_size; +int clock = intel_crtc->config->base.adjusted_mode.crtc_clock;const int high_precision =IS_CHERRYVIEW (dev) ?16 :64 ; +/* +* FIXME the plane might have an fb +* but be invisible (eg. due to clipping) +*/ +if (!intel_crtc->active || !plane->fb) +return 0 ; +if (WARN (clock ==0 ,"Pixel clock is zero!\n" ))return 0 ; + pixel_size =drm_format_plane_cpp (plane->fb->pixel_format,0 ); +if (WARN (pixel_size ==0 ,"Pixel size is zero!\n" ))return 0 ;@@ -770,31 +780,11 @@ static void vlv_update_drain_latency(struct drm_crtc *crtc)struct drm_device *dev = crtc->dev;struct drm_i915_private *dev_priv = dev->dev_private;struct intel_crtc *intel_crtc =to_intel_crtc (crtc); -int pixel_size;enum pipe pipe = intel_crtc->pipe;struct vlv_wm_values wm = dev_priv->wm.vlv; - wm.ddl[pipe].primary =0 ; - wm.ddl[pipe].cursor =0 ; - -if (!intel_crtc_active (crtc)) { -vlv_write_wm_values (intel_crtc, &wm); -return ; - } - -/* Primary plane Drain Latency */ - pixel_size = crtc->primary->fb->bits_per_pixel /8 ;/* BPP */ - wm.ddl[pipe].primary =vlv_compute_drain_latency (crtc, pixel_size); - -/* Cursor Drain Latency -* BPP is always 4 for cursor -*/ - pixel_size =4 ; - -/* Program cursor DL only if it is enabled */ -if (intel_crtc->cursor_base) - wm.ddl[pipe].cursor = -vlv_compute_drain_latency (crtc, pixel_size); + wm.ddl[pipe].primary =vlv_compute_drain_latency (crtc, crtc->primary); + wm.ddl[pipe].cursor =vlv_compute_drain_latency (crtc, crtc->cursor);vlv_write_wm_values (intel_crtc, &wm); }@@ -961,7 +951,7 @@ static void valleyview_update_sprite_wm(struct drm_plane *plane,Quoted 10 lines
drivers/gpu/drm/i915/intel_pm.c static void valleyview_update_sprite_wm(struct drm_plane *plane, · line 957
Quoted 8 lines
drivers/gpu/drm/i915/intel_pm.c +1
-1if (enabled) wm.ddl[pipe].sprite[sprite] = -vlv_compute_drain_latency (crtc, pixel_size); +vlv_compute_drain_latency (crtc, plane);else wm.ddl[pipe].sprite[sprite] =0 ;Nice.
Quoted 3 lines
Actually this is going to have issues now that atomic is partially in. We'd need to look at
plane->state->fbnow, but that steps on the same turf as Matt's latest patches.
Yeah there's some overlap, but mostly it looked like these would make things a little easier by removing duplication and clearing things up (not to mention the bug fixes).
Jesse
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 06/12] drm/i915: Pass plane to vlv_compute_drain_latency()
In reply to Ville SyrjäläQuoted 94 lines · Ville Syrjälä
Quoted 82 lines · Jesse Barnes
Quoted 81 lines · On 02/10/2015 05:28 AM, [email protected] wrote:
From: Ville Syrjälä <[email protected]>
Now that we have
drm_planesfor the cursor and primary we can move thepixel_sizehandling intovlv_compute_drain_latency()and just pass the appropriate plane to it.Signed-off-by Ville Syrjälä <[email protected]>--- drivers/gpu/drm/i915/intel_pm.c | 42 ++++++++++++++++------------------------- 1 file changed, 16 insertions(+), 26 deletions(-)drivers/gpu/drm/i915/intel_pm.c +15
-25@@ -727,16 +727,26 @@ static void vlv_write_wm_values(struct intel_crtc *crtc, }static uint8_t vlv_compute_drain_latency (struct drm_crtc *crtc, -int pixel_size) +struct drm_plane *plane) {struct drm_device *dev = crtc->dev; -int entries, prec_mult, drain_latency; -int clock =to_intel_crtc (crtc)->config->base.adjusted_mode.crtc_clock; +struct intel_crtc *intel_crtc =to_intel_crtc (crtc); +int entries, prec_mult, drain_latency, pixel_size; +int clock = intel_crtc->config->base.adjusted_mode.crtc_clock;const int high_precision =IS_CHERRYVIEW (dev) ?16 :64 ; +/* +* FIXME the plane might have an fb +* but be invisible (eg. due to clipping) +*/ +if (!intel_crtc->active || !plane->fb) +return 0 ; +if (WARN (clock ==0 ,"Pixel clock is zero!\n" ))return 0 ; + pixel_size =drm_format_plane_cpp (plane->fb->pixel_format,0 ); +if (WARN (pixel_size ==0 ,"Pixel size is zero!\n" ))return 0 ;@@ -770,31 +780,11 @@ static void vlv_update_drain_latency(struct drm_crtc *crtc)struct drm_device *dev = crtc->dev;struct drm_i915_private *dev_priv = dev->dev_private;struct intel_crtc *intel_crtc =to_intel_crtc (crtc); -int pixel_size;enum pipe pipe = intel_crtc->pipe;struct vlv_wm_values wm = dev_priv->wm.vlv; - wm.ddl[pipe].primary =0 ; - wm.ddl[pipe].cursor =0 ; - -if (!intel_crtc_active (crtc)) { -vlv_write_wm_values (intel_crtc, &wm); -return ; - } - -/* Primary plane Drain Latency */ - pixel_size = crtc->primary->fb->bits_per_pixel /8 ;/* BPP */ - wm.ddl[pipe].primary =vlv_compute_drain_latency (crtc, pixel_size); - -/* Cursor Drain Latency -* BPP is always 4 for cursor -*/ - pixel_size =4 ; - -/* Program cursor DL only if it is enabled */ -if (intel_crtc->cursor_base) - wm.ddl[pipe].cursor = -vlv_compute_drain_latency (crtc, pixel_size); + wm.ddl[pipe].primary =vlv_compute_drain_latency (crtc, crtc->primary); + wm.ddl[pipe].cursor =vlv_compute_drain_latency (crtc, crtc->cursor);vlv_write_wm_values (intel_crtc, &wm); }@@ -961,7 +951,7 @@ static void valleyview_update_sprite_wm(struct drm_plane *plane,Quoted 10 lines
drivers/gpu/drm/i915/intel_pm.c static void valleyview_update_sprite_wm(struct drm_plane *plane, · line 957
Quoted 8 lines
drivers/gpu/drm/i915/intel_pm.c +1
-1if (enabled) wm.ddl[pipe].sprite[sprite] = -vlv_compute_drain_latency (crtc, pixel_size); +vlv_compute_drain_latency (crtc, plane);else wm.ddl[pipe].sprite[sprite] =0 ;Nice.
Quoted 3 lines
Actually this is going to have issues now that atomic is partially in. We'd need to look at
plane->state->fbnow, but that steps on the same turf as Matt's latest patches.
All the wm computation needs to be moved over to look at plane states, not plane->state - we need to do all this in the check phase when state objects haven't been commited yet. Which is a lot more work and probably best done separately in one go than all over the place and inconsistently. -Daniel
Signature · 7 lines
Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 06/12] drm/i915: Pass plane to vlv_compute_drain_latency()
Quoted 95 lines · Daniel Vetter
Quoted 94 lines · Ville Syrjälä
Quoted 92 lines · Jesse Barnes
Quoted 81 lines · On 02/10/2015 05:28 AM, [email protected] wrote:
From: Ville Syrjälä <[email protected]>
Now that we have
drm_planesfor the cursor and primary we can move thepixel_sizehandling intovlv_compute_drain_latency()and just pass the appropriate plane to it.Signed-off-by Ville Syrjälä <[email protected]>--- drivers/gpu/drm/i915/intel_pm.c | 42 ++++++++++++++++------------------------- 1 file changed, 16 insertions(+), 26 deletions(-)drivers/gpu/drm/i915/intel_pm.c +15
-25@@ -727,16 +727,26 @@ static void vlv_write_wm_values(struct intel_crtc *crtc, }static uint8_t vlv_compute_drain_latency (struct drm_crtc *crtc, -int pixel_size) +struct drm_plane *plane) {struct drm_device *dev = crtc->dev; -int entries, prec_mult, drain_latency; -int clock =to_intel_crtc (crtc)->config->base.adjusted_mode.crtc_clock; +struct intel_crtc *intel_crtc =to_intel_crtc (crtc); +int entries, prec_mult, drain_latency, pixel_size; +int clock = intel_crtc->config->base.adjusted_mode.crtc_clock;const int high_precision =IS_CHERRYVIEW (dev) ?16 :64 ; +/* +* FIXME the plane might have an fb +* but be invisible (eg. due to clipping) +*/ +if (!intel_crtc->active || !plane->fb) +return 0 ; +if (WARN (clock ==0 ,"Pixel clock is zero!\n" ))return 0 ; + pixel_size =drm_format_plane_cpp (plane->fb->pixel_format,0 ); +if (WARN (pixel_size ==0 ,"Pixel size is zero!\n" ))return 0 ;@@ -770,31 +780,11 @@ static void vlv_update_drain_latency(struct drm_crtc *crtc)struct drm_device *dev = crtc->dev;struct drm_i915_private *dev_priv = dev->dev_private;struct intel_crtc *intel_crtc =to_intel_crtc (crtc); -int pixel_size;enum pipe pipe = intel_crtc->pipe;struct vlv_wm_values wm = dev_priv->wm.vlv; - wm.ddl[pipe].primary =0 ; - wm.ddl[pipe].cursor =0 ; - -if (!intel_crtc_active (crtc)) { -vlv_write_wm_values (intel_crtc, &wm); -return ; - } - -/* Primary plane Drain Latency */ - pixel_size = crtc->primary->fb->bits_per_pixel /8 ;/* BPP */ - wm.ddl[pipe].primary =vlv_compute_drain_latency (crtc, pixel_size); - -/* Cursor Drain Latency -* BPP is always 4 for cursor -*/ - pixel_size =4 ; - -/* Program cursor DL only if it is enabled */ -if (intel_crtc->cursor_base) - wm.ddl[pipe].cursor = -vlv_compute_drain_latency (crtc, pixel_size); + wm.ddl[pipe].primary =vlv_compute_drain_latency (crtc, crtc->primary); + wm.ddl[pipe].cursor =vlv_compute_drain_latency (crtc, crtc->cursor);vlv_write_wm_values (intel_crtc, &wm); }drivers/gpu/drm/i915/intel_pm.c static void valleyview_update_sprite_wm(struct drm_plane *plane, · line 957
Quoted 8 lines
drivers/gpu/drm/i915/intel_pm.c +1
-1@@ -961,7 +951,7 @@ static void valleyview_update_sprite_wm(struct drm_plane *plane,if (enabled) wm.ddl[pipe].sprite[sprite] = -vlv_compute_drain_latency (crtc, pixel_size); +vlv_compute_drain_latency (crtc, plane);else wm.ddl[pipe].sprite[sprite] =0 ;Nice.
Quoted 8 lines
Quoted 3 lines
Actually this is going to have issues now that atomic is partially in. We'd need to look at
plane->state->fbnow, but that steps on the same turf as Matt's latest patches.All the wm computation needs to be moved over to look at plane states, not
plane->state- we need to do all this in the check phase when state objects haven't been commited yet. Which is a lot more work and probably best done separately in one go than all over the place and inconsistently.
Sure, but the quick "keep things sort of working" fix is to look at plane->state since we currently do the wm calculation from commit.
Signature · 6 lines
Ville Syrjälä Intel OTC _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 06/12] drm/i915: Pass plane to vlv_compute_drain_latency()
Quoted 6 lines · Ville Syrjälä
Quoted 5 lines · Daniel Vetter
Quoted 3 lines · Ville Syrjälä
Actually this is going to have issues now that atomic is partially in. We'd need to look at
plane->state->fbnow, but that steps on the same turf as Matt's latest patches.
Quoted 7 lines
Quoted 4 lines
All the wm computation needs to be moved over to look at plane states, not
plane->state- we need to do all this in the check phase when state objects haven't been commited yet. Which is a lot more work and probably best done separately in one go than all over the place and inconsistently.Sure, but the quick "keep things sort of working" fix is to look at
plane->statesince we currently do the wm calculation from commit.
Yeah my reply was just with your comment about stepping onto Matt's turf. The minimal change to look at plane->state->fb is obviously needed and we can't avoid such conflicts really. Just figured we shouldn't charge ahead with changing interfaces all over the place.
-Daniel
Signature · 7 lines
Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 7/12 drm/i915: Read out display FIFO size on VLV/CHV
In reply to [email protected]From: Ville Syrjälä <[email protected]>
VLV/CHV have similar DSPARB registers as older platforms, just more of them due to more planes. Add a bit of code to read out the current FIFO split from the registers. Will be useful later when we improve the WM calculations.
--- drivers/gpu/drm/i915/i915_reg.h | 3 +++ drivers/gpu/drm/i915/intel_pm.c | 55 +++++++++++++++++++++++++++++++++++++++++ 2 files changed, 58 insertions(+)
drivers/gpu/drm/i915/i915_reg.h +3 -0
@@ -4034,6 +4034,9 @@ enum skl_disp_power_wells {#define DSPARB_BEND_SHIFT 9/* on 855 */ #define DSPARB_AEND_SHIFT 0 +#define DSPARB2 (VLV_DISPLAY_BASE + 0x70060)/* vlv/chv */ +#define DSPARB3 (VLV_DISPLAY_BASE + 0x7006c)/* chv */ +/* pnv/gen4/g4x/vlv/chv */ #define DSPFW1 (dev_priv->info.display_mmio_offset + 0x70034)#define DSPFW_SR_SHIFT 23
drivers/gpu/drm/i915/intel_pm.c +55 -0
61 lines not on this page · raw message
Signature · 6 lines
2.0.5 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v2 7/12 drm/i915: Read out display FIFO size on VLV/CHV
From: Ville Syrjälä <[email protected]>
VLV/CHV have similar DSPARB registers as older platforms, just more of them due to more planes. Add a bit of code to read out the current FIFO split from the registers. Will be useful later when we improve the WM calculations.
v2: Add display_mmio_offset to DSPARB
--- drivers/gpu/drm/i915/i915_reg.h | 5 +++- drivers/gpu/drm/i915/intel_pm.c | 55 +++++++++++++++++++++++++++++++++++++++++ 2 files changed, 59 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/i915_reg.h +4 -1
@@ -4026,7 +4026,7 @@ enum skl_disp_power_wells {#define DPINVGTT_STATUS_MASK 0xff#define DPINVGTT_STATUS_MASK_CHV 0xfff -#define DSPARB 0x70030 +#define DSPARB (dev_priv->info.display_mmio_offset + 0x70030)#define DSPARB_CSTART_MASK (0x7f << 7)#define DSPARB_CSTART_SHIFT 7#define DSPARB_BSTART_MASK (0x7f)
@@ -4034,6 +4034,9 @@ enum skl_disp_power_wells {#define DSPARB_BEND_SHIFT 9/* on 855 */ #define DSPARB_AEND_SHIFT 0 +#define DSPARB2 (VLV_DISPLAY_BASE + 0x70060)/* vlv/chv */ +#define DSPARB3 (VLV_DISPLAY_BASE + 0x7006c)/* chv */ +/* pnv/gen4/g4x/vlv/chv */ #define DSPFW1 (dev_priv->info.display_mmio_offset + 0x70034)#define DSPFW_SR_SHIFT 23
drivers/gpu/drm/i915/intel_pm.c +55 -0
61 lines not on this page · raw message
Signature · 6 lines
2.0.5 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v2 07/12] drm/i915: Read out display FIFO size on VLV/CHV
Quoted 95 lines · On 02/12/2015 10:59 AM, [email protected] wrote:
From: Ville Syrjälä <[email protected]>
VLV/CHV have similar DSPARB registers as older platforms, just more of them due to more planes. Add a bit of code to read out the current FIFO split from the registers. Will be useful later when we improve the WM calculations.
v2: Add
display_mmio_offsetto DSPARBSigned-off-by Ville Syrjälä <[email protected]>--- drivers/gpu/drm/i915/i915_reg.h | 5 +++- drivers/gpu/drm/i915/intel_pm.c | 55 +++++++++++++++++++++++++++++++++++++++++ 2 files changed, 59 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/i915_reg.h +4
-1@@ -4026,7 +4026,7 @@ enum skl_disp_power_wells {#define DPINVGTT_STATUS_MASK 0xff#define DPINVGTT_STATUS_MASK_CHV 0xfff -#define DSPARB 0x70030 +#define DSPARB (dev_priv->info.display_mmio_offset + 0x70030)#define DSPARB_CSTART_MASK (0x7f << 7)#define DSPARB_CSTART_SHIFT 7#define DSPARB_BSTART_MASK (0x7f)@@ -4034,6 +4034,9 @@ enum skl_disp_power_wells {#define DSPARB_BEND_SHIFT 9/* on 855 */ #define DSPARB_AEND_SHIFT 0 +#define DSPARB2 (VLV_DISPLAY_BASE + 0x70060)/* vlv/chv */ +#define DSPARB3 (VLV_DISPLAY_BASE + 0x7006c)/* chv */ +/* pnv/gen4/g4x/vlv/chv */ #define DSPFW1 (dev_priv->info.display_mmio_offset + 0x70034)#define DSPFW_SR_SHIFT 23drivers/gpu/drm/i915/intel_pm.c +48
-0@@ -280,6 +280,61 @@ void intel_set_memory_cxsr(struct drm_i915_private *dev_priv, bool enable)*/ static const int pessimal_latency_ns =5000 ; +#define VLV_FIFO_START (dsparb, dsparb2, lo_shift, hi_shift) \ + ((((dsparb) >> (lo_shift)) & 0xff) | ((((dsparb2) >> (hi_shift)) & 0x1) << 8)) + +static int vlv_get_fifo_size (struct drm_device *dev, +enum pipe pipe,int plane) +{ +struct drm_i915_private *dev_priv = dev->dev_private; +int sprite0_start, sprite1_start, size; + +switch (pipe) { +uint32_t dsparb, dsparb2, dsparb3; +case PIPE_A : + dsparb =I915_READ (DSPARB ); + dsparb2 =I915_READ (DSPARB2 ); + sprite0_start =VLV_FIFO_START (dsparb, dsparb2,0 ,0 ); + sprite1_start =VLV_FIFO_START (dsparb, dsparb2,8 ,4 ); +break ; +case PIPE_B : + dsparb =I915_READ (DSPARB ); + dsparb2 =I915_READ (DSPARB2 ); + sprite0_start =VLV_FIFO_START (dsparb, dsparb2,16 ,8 ); + sprite1_start =VLV_FIFO_START (dsparb, dsparb2,24 ,12 ); +break ; +case PIPE_C : + dsparb2 =I915_READ (DSPARB2 ); + dsparb3 =I915_READ (DSPARB3 ); + sprite0_start =VLV_FIFO_START (dsparb3, dsparb2,0 ,16 ); + sprite1_start =VLV_FIFO_START (dsparb3, dsparb2,8 ,20 ); +break ; +default : +return 0 ; + } + +switch (plane) { +case 0 : + size = sprite0_start; +break ; +case 1 : + size = sprite1_start - sprite0_start; +break ; +case 2 : + size =512 -1 - sprite1_start; +break ; +default : +return 0 ; + } + + DRM_DEBUG_KMS("Pipe %c %s %c FIFO size: %d\n",
drivers/gpu/drm/i915/intel_pm.c void intel_set_memory_cxsr(struct drm_i915_private *dev_priv, bool enable) · line 340
Quoted 10 lines
drivers/gpu/drm/i915/intel_pm.c +7
-0+pipe_name (pipe), plane ==0 ?"primary" :"sprite" , + plane ==0 ?plane_name (pipe) :sprite_name (pipe, plane -1 ), + size); + +return size; +} +static int i9xx_get_fifo_size (struct drm_device *dev,int plane) {struct drm_i915_private *dev_priv = dev->dev_private;
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 8/12 drm/i915: Make sure PND deadline mode is enabled on VLV/CHV
In reply to [email protected]From: Ville Syrjälä <[email protected]>
Poke at the CBR1_VLV register during init_clock_gating to make sure the PND deadline scheme is used.
The hardware has two modes of operation wrt. watermarks:
1) PND deadline mode:
- memory request deadline is calculated from actual FIFO level * DDL
- WM1 watermark values are unused (AFAIK)
- WM watermark level defines when to start fetching data from memory (assuming trickle feed is not used)
2) backup mode
- deadline is based on FIFO status, DDL is unused
- FIFO split into three regions with WM and WM1 watermarks, each part specifying a different FIFO status
We want to use the PND deadline mode, so let's make sure the chicken bit is in the correct position on init.
Also take the opportunity to refactor the shared code between VLV and CHV to a shared function.
--- drivers/gpu/drm/i915/i915_reg.h | 3 +++ drivers/gpu/drm/i915/intel_pm.c | 19 +++++++++++++------ 2 files changed, 16 insertions(+), 6 deletions(-)
drivers/gpu/drm/i915/i915_reg.h +3 -0
@@ -4177,6 +4177,9 @@ enum skl_disp_power_wells {#define DDL_PRECISION_LOW (0<<7)#define DRAIN_LATENCY_MASK 0x7f +#define CBR1_VLV (VLV_DISPLAY_BASE + 0x70400) +#define CBR_PND_DEADLINE_DISABLE (1<<31) +/* FIFO watermark sizes etc */ #define G4X_FIFO_LINE_SIZE 64#define I915_FIFO_LINE_SIZE 64
drivers/gpu/drm/i915/intel_pm.c +13 -6
@@ -6197,11 +6197,22 @@ static void ivybridge_init_clock_gating(struct drm_device *dev)gen6_check_mch_setup (dev); } +static void vlv_init_display_clock_gating (struct drm_i915_private *dev_priv) +{ +I915_WRITE (DSPCLK_GATE_D ,VRHUNIT_CLOCK_GATE_DISABLE ); + +/* +* Disable trickle feed and enable pnd deadline calculation +*/ +I915_WRITE (MI_ARB_VLV ,MI_ARB_DISPLAY_TRICKLE_FEED_DISABLE ); +I915_WRITE (CBR1_VLV ,0 ); +} +static void valleyview_init_clock_gating (struct drm_device *dev) {struct drm_i915_private *dev_priv = dev->dev_private; -I915_WRITE (DSPCLK_GATE_D ,VRHUNIT_CLOCK_GATE_DISABLE ); +vlv_init_display_clock_gating (dev_priv);/* WaDisableEarlyCull:vlv */ I915_WRITE(_3D_CHICKEN3,
@@ -6249,8 +6260,6 @@ static void valleyview_init_clock_gating(struct drm_device *dev)I915_WRITE (GEN7_UCGCTL4 ,I915_READ (GEN7_UCGCTL4 ) |GEN7_L3BANK2X_CLOCK_GATE_DISABLE ); -I915_WRITE (MI_ARB_VLV ,MI_ARB_DISPLAY_TRICKLE_FEED_DISABLE ); -/* * BSpec says this must be set, even though * WaDisable4x2SubspanOptimization isn't listed for VLV.
@@ -6287,9 +6296,7 @@ static void cherryview_init_clock_gating(struct drm_device *dev) {struct drm_i915_private *dev_priv = dev->dev_private; -I915_WRITE (DSPCLK_GATE_D ,VRHUNIT_CLOCK_GATE_DISABLE ); - -I915_WRITE (MI_ARB_VLV ,MI_ARB_DISPLAY_TRICKLE_FEED_DISABLE ); +vlv_init_display_clock_gating (dev_priv);/* WaVSRefCountFullforceMissDisable:chv */ /* WaDSRefCountFullforceMissDisable:chv */
Signature · 6 lines
2.0.5 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 08/12] drm/i915: Make sure PND deadline mode is enabled on VLV/CHV
Quoted 83 lines · On 02/10/2015 05:28 AM, [email protected] wrote:
From: Ville Syrjälä <[email protected]>
Poke at the
CBR1_VLVregister duringinit_clock_gatingto make sure the PND deadline scheme is used.The hardware has two modes of operation wrt. watermarks:
1) PND deadline mode:
- memory request deadline is calculated from actual FIFO level * DDL
- WM1 watermark values are unused (AFAIK)
- WM watermark level defines when to start fetching data from memory (assuming trickle feed is not used)2) backup mode
- deadline is based on FIFO status, DDL is unused
- FIFO split into three regions with WM and WM1 watermarks, each part specifying a different FIFO statusWe want to use the PND deadline mode, so let's make sure the chicken bit is in the correct position on init.
Also take the opportunity to refactor the shared code between VLV and CHV to a shared function.
Signed-off-by Ville Syrjälä <[email protected]>--- drivers/gpu/drm/i915/i915_reg.h | 3 +++ drivers/gpu/drm/i915/intel_pm.c | 19 +++++++++++++------ 2 files changed, 16 insertions(+), 6 deletions(-)drivers/gpu/drm/i915/i915_reg.h +3
-0@@ -4177,6 +4177,9 @@ enum skl_disp_power_wells {#define DDL_PRECISION_LOW (0<<7)#define DRAIN_LATENCY_MASK 0x7f +#define CBR1_VLV (VLV_DISPLAY_BASE + 0x70400) +#define CBR_PND_DEADLINE_DISABLE (1<<31) +/* FIFO watermark sizes etc */ #define G4X_FIFO_LINE_SIZE 64#define I915_FIFO_LINE_SIZE 64drivers/gpu/drm/i915/intel_pm.c +12
-3@@ -6197,11 +6197,22 @@ static void ivybridge_init_clock_gating(struct drm_device *dev)gen6_check_mch_setup (dev); } +static void vlv_init_display_clock_gating (struct drm_i915_private *dev_priv) +{ +I915_WRITE (DSPCLK_GATE_D ,VRHUNIT_CLOCK_GATE_DISABLE ); + +/* +* Disable trickle feed and enable pnd deadline calculation +*/ +I915_WRITE (MI_ARB_VLV ,MI_ARB_DISPLAY_TRICKLE_FEED_DISABLE ); +I915_WRITE (CBR1_VLV ,0 ); +} +static void valleyview_init_clock_gating (struct drm_device *dev) {struct drm_i915_private *dev_priv = dev->dev_private; -I915_WRITE (DSPCLK_GATE_D ,VRHUNIT_CLOCK_GATE_DISABLE ); +vlv_init_display_clock_gating (dev_priv);/* WaDisableEarlyCull:vlv */ I915_WRITE(_3D_CHICKEN3,@@ -6249,8 +6260,6 @@ static void valleyview_init_clock_gating(struct drm_device *dev)I915_WRITE (GEN7_UCGCTL4 ,I915_READ (GEN7_UCGCTL4 ) |GEN7_L3BANK2X_CLOCK_GATE_DISABLE ); -I915_WRITE (MI_ARB_VLV ,MI_ARB_DISPLAY_TRICKLE_FEED_DISABLE ); -/* * BSpec says this must be set, even though * WaDisable4x2SubspanOptimization isn't listed for VLV.
drivers/gpu/drm/i915/intel_pm.c static void cherryview_init_clock_gating(struct drm_device *dev) · line 6302
Quoted 10 lines
drivers/gpu/drm/i915/intel_pm.c +1
-3@@ -6287,9 +6296,7 @@ static void cherryview_init_clock_gating(struct drm_device *dev) {struct drm_i915_private *dev_priv = dev->dev_private; -I915_WRITE (DSPCLK_GATE_D ,VRHUNIT_CLOCK_GATE_DISABLE ); - -I915_WRITE (MI_ARB_VLV ,MI_ARB_DISPLAY_TRICKLE_FEED_DISABLE ); +vlv_init_display_clock_gating (dev_priv);/* WaVSRefCountFullforceMissDisable:chv */ /* WaDSRefCountFullforceMissDisable:chv */
Is the deadline mode preference documented somewhere? Do we need another bspec bug filed?
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 08/12] drm/i915: Make sure PND deadline mode is enabled on VLV/CHV
Quoted 91 lines · Jesse Barnes
Quoted 90 lines · On 02/10/2015 05:28 AM, [email protected] wrote:
From: Ville Syrjälä <[email protected]>
Poke at the
CBR1_VLVregister duringinit_clock_gatingto make sure the PND deadline scheme is used.The hardware has two modes of operation wrt. watermarks:
1) PND deadline mode:
- memory request deadline is calculated from actual FIFO level * DDL
- WM1 watermark values are unused (AFAIK)
- WM watermark level defines when to start fetching data from memory (assuming trickle feed is not used)2) backup mode
- deadline is based on FIFO status, DDL is unused
- FIFO split into three regions with WM and WM1 watermarks, each part specifying a different FIFO statusWe want to use the PND deadline mode, so let's make sure the chicken bit is in the correct position on init.
Also take the opportunity to refactor the shared code between VLV and CHV to a shared function.
Signed-off-by Ville Syrjälä <[email protected]>--- drivers/gpu/drm/i915/i915_reg.h | 3 +++ drivers/gpu/drm/i915/intel_pm.c | 19 +++++++++++++------ 2 files changed, 16 insertions(+), 6 deletions(-)drivers/gpu/drm/i915/i915_reg.h +3
-0@@ -4177,6 +4177,9 @@ enum skl_disp_power_wells {#define DDL_PRECISION_LOW (0<<7)#define DRAIN_LATENCY_MASK 0x7f +#define CBR1_VLV (VLV_DISPLAY_BASE + 0x70400) +#define CBR_PND_DEADLINE_DISABLE (1<<31) +/* FIFO watermark sizes etc */ #define G4X_FIFO_LINE_SIZE 64#define I915_FIFO_LINE_SIZE 64drivers/gpu/drm/i915/intel_pm.c +13
-6@@ -6197,11 +6197,22 @@ static void ivybridge_init_clock_gating(struct drm_device *dev)gen6_check_mch_setup (dev); } +static void vlv_init_display_clock_gating (struct drm_i915_private *dev_priv) +{ +I915_WRITE (DSPCLK_GATE_D ,VRHUNIT_CLOCK_GATE_DISABLE ); + +/* +* Disable trickle feed and enable pnd deadline calculation +*/ +I915_WRITE (MI_ARB_VLV ,MI_ARB_DISPLAY_TRICKLE_FEED_DISABLE ); +I915_WRITE (CBR1_VLV ,0 ); +} +static void valleyview_init_clock_gating (struct drm_device *dev) {struct drm_i915_private *dev_priv = dev->dev_private; -I915_WRITE (DSPCLK_GATE_D ,VRHUNIT_CLOCK_GATE_DISABLE ); +vlv_init_display_clock_gating (dev_priv);/* WaDisableEarlyCull:vlv */ I915_WRITE(_3D_CHICKEN3,@@ -6249,8 +6260,6 @@ static void valleyview_init_clock_gating(struct drm_device *dev)I915_WRITE (GEN7_UCGCTL4 ,I915_READ (GEN7_UCGCTL4 ) |GEN7_L3BANK2X_CLOCK_GATE_DISABLE ); -I915_WRITE (MI_ARB_VLV ,MI_ARB_DISPLAY_TRICKLE_FEED_DISABLE ); -/* * BSpec says this must be set, even though * WaDisable4x2SubspanOptimization isn't listed for VLV. @@ -6287,9 +6296,7 @@ static void cherryview_init_clock_gating(struct drm_device *dev) {struct drm_i915_private *dev_priv = dev->dev_private; -I915_WRITE (DSPCLK_GATE_D ,VRHUNIT_CLOCK_GATE_DISABLE ); - -I915_WRITE (MI_ARB_VLV ,MI_ARB_DISPLAY_TRICKLE_FEED_DISABLE ); +vlv_init_display_clock_gating (dev_priv);
Quoted 6 lines
drivers/gpu/drm/i915/intel_pm.c static void cherryview_init_clock_gating(struct drm_device *dev) · line 6302
Quoted 3 lines
drivers/gpu/drm/i915/intel_pm.c +0
-0/* WaVSRefCountFullforceMissDisable:chv */ /* WaDSRefCountFullforceMissDisable:chv */ Is the deadline mode preference documented somewhere? Do we need another bspec bug filed?
VLV display cluster HAS had a fairly good description. We can at least hope it works well enough on VLV. Sadly it doesn't actually work the way you'd expect on CHV, but that's a whole other story.
Quoted 2 lines
Reviewed-by Jesse Barnes <[email protected]>
Signature · 6 lines
Ville Syrjälä Intel OTC _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 9/12 drm/i915: Rewrite VLV/CHV watermark code
In reply to [email protected]From: Ville Syrjälä <[email protected]>
Assuming the PND deadline mechanism works reasonably we should do memory requests as early as possible so that PND has schedule the requests more intelligently. Currently we're still calculating the watermarks as if VLV/CHV are identical to g4x, which isn't the case.
The current code also seems to calculate insufficient watermarks and hence we're seeing some underruns, especially on high resolution displays.
To fix it just rip out the current code and replace is with something that tries to utilize PND as efficiently as possible.
We now calculate the WM watermark to trigger when the FIFO still has 256us worth of data. 256us is the maximum deadline value supoorted by PND, so issuing memory requests earlier would mean we probably couldn't utilize the full FIFO as PND would attempt to return the data at least in at least 256us. We also clamp the watermark to at least 8 cachelines as that's the magic watermark that enabling trickle feed would also impose. I'm assuming it matches some burst size.
In theory we could just enable trickle feed and ignore the WM values, except trickle feed doesn't work with max fifo mode anyway, so we'd still need to calculate the SR watermarks. It seems cleaner to just disable trickle feed and calculate all watermarks the same way. Also trickle feed wouldn't account for the 256us max deadline value, thoguh that may be a moot point in non-max fifo mode sicne the FIFOs are fairly small.
On VLV max fifo mode can be used with either primary or sprite planes. So the code now also checks all the planes (apart from the cursor) when calculating the SR plane watermark.
We don't have to worry about the WM1 watermarks since we're using the PND deadline scheme which means the hardware ignores WM1 values.
--- drivers/gpu/drm/i915/i915_drv.h | 11 ++ drivers/gpu/drm/i915/i915_reg.h | 4 +- drivers/gpu/drm/i915/intel_pm.c | 327 +++++++++++++++++++++------------------- 3 files changed, 185 insertions(+), 157 deletions(-)
drivers/gpu/drm/i915/i915_drv.h +11 -0
@@ -1516,6 +1516,17 @@ struct ilk_wm_values {struct vlv_wm_values {struct { +uint16_t primary; +uint16_t sprite[2 ]; +uint8_t cursor; + } pipe[3 ]; + +struct { +uint16_t plane; +uint8_t cursor; + } sr; + +struct {uint8_t cursor;uint8_t sprite[2 ];uint8_t primary;
drivers/gpu/drm/i915/i915_reg.h +2 -2
@@ -4127,7 +4127,7 @@ enum skl_disp_power_wells {/* vlv/chv high order bits */ #define DSPHOWM (VLV_DISPLAY_BASE + 0x70064)#define DSPFW_SR_HI_SHIFT 24 -#define DSPFW_SR_HI_MASK (1<<24) +#define DSPFW_SR_HI_MASK (3<<24)/* 2 bits for chv, 1 for vlv */ #define DSPFW_SPRITEF_HI_SHIFT 23#define DSPFW_SPRITEF_HI_MASK (1<<23)#define DSPFW_SPRITEE_HI_SHIFT 22
@@ -4148,7 +4148,7 @@ enum skl_disp_power_wells {#define DSPFW_PLANEA_HI_MASK (1<<0)#define DSPHOWM1 (VLV_DISPLAY_BASE + 0x70068)#define DSPFW_SR_WM1_HI_SHIFT 24 -#define DSPFW_SR_WM1_HI_MASK (1<<24) +#define DSPFW_SR_WM1_HI_MASK (3<<24)/* 2 bits for chv, 1 for vlv */ #define DSPFW_SPRITEF_WM1_HI_SHIFT 23#define DSPFW_SPRITEF_WM1_HI_MASK (1<<23)#define DSPFW_SPRITEE_WM1_HI_SHIFT 22
drivers/gpu/drm/i915/intel_pm.c +172 -155
371 lines not on this page · raw message
Signature · 6 lines
2.0.5 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 09/12] drm/i915: Rewrite VLV/CHV watermark code
Quoted 31 lines · On Tue, Feb 10, 2015 at 03:28:26PM +0200, [email protected] wrote:
From: Ville Syrjälä <[email protected]>
Assuming the PND deadline mechanism works reasonably we should do memory requests as early as possible so that PND has schedule the requests more intelligently. Currently we're still calculating the watermarks as if VLV/CHV are identical to g4x, which isn't the case.
The current code also seems to calculate insufficient watermarks and hence we're seeing some underruns, especially on high resolution displays.
To fix it just rip out the current code and replace is with something that tries to utilize PND as efficiently as possible.
We now calculate the WM watermark to trigger when the FIFO still has 256us worth of data. 256us is the maximum deadline value supoorted by PND, so issuing memory requests earlier would mean we probably couldn't utilize the full FIFO as PND would attempt to return the data at least in at least 256us. We also clamp the watermark to at least 8 cachelines as that's the magic watermark that enabling trickle feed would also impose. I'm assuming it matches some burst size.
In theory we could just enable trickle feed and ignore the WM values, except trickle feed doesn't work with max fifo mode anyway, so we'd still need to calculate the SR watermarks. It seems cleaner to just disable trickle feed and calculate all watermarks the same way. Also trickle feed wouldn't account for the 256us max deadline value, thoguh that may be a moot point in non-max fifo mode sicne the FIFOs are fairly small.
Quoted 8 lines
On VLV max fifo mode can be used with either primary or sprite planes. So the code now also checks all the planes (apart from the cursor) when calculating the SR plane watermark.
We don't have to worry about the WM1 watermarks since we're using the PND deadline scheme which means the hardware ignores WM1 values.
Signed-off-by Ville Syrjälä <[email protected]>
This patch still lacks review. Any takers?
Signature · 6 lines
Ville Syrjälä Intel OTC _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 10/12 drm/i915: Support maxfifo with two planes on CHV
In reply to [email protected]From: Ville Syrjälä <[email protected]>
CHV supposedly does maxfifo mode even with two enabled (primary/sprite) planes. Lets try to support that by halving the FIFO size for the calculations and picking the smallest calculcated watermark from the enabled planes.
--- drivers/gpu/drm/i915/intel_pm.c | 22 +++++++++++++++++----- 1 file changed, 17 insertions(+), 5 deletions(-)
drivers/gpu/drm/i915/intel_pm.c +17 -5
@@ -907,6 +907,8 @@ static bool vlv_compute_sr_wm(struct drm_device *dev,int num_planes =0 ;int fifo_size =0 ;struct intel_plane *plane; +/* CHV supports max fifo with two planes (1:1 split) */ +int max_planes =IS_CHERRYVIEW (dev) ?2 :1 ; wm->sr.cursor = wm->sr.plane =0 ;
@@ -920,23 +922,33 @@ static bool vlv_compute_sr_wm(struct drm_device *dev, fifo_size =INTEL_INFO (dev_priv)->num_pipes *512 -1 ; } -if (fifo_size ==0 || num_planes >1 ) +if (fifo_size ==0 || num_planes > max_planes)return false; +if (num_planes) + fifo_size /= num_planes; + wm->sr.cursor =vlv_compute_wm (to_intel_crtc (crtc),to_intel_plane (crtc->cursor),0x3f );list_for_each_entry (plane, &dev->mode_config.plane_list, base.head) { +uint16_t sr_wm; +if (plane->base.type ==DRM_PLANE_TYPE_CURSOR )continue ;if (plane->pipe != pipe)continue ; - wm->sr.plane =vlv_compute_wm (to_intel_crtc (crtc), - plane, fifo_size); -if (wm->sr.plane !=0 ) -break ; + sr_wm =vlv_compute_wm (to_intel_crtc (crtc), + plane, fifo_size); +if (sr_wm ==0 ) +continue ; + +if (wm->sr.plane ==0 ) + wm->sr.plane = sr_wm; +else + wm->sr.plane =min (wm->sr.plane, sr_wm); }return true;
Signature · 6 lines
2.0.5 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 10/12] drm/i915: Support maxfifo with two planes on CHV
Quoted 6 lines · On 2/10/2015 6:58 PM, [email protected] wrote:
From: Ville Syrjälä <[email protected]>
CHV supposedly does maxfifo mode even with two enabled (primary/sprite) planes. Lets try to support that by halving the FIFO size for the calculations and picking the smallest calculcated watermark from the enabled planes.
Where is this mentioned in the spec? My understanding is MaxFIFO can be enabled when only one plane is active (either ARGB or YUV). I do remember some TR task that was talking about enabling MaxFIFO for two planes. But i didn't get any confirmation that this can be enabled. We have not enabled this for CHT in any other OS (Windows / Android).
Other features like PM2 / PM5 / DVFS can be enabled for multi plane scenarios
Thanks,
Vijay
Quoted 48 lines
Signed-off-by Ville Syrjälä <[email protected]>--- drivers/gpu/drm/i915/intel_pm.c | 22 +++++++++++++++++----- 1 file changed, 17 insertions(+), 5 deletions(-)drivers/gpu/drm/i915/intel_pm.c +10
-5@@ -907,6 +907,8 @@ static bool vlv_compute_sr_wm(struct drm_device *dev,int num_planes =0 ;int fifo_size =0 ;struct intel_plane *plane; +/* CHV supports max fifo with two planes (1:1 split) */ +int max_planes =IS_CHERRYVIEW (dev) ?2 :1 ; wm->sr.cursor = wm->sr.plane =0 ;@@ -920,23 +922,33 @@ static bool vlv_compute_sr_wm(struct drm_device *dev, fifo_size =INTEL_INFO (dev_priv)->num_pipes *512 -1 ; } -if (fifo_size ==0 || num_planes >1 ) +if (fifo_size ==0 || num_planes > max_planes)return false; +if (num_planes) + fifo_size /= num_planes; + wm->sr.cursor =vlv_compute_wm (to_intel_crtc (crtc),to_intel_plane (crtc->cursor),0x3f );list_for_each_entry (plane, &dev->mode_config.plane_list, base.head) { +uint16_t sr_wm; +if (plane->base.type ==DRM_PLANE_TYPE_CURSOR )continue ;if (plane->pipe != pipe)continue ; - wm->sr.plane =vlv_compute_wm (to_intel_crtc (crtc), - plane, fifo_size); -if (wm->sr.plane !=0 ) -break ; + sr_wm =vlv_compute_wm (to_intel_crtc (crtc), + plane, fifo_size);
drivers/gpu/drm/i915/intel_pm.c static bool vlv_compute_sr_wm(struct drm_device *dev, · line 954
Quoted 10 lines
drivers/gpu/drm/i915/intel_pm.c +7
-0+if (sr_wm ==0 ) +continue ; + +if (wm->sr.plane ==0 ) + wm->sr.plane = sr_wm; +else + wm->sr.plane =min (wm->sr.plane, sr_wm); }return true;
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 10/12] drm/i915: Support maxfifo with two planes on CHV
Quoted 11 lines · Vijay A
Quoted 6 lines · On 2/10/2015 6:58 PM, [email protected] wrote:
From: Ville Syrjälä <[email protected]>
CHV supposedly does maxfifo mode even with two enabled (primary/sprite) planes. Lets try to support that by halving the FIFO size for the calculations and picking the smallest calculcated watermark from the enabled planes.
Where is this mentioned in the spec? My understanding is MaxFIFO can be enabled when only one plane is active (either ARGB or YUV). I do remember some TR task that was talking about enabling MaxFIFO for two planes. But i didn't get any confirmation that this can be enabled.
It was mentioned in the display cluster HAS (also maybe some version of the PUNIT HAS), but I wasn't sure it's actually there. IIRC the answer I got in one DDR DVFS meeting was that yes it does exit. But I've not actually confirmed whether it seems to work on real hardware. The annoying thing is that there doesn't seem to be any kind of status bit to tell me if it has entered maxfifo or not, so it would need to be deduced from some other facts.
Anyway, we can just skip this patch as it's still somewhat unclear if this can be used or not.
Quoted 5 lines
We
have not enabled this for CHT in any other OS (Windows / Android).Other features like PM2 / PM5 / DVFS can be enabled for multi plane scenarios
As far as I know we can't even control PM2. So the only thing we can influence is whether it will enter PM2 or PM5 when things are sufficiently idle. So we must always tolerate the PM2 latency, and if we can tolerate the extra PM5 latency we can then choose PM5 over PM2.
Previously I thought the something would check if the display is in maxfifo or not before entering PM2/PM5, but now I can't see anything to back that up. So I suppose we must always verify that even the non-maxfifo FIFO sizes can tolerate the latency, whether or not we have enable maxfifo or not (since we can't force maxfifo entry, and instead the hardware just decides that by itself).
Quoted 66 lines
Thanks,
VijayQuoted 48 lines
Signed-off-by Ville Syrjälä <[email protected]>--- drivers/gpu/drm/i915/intel_pm.c | 22 +++++++++++++++++----- 1 file changed, 17 insertions(+), 5 deletions(-)drivers/gpu/drm/i915/intel_pm.c +10
-5@@ -907,6 +907,8 @@ static bool vlv_compute_sr_wm(struct drm_device *dev,int num_planes =0 ;int fifo_size =0 ;struct intel_plane *plane; +/* CHV supports max fifo with two planes (1:1 split) */ +int max_planes =IS_CHERRYVIEW (dev) ?2 :1 ; wm->sr.cursor = wm->sr.plane =0 ;@@ -920,23 +922,33 @@ static bool vlv_compute_sr_wm(struct drm_device *dev, fifo_size =INTEL_INFO (dev_priv)->num_pipes *512 -1 ; } -if (fifo_size ==0 || num_planes >1 ) +if (fifo_size ==0 || num_planes > max_planes)return false; +if (num_planes) + fifo_size /= num_planes; + wm->sr.cursor =vlv_compute_wm (to_intel_crtc (crtc),to_intel_plane (crtc->cursor),0x3f );list_for_each_entry (plane, &dev->mode_config.plane_list, base.head) { +uint16_t sr_wm; +if (plane->base.type ==DRM_PLANE_TYPE_CURSOR )continue ;if (plane->pipe != pipe)continue ; - wm->sr.plane =vlv_compute_wm (to_intel_crtc (crtc), - plane, fifo_size); -if (wm->sr.plane !=0 ) -break ; + sr_wm =vlv_compute_wm (to_intel_crtc (crtc), + plane, fifo_size);drivers/gpu/drm/i915/intel_pm.c static bool vlv_compute_sr_wm(struct drm_device *dev, · line 954
Quoted 10 lines
drivers/gpu/drm/i915/intel_pm.c +7
-0+if (sr_wm ==0 ) +continue ; + +if (wm->sr.plane ==0 ) + wm->sr.plane = sr_wm; +else + wm->sr.plane =min (wm->sr.plane, sr_wm); }return true;_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Signature · 6 lines
Ville Syrjälä Intel OTC _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 11/12 drm/i915: Program PFI credits for VLV
In reply to [email protected]From: Vidya Srinivas <[email protected]>
PFI credit programming is required when CD clock (related to data flow from display pipeline to end display) is greater than CZ clock (related to data flow from memory to display plane). This programming should be done when all planes are OFF to avoid intermittent hangs while accessing memory even from different Gfx units (not just display).
If cdclk/czclk >=1, PFI credits could be set as any number. To get better performance, larger PFI credit can be assigned to PND. Otherwise if cdclk/czclk<1, the default PFI credit of 8 should be set.
v2:
- Change log to lower log level instead of DRM_ERROR
- Change function name to valleyview_program_pfi_credits
- Move program PFI credits to modeset_init instead of intel_set_mode
- Change magic numbers to logical constants
[vsyrjala v3:
- only program in response to cdclk update
- program the credits also when cdclk<czclk
- add CHV bits]
--- drivers/gpu/drm/i915/i915_reg.h | 8 ++++++++ drivers/gpu/drm/i915/intel_display.c | 33 +++++++++++++++++++++++++++++++++ 2 files changed, 41 insertions(+)
drivers/gpu/drm/i915/i915_reg.h +8 -0
@@ -2061,6 +2061,14 @@ enum skl_disp_power_wells {#define CDCLK_FREQ_SHIFT 4#define CDCLK_FREQ_MASK (0x1f << CDCLK_FREQ_SHIFT)#define CZCLK_FREQ_MASK 0xf + +#define GCI_CONTROL (VLV_DISPLAY_BASE + 0x650C) +#define PFI_CREDIT_63 (9 << 28)/* chv only */ +#define PFI_CREDIT_31 (8 << 28)/* chv only */ +#define PFI_CREDIT (x) (((x) - 8) << 28)/* 8-15 */ +#define PFI_CREDIT_RESEND (1 << 27) +#define VGA_FAST_MODE_DISABLE (1 << 14) +#define GMBUSFREQ_VLV (VLV_DISPLAY_BASE + 0x6510)/*
drivers/gpu/drm/i915/intel_display.c +33 -0
@@ -4987,6 +4987,37 @@ static void valleyview_modeset_global_pipes(struct drm_device *dev, *prepare_pipes |= (1 << intel_crtc->pipe); } +static void vlv_program_pfi_credits (struct drm_i915_private *dev_priv) +{ +unsigned int credits; + +if (DIV_ROUND_CLOSEST (dev_priv->vlv_cdclk_freq,1000 ) >= dev_priv->rps.cz_freq) { +/* CHV suggested value is 31 or 63 */ +if (IS_CHERRYVIEW (dev_priv)) + credits =PFI_CREDIT_31 ; +else + credits =PFI_CREDIT (15 ); + }else { + credits =PFI_CREDIT (8 ); + } + +/* +* WA - write default credits before re-programming +* FIXME: should we also set the resend bit here? +*/ +I915_WRITE (GCI_CONTROL ,VGA_FAST_MODE_DISABLE | +PFI_CREDIT (8 )); + +I915_WRITE (GCI_CONTROL ,VGA_FAST_MODE_DISABLE | + credits |PFI_CREDIT_RESEND ); + +/* +* FIXME is this guaranteed to clear +* immediately or should we poll for it? +*/ +WARN_ON (I915_READ (GCI_CONTROL ) &PFI_CREDIT_RESEND ); +} +static void valleyview_modeset_global_resources (struct drm_device *dev) {struct drm_i915_private *dev_priv = dev->dev_private;
@@ -5010,6 +5041,8 @@ static void valleyview_modeset_global_resources(struct drm_device *dev)else valleyview_set_cdclk (dev, req_cdclk); +vlv_program_pfi_credits (dev_priv); +intel_display_power_put (dev_priv,POWER_DOMAIN_PIPE_A ); } }
Signature · 6 lines
2.0.5 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 11/12] drm/i915: Program PFI credits for VLV
Quoted 61 lines · On 2/10/2015 6:58 PM, [email protected] wrote:
From: Vidya Srinivas <[email protected]>
PFI credit programming is required when CD clock (related to data flow from display pipeline to end display) is greater than CZ clock (related to data flow from memory to display plane). This programming should be done when all planes are OFF to avoid intermittent hangs while accessing memory even from different Gfx units (not just display).
If cdclk/czclk >=1, PFI credits could be set as any number. To get better performance, larger PFI credit can be assigned to PND. Otherwise if cdclk/czclk<1, the default PFI credit of 8 should be set.
v2:
- Change log to lower log level instead ofDRM_ERROR
- Change function name tovalleyview_program_pfi_credits
- Move program PFI credits tomodeset_initinstead ofintel_set_mode
- Change magic numbers to logical constants[vsyrjala v3:
- only program in response to cdclk update
- program the credits also when cdclk<czclk
- add CHV bits]Signed-off-by Vidya Srinivas <[email protected]>Signed-off-by Gajanan Bhat <[email protected]>Signed-off-by Vandana Kannan <[email protected]>Signed-off-by Ville Syrjälä <[email protected]>--- drivers/gpu/drm/i915/i915_reg.h | 8 ++++++++ drivers/gpu/drm/i915/intel_display.c | 33 +++++++++++++++++++++++++++++++++ 2 files changed, 41 insertions(+)drivers/gpu/drm/i915/i915_reg.h +8
-0@@ -2061,6 +2061,14 @@ enum skl_disp_power_wells {#define CDCLK_FREQ_SHIFT 4#define CDCLK_FREQ_MASK (0x1f << CDCLK_FREQ_SHIFT)#define CZCLK_FREQ_MASK 0xf + +#define GCI_CONTROL (VLV_DISPLAY_BASE + 0x650C) +#define PFI_CREDIT_63 (9 << 28)/* chv only */ +#define PFI_CREDIT_31 (8 << 28)/* chv only */ +#define PFI_CREDIT (x) (((x) - 8) << 28)/* 8-15 */ +#define PFI_CREDIT_RESEND (1 << 27) +#define VGA_FAST_MODE_DISABLE (1 << 14) +#define GMBUSFREQ_VLV (VLV_DISPLAY_BASE + 0x6510)/* drivers/gpu/drm/i915/intel_display.c +2
-0@@ -4987,6 +4987,37 @@ static void valleyview_modeset_global_pipes(struct drm_device *dev, *prepare_pipes |= (1 << intel_crtc->pipe); } +static void vlv_program_pfi_credits (struct drm_i915_private *dev_priv) +{
drivers/gpu/drm/i915/intel_display.c static void valleyview_modeset_global_pipes(struct drm_device *dev, · line 5001
Quoted 10 lines
drivers/gpu/drm/i915/intel_display.c +10
-0+unsigned int credits; + +if (DIV_ROUND_CLOSEST (dev_priv->vlv_cdclk_freq,1000 ) >= dev_priv->rps.cz_freq) { +/* CHV suggested value is 31 or 63 */ +if (IS_CHERRYVIEW (dev_priv)) + credits =PFI_CREDIT_31 ; +else + credits =PFI_CREDIT (15 ); + }else { + credits =PFI_CREDIT (8 );
The default value should be 4 credits for CHV and 0 for VLV.
drivers/gpu/drm/i915/intel_display.c static void valleyview_modeset_global_pipes(struct drm_device *dev, · line 5009
Quoted 8 lines
drivers/gpu/drm/i915/intel_display.c +8
-0+ } + +/* +* WA - write default credits before re-programming +* FIXME: should we also set the resend bit here? +*/ +I915_WRITE (GCI_CONTROL ,VGA_FAST_MODE_DISABLE | +PFI_CREDIT (8 ));
Default credit should be 4 credits for CHV. PFI_CREDIT(12). Document update is pending. But this is the latest recommendation to windows team.
Thanks,
Vijay
Quoted 15 lines
drivers/gpu/drm/i915/intel_display.c +11
-0+ +I915_WRITE (GCI_CONTROL ,VGA_FAST_MODE_DISABLE | + credits |PFI_CREDIT_RESEND ); + +/* +* FIXME is this guaranteed to clear +* immediately or should we poll for it? +*/ +WARN_ON (I915_READ (GCI_CONTROL ) &PFI_CREDIT_RESEND ); +} +static void valleyview_modeset_global_resources (struct drm_device *dev) {struct drm_i915_private *dev_priv = dev->dev_private;
drivers/gpu/drm/i915/intel_display.c static void valleyview_modeset_global_resources(struct drm_device *dev) · line 5048
Quoted 8 lines
drivers/gpu/drm/i915/intel_display.c +2
-0@@ -5010,6 +5041,8 @@ static void valleyview_modeset_global_resources(struct drm_device *dev)else valleyview_set_cdclk (dev, req_cdclk); +vlv_program_pfi_credits (dev_priv); +intel_display_power_put (dev_priv,POWER_DOMAIN_PIPE_A ); } }
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 11/12] drm/i915: Program PFI credits for VLV
Quoted 60 lines · Vijay A
Quoted 59 lines · On 2/10/2015 6:58 PM, [email protected] wrote:
From: Vidya Srinivas <[email protected]>
PFI credit programming is required when CD clock (related to data flow from display pipeline to end display) is greater than CZ clock (related to data flow from memory to display plane). This programming should be done when all planes are OFF to avoid intermittent hangs while accessing memory even from different Gfx units (not just display).
If cdclk/czclk >=1, PFI credits could be set as any number. To get better performance, larger PFI credit can be assigned to PND. Otherwise if cdclk/czclk<1, the default PFI credit of 8 should be set.
v2:
- Change log to lower log level instead ofDRM_ERROR
- Change function name tovalleyview_program_pfi_credits
- Move program PFI credits tomodeset_initinstead ofintel_set_mode
- Change magic numbers to logical constants[vsyrjala v3:
- only program in response to cdclk update
- program the credits also when cdclk<czclk
- add CHV bits]Signed-off-by Vidya Srinivas <[email protected]>Signed-off-by Gajanan Bhat <[email protected]>Signed-off-by Vandana Kannan <[email protected]>Signed-off-by Ville Syrjälä <[email protected]>--- drivers/gpu/drm/i915/i915_reg.h | 8 ++++++++ drivers/gpu/drm/i915/intel_display.c | 33 +++++++++++++++++++++++++++++++++ 2 files changed, 41 insertions(+)drivers/gpu/drm/i915/i915_reg.h +8
-0@@ -2061,6 +2061,14 @@ enum skl_disp_power_wells {#define CDCLK_FREQ_SHIFT 4#define CDCLK_FREQ_MASK (0x1f << CDCLK_FREQ_SHIFT)#define CZCLK_FREQ_MASK 0xf + +#define GCI_CONTROL (VLV_DISPLAY_BASE + 0x650C) +#define PFI_CREDIT_63 (9 << 28)/* chv only */ +#define PFI_CREDIT_31 (8 << 28)/* chv only */ +#define PFI_CREDIT (x) (((x) - 8) << 28)/* 8-15 */ +#define PFI_CREDIT_RESEND (1 << 27) +#define VGA_FAST_MODE_DISABLE (1 << 14) +#define GMBUSFREQ_VLV (VLV_DISPLAY_BASE + 0x6510)/* drivers/gpu/drm/i915/intel_display.c +0
-0@@ -4987,6 +4987,37 @@ static void valleyview_modeset_global_pipes(struct drm_device *dev, *prepare_pipes |= (1 << intel_crtc->pipe); }
Quoted 13 lines
drivers/gpu/drm/i915/intel_display.c static void valleyview_modeset_global_pipes(struct drm_device *dev, · line 5001
Quoted 12 lines
drivers/gpu/drm/i915/intel_display.c +12
-0+static void vlv_program_pfi_credits (struct drm_i915_private *dev_priv) +{ +unsigned int credits; + +if (DIV_ROUND_CLOSEST (dev_priv->vlv_cdclk_freq,1000 ) >= dev_priv->rps.cz_freq) { +/* CHV suggested value is 31 or 63 */ +if (IS_CHERRYVIEW (dev_priv)) + credits =PFI_CREDIT_31 ; +else + credits =PFI_CREDIT (15 ); + }else { + credits =PFI_CREDIT (8 );The default value should be 4 credits for CHV and 0 for VLV.
8 is the minimum. So I think on CHV we actually want PFI_CREDIT(12).
The reason the CHV value is wrong here is because I wrote the patch based on the spec, and sadly the new recommended value isn't in the spec.
Quoted 11 lines
drivers/gpu/drm/i915/intel_display.c static void valleyview_modeset_global_pipes(struct drm_device *dev, · line 5009
Quoted 9 lines
drivers/gpu/drm/i915/intel_display.c +8
-0+ } + +/* +* WA - write default credits before re-programming +* FIXME: should we also set the resend bit here? +*/ +I915_WRITE (GCI_CONTROL ,VGA_FAST_MODE_DISABLE | +PFI_CREDIT (8 ));Default credit should be 4 credits for CHV.
PFI_CREDIT(12). Document update is pending. But this is the latest recommendation to windows team.
Right. So exactly as I thought too. I'll respin the patch with the new value.
Quoted 32 lines
Thanks,
VijayQuoted 15 lines
drivers/gpu/drm/i915/intel_display.c +11
-0+ +I915_WRITE (GCI_CONTROL ,VGA_FAST_MODE_DISABLE | + credits |PFI_CREDIT_RESEND ); + +/* +* FIXME is this guaranteed to clear +* immediately or should we poll for it? +*/ +WARN_ON (I915_READ (GCI_CONTROL ) &PFI_CREDIT_RESEND ); +} +static void valleyview_modeset_global_resources (struct drm_device *dev) {struct drm_i915_private *dev_priv = dev->dev_private;drivers/gpu/drm/i915/intel_display.c static void valleyview_modeset_global_resources(struct drm_device *dev) · line 5048
Quoted 8 lines
drivers/gpu/drm/i915/intel_display.c +2
-0@@ -5010,6 +5041,8 @@ static void valleyview_modeset_global_resources(struct drm_device *dev)else valleyview_set_cdclk (dev, req_cdclk); +vlv_program_pfi_credits (dev_priv); +intel_display_power_put (dev_priv,POWER_DOMAIN_PIPE_A ); } }_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Signature · 6 lines
Ville Syrjälä Intel OTC _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 11/12] drm/i915: Program PFI credits for VLV
In reply to Purushothaman, Vijay AQuoted 74 lines · Vijay A
Quoted 61 lines · On 2/10/2015 6:58 PM, [email protected] wrote:
From: Vidya Srinivas <[email protected]>
PFI credit programming is required when CD clock (related to data flow from display pipeline to end display) is greater than CZ clock (related to data flow from memory to display plane). This programming should be done when all planes are OFF to avoid intermittent hangs while accessing memory even from different Gfx units (not just display).
If cdclk/czclk >=1, PFI credits could be set as any number. To get better performance, larger PFI credit can be assigned to PND. Otherwise if cdclk/czclk<1, the default PFI credit of 8 should be set.
v2:
- Change log to lower log level instead ofDRM_ERROR
- Change function name tovalleyview_program_pfi_credits
- Move program PFI credits tomodeset_initinstead ofintel_set_mode
- Change magic numbers to logical constants[vsyrjala v3:
- only program in response to cdclk update
- program the credits also when cdclk<czclk
- add CHV bits]Signed-off-by Vidya Srinivas <[email protected]>Signed-off-by Gajanan Bhat <[email protected]>Signed-off-by Vandana Kannan <[email protected]>Signed-off-by Ville Syrjälä <[email protected]>--- drivers/gpu/drm/i915/i915_reg.h | 8 ++++++++ drivers/gpu/drm/i915/intel_display.c | 33 +++++++++++++++++++++++++++++++++ 2 files changed, 41 insertions(+)drivers/gpu/drm/i915/i915_reg.h +8
-0@@ -2061,6 +2061,14 @@ enum skl_disp_power_wells {#define CDCLK_FREQ_SHIFT 4#define CDCLK_FREQ_MASK (0x1f << CDCLK_FREQ_SHIFT)#define CZCLK_FREQ_MASK 0xf + +#define GCI_CONTROL (VLV_DISPLAY_BASE + 0x650C) +#define PFI_CREDIT_63 (9 << 28)/* chv only */ +#define PFI_CREDIT_31 (8 << 28)/* chv only */ +#define PFI_CREDIT (x) (((x) - 8) << 28)/* 8-15 */ +#define PFI_CREDIT_RESEND (1 << 27) +#define VGA_FAST_MODE_DISABLE (1 << 14) +#define GMBUSFREQ_VLV (VLV_DISPLAY_BASE + 0x6510)/* drivers/gpu/drm/i915/intel_display.c +2
-0@@ -4987,6 +4987,37 @@ static void valleyview_modeset_global_pipes(struct drm_device *dev, *prepare_pipes |= (1 << intel_crtc->pipe); } +static void vlv_program_pfi_credits (struct drm_i915_private *dev_priv) +{drivers/gpu/drm/i915/intel_display.c static void valleyview_modeset_global_pipes(struct drm_device *dev, · line 5001
Quoted 10 lines
drivers/gpu/drm/i915/intel_display.c +10
-0+unsigned int credits; + +if (DIV_ROUND_CLOSEST (dev_priv->vlv_cdclk_freq,1000 ) >= dev_priv->rps.cz_freq) { +/* CHV suggested value is 31 or 63 */ +if (IS_CHERRYVIEW (dev_priv)) + credits =PFI_CREDIT_31 ; +else + credits =PFI_CREDIT (15 ); + }else { + credits =PFI_CREDIT (8 );The default value should be 4 credits for CHV and 0 for VLV.
Quoted 10 lines
drivers/gpu/drm/i915/intel_display.c static void valleyview_modeset_global_pipes(struct drm_device *dev, · line 5009
Quoted 8 lines
drivers/gpu/drm/i915/intel_display.c +8
-0+ } + +/* +* WA - write default credits before re-programming +* FIXME: should we also set the resend bit here? +*/ +I915_WRITE (GCI_CONTROL ,VGA_FAST_MODE_DISABLE | +PFI_CREDIT (8 ));Default credit should be 4 credits for CHV.
PFI_CREDIT(12). Document update is pending. But this is the latest recommendation to windows team.
BTW do you have any specific information about this workaround? I asked Vandana about it when she first submitted the patch and she said she'd get back to me on that, but I don't think I ever got an actual answer. The FIXMEs in particular would need to be answered.
Also if we still need this workaround on CHV, I don't know if we should set the credits to 8 or 12 here. Any ideas?
Quoted 32 lines
Thanks,
VijayQuoted 15 lines
drivers/gpu/drm/i915/intel_display.c +11
-0+ +I915_WRITE (GCI_CONTROL ,VGA_FAST_MODE_DISABLE | + credits |PFI_CREDIT_RESEND ); + +/* +* FIXME is this guaranteed to clear +* immediately or should we poll for it? +*/ +WARN_ON (I915_READ (GCI_CONTROL ) &PFI_CREDIT_RESEND ); +} +static void valleyview_modeset_global_resources (struct drm_device *dev) {struct drm_i915_private *dev_priv = dev->dev_private;drivers/gpu/drm/i915/intel_display.c static void valleyview_modeset_global_resources(struct drm_device *dev) · line 5048
Quoted 8 lines
drivers/gpu/drm/i915/intel_display.c +2
-0@@ -5010,6 +5041,8 @@ static void valleyview_modeset_global_resources(struct drm_device *dev)else valleyview_set_cdclk (dev, req_cdclk); +vlv_program_pfi_credits (dev_priv); +intel_display_power_put (dev_priv,POWER_DOMAIN_PIPE_A ); } }_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Signature · 6 lines
Ville Syrjälä Intel OTC _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 12/12 drm/i915: Enable the maxfifo PM5 mode when appropriate on CHV
In reply to [email protected]From: Ville Syrjälä <[email protected]>
CHV has a new knob in Punit to select between some memory power savings modes PM2 and PM5. We can allow the deeper PM5 when maxfifo mode is enabled, so let's do so in the hopes for moar power savings.
--- drivers/gpu/drm/i915/i915_reg.h | 3 +++ drivers/gpu/drm/i915/intel_pm.c | 13 ++++++++++++- 2 files changed, 15 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/i915_reg.h +3 -0
@@ -552,6 +552,9 @@#define DSPFREQSTAT_MASK (0x3 << DSPFREQSTAT_SHIFT)#define DSPFREQGUAR_SHIFT 14#define DSPFREQGUAR_MASK (0x3 << DSPFREQGUAR_SHIFT) +#define DSP_MAXFIFO_PM5_STATUS (1 << 22)/* chv */ +#define DSP_AUTO_CDCLK_GATE_DISABLE (1 << 7)/* chv */ +#define DSP_MAXFIFO_PM5_ENABLE (1 << 6)/* chv */ #define _DP_SSC (val, pipe) ((val) << (2 * (pipe)))#define DP_SSC_MASK (pipe) _DP_SSC(0x3, (pipe))#define DP_SSC_PWR_ON (pipe) _DP_SSC(0x0, (pipe))
drivers/gpu/drm/i915/intel_pm.c +12 -1
@@ -240,7 +240,18 @@ void intel_set_memory_cxsr(struct drm_i915_private *dev_priv, bool enable)struct drm_device *dev = dev_priv->dev;u32 val; -if (IS_VALLEYVIEW (dev)) { +if (IS_CHERRYVIEW (dev)) { +I915_WRITE (FW_BLC_SELF_VLV , enable ?FW_CSPWRDWNEN :0 ); + +mutex_lock (&dev_priv->rps.hw_lock); + val =vlv_punit_read (dev_priv,PUNIT_REG_DSPFREQ ); +if (enable) + val |=DSP_MAXFIFO_PM5_ENABLE ; +else + val &= ~DSP_MAXFIFO_PM5_ENABLE ; +vlv_punit_write (dev_priv,PUNIT_REG_DSPFREQ , val); +mutex_unlock (&dev_priv->rps.hw_lock); + }else if (IS_VALLEYVIEW (dev)) {I915_WRITE (FW_BLC_SELF_VLV , enable ?FW_CSPWRDWNEN :0 ); }else if (IS_G4X (dev) ||IS_CRESTLINE (dev)) {I915_WRITE (FW_BLC_SELF , enable ?FW_BLC_SELF_EN :0 );
Signature · 6 lines
2.0.5 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 12/12] drm/i915: Enable the maxfifo PM5 mode when appropriate on CHV
Task id: 5748 -------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
PNV +3 275/283 278/283 ILK +1-2 310/315 309/315 SNB +3 320/346 323/346
IVB -1 380/384 379/384
BYT 296/296 296/296
HSW +3 422/428 425/428
BDW 318/333 318/333
-------------------------------------Detailed-------------------------------------
Platform Test drm-intel-nightly Series Applied
PNV igt_gem_userptr_blits_coherency-sync CRASH(3, M7)PASS(2, M7) PASS(1, M7) PNV igt_gem_userptr_blits_coherency-unsync CRASH(3, M7)PASS(3, M7) PASS(1, M7) PNV igt_gem_userptr_blits_create-destroy-sync NRUN(1, M7)PASS(5, M7) PASS(1, M7) PNV igt_gen3_render_tiledx_blits FAIL(2, M7)TIMEOUT(1, M7)PASS(3, M7) FAIL(1, M7) ILK igt_gem_fenced_exec_thrash_no-spare-fences-busy-interruptible DMESG_WARN(1, M26)PASS(1, M26) DMESG_WARN(1, M26) *ILK igt_gem_unfence_active_buffers PASS(3, M26) DMESG_WARN(1, M26) *ILK igt_drv_suspend_forcewake DMESG_WARN(3, M26) PASS(1, M26) *SNB igt_kms_flip_bo-too-big BLACKLIST(1, M35) PASS(1, M35) *SNB igt_kms_flip_bo-too-big-interruptible BLACKLIST(1, M35) PASS(1, M35) *SNB igt_kms_flip_event_leak NSPT(5, M35) PASS(1, M35) IVB igt_gem_storedw_batches_loop_normal DMESG_WARN(1, M4)PASS(4, M4) DMESG_WARN(1, M4) *HSW igt_kms_flip_bo-too-big BLACKLIST(1, M40) PASS(1, M40) *HSW igt_kms_flip_bo-too-big-interruptible BLACKLIST(1, M40) PASS(1, M40) HSW igt_kms_flip_plain-flip-fb-recreate-interruptible TIMEOUT(5, M40)PASS(2, M40) PASS(1, M40)
Note: You need to pay more attention to line start with '*'
_______________________________________________
Intel-gfx mailing list [email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v2 12/12 drm/i915: Enable the maxfifo PM5 mode when appropriate on CHV
In reply to [email protected]From: Ville Syrjälä <[email protected]>
CHV has a new knob in Punit to select between some memory power savings modes PM2 and PM5. We can allow the deeper PM5 when maxfifo mode is enabled, so let's do so in the hopes for moar power savings.
v2: Put the thing into a separate function to avoid churn later
--- drivers/gpu/drm/i915/i915_reg.h | 3 +++ drivers/gpu/drm/i915/intel_pm.c | 19 ++++++++++++++++++- 2 files changed, 21 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/i915_reg.h +3 -0
@@ -552,6 +552,9 @@#define DSPFREQSTAT_MASK (0x3 << DSPFREQSTAT_SHIFT)#define DSPFREQGUAR_SHIFT 14#define DSPFREQGUAR_MASK (0x3 << DSPFREQGUAR_SHIFT) +#define DSP_MAXFIFO_PM5_STATUS (1 << 22)/* chv */ +#define DSP_AUTO_CDCLK_GATE_DISABLE (1 << 7)/* chv */ +#define DSP_MAXFIFO_PM5_ENABLE (1 << 6)/* chv */ #define _DP_SSC (val, pipe) ((val) << (2 * (pipe)))#define DP_SSC_MASK (pipe) _DP_SSC(0x3, (pipe))#define DP_SSC_PWR_ON (pipe) _DP_SSC(0x0, (pipe))
drivers/gpu/drm/i915/intel_pm.c +18 -1
@@ -235,13 +235,30 @@ static const struct cxsr_latency *intel_get_cxsr_latency(int is_desktop,return NULL ; } +static void chv_set_memory_pm5 (struct drm_i915_private *dev_priv,bool enable) +{ +u32 val; + +mutex_lock (&dev_priv->rps.hw_lock); + + val =vlv_punit_read (dev_priv,PUNIT_REG_DSPFREQ ); +if (enable) + val |=DSP_MAXFIFO_PM5_ENABLE ; +else + val &= ~DSP_MAXFIFO_PM5_ENABLE ; +vlv_punit_write (dev_priv,PUNIT_REG_DSPFREQ , val); + +mutex_unlock (&dev_priv->rps.hw_lock); +} +void intel_set_memory_cxsr (struct drm_i915_private *dev_priv,bool enable) {struct drm_device *dev = dev_priv->dev;u32 val; -if (IS_VALLEYVIEW (dev)) { +if (IS_CHERRYVIEW (dev)) {I915_WRITE (FW_BLC_SELF_VLV , enable ?FW_CSPWRDWNEN :0 ); +chv_set_memory_pm5 (dev_priv, enable); }else if (IS_G4X (dev) ||IS_CRESTLINE (dev)) {I915_WRITE (FW_BLC_SELF , enable ?FW_BLC_SELF_EN :0 ); }else if (IS_PINEVIEW (dev)) {
Signature · 6 lines
2.0.5 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 12/12] drm/i915: Enable the maxfifo PM5 mode when appropriate on CHV
In reply to [email protected]Quoted 40 lines · On 2/10/2015 6:58 PM, [email protected] wrote:
From: Ville Syrjälä <[email protected]>
CHV has a new knob in Punit to select between some memory power savings modes PM2 and PM5. We can allow the deeper PM5 when maxfifo mode is enabled, so let's do so in the hopes for moar power savings.
Signed-off-by Ville Syrjälä <[email protected]>--- drivers/gpu/drm/i915/i915_reg.h | 3 +++ drivers/gpu/drm/i915/intel_pm.c | 13 ++++++++++++- 2 files changed, 15 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/i915_reg.h +3
-0@@ -552,6 +552,9 @@#define DSPFREQSTAT_MASK (0x3 << DSPFREQSTAT_SHIFT)#define DSPFREQGUAR_SHIFT 14#define DSPFREQGUAR_MASK (0x3 << DSPFREQGUAR_SHIFT) +#define DSP_MAXFIFO_PM5_STATUS (1 << 22)/* chv */ +#define DSP_AUTO_CDCLK_GATE_DISABLE (1 << 7)/* chv */ +#define DSP_MAXFIFO_PM5_ENABLE (1 << 6)/* chv */ #define _DP_SSC (val, pipe) ((val) << (2 * (pipe)))#define DP_SSC_MASK (pipe) _DP_SSC(0x3, (pipe))#define DP_SSC_PWR_ON (pipe) _DP_SSC(0x0, (pipe))drivers/gpu/drm/i915/intel_pm.c +5
-1@@ -240,7 +240,18 @@ void intel_set_memory_cxsr(struct drm_i915_private *dev_priv, bool enable)struct drm_device *dev = dev_priv->dev;u32 val; -if (IS_VALLEYVIEW (dev)) { +if (IS_CHERRYVIEW (dev)) { +I915_WRITE (FW_BLC_SELF_VLV , enable ?FW_CSPWRDWNEN :0 ); + +mutex_lock (&dev_priv->rps.hw_lock); + val =vlv_punit_read (dev_priv,PUNIT_REG_DSPFREQ );
drivers/gpu/drm/i915/intel_pm.c void intel_set_memory_cxsr(struct drm_i915_private *dev_priv, bool enable) · line 257
Quoted 10 lines
drivers/gpu/drm/i915/intel_pm.c +7
-0+if (enable) + val |=DSP_MAXFIFO_PM5_ENABLE ; +else + val &= ~DSP_MAXFIFO_PM5_ENABLE ; +vlv_punit_write (dev_priv,PUNIT_REG_DSPFREQ , val); +mutex_unlock (&dev_priv->rps.hw_lock); + }else if (IS_VALLEYVIEW (dev)) {I915_WRITE (FW_BLC_SELF_VLV , enable ?FW_CSPWRDWNEN :0 ); }else if (IS_G4X (dev) ||IS_CRESTLINE (dev)) {I915_WRITE (FW_BLC_SELF , enable ?FW_BLC_SELF_EN :0 );
Since you are enabling MaxFIFO for multi plane in one of the previous patches, i guess PM5 will also be enabled when more than one plane is active in this flow. Let's enable MaxFIFO and PM5 when only one plane is active for now. This is the only validated scenario by SV.
With this addressed,
Thanks,
Vijay
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 12/12] drm/i915: Enable the maxfifo PM5 mode when appropriate on CHV
Quoted 48 lines · Vijay A
Quoted 47 lines · On 2/10/2015 6:58 PM, [email protected] wrote:
From: Ville Syrjälä <[email protected]>
CHV has a new knob in Punit to select between some memory power savings modes PM2 and PM5. We can allow the deeper PM5 when maxfifo mode is enabled, so let's do so in the hopes for moar power savings.
Signed-off-by Ville Syrjälä <[email protected]>--- drivers/gpu/drm/i915/i915_reg.h | 3 +++ drivers/gpu/drm/i915/intel_pm.c | 13 ++++++++++++- 2 files changed, 15 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/i915_reg.h +3
-0@@ -552,6 +552,9 @@#define DSPFREQSTAT_MASK (0x3 << DSPFREQSTAT_SHIFT)#define DSPFREQGUAR_SHIFT 14#define DSPFREQGUAR_MASK (0x3 << DSPFREQGUAR_SHIFT) +#define DSP_MAXFIFO_PM5_STATUS (1 << 22)/* chv */ +#define DSP_AUTO_CDCLK_GATE_DISABLE (1 << 7)/* chv */ +#define DSP_MAXFIFO_PM5_ENABLE (1 << 6)/* chv */ #define _DP_SSC (val, pipe) ((val) << (2 * (pipe)))#define DP_SSC_MASK (pipe) _DP_SSC(0x3, (pipe))#define DP_SSC_PWR_ON (pipe) _DP_SSC(0x0, (pipe))drivers/gpu/drm/i915/intel_pm.c +12
-1@@ -240,7 +240,18 @@ void intel_set_memory_cxsr(struct drm_i915_private *dev_priv, bool enable)struct drm_device *dev = dev_priv->dev;u32 val; -if (IS_VALLEYVIEW (dev)) { +if (IS_CHERRYVIEW (dev)) { +I915_WRITE (FW_BLC_SELF_VLV , enable ?FW_CSPWRDWNEN :0 ); + +mutex_lock (&dev_priv->rps.hw_lock); + val =vlv_punit_read (dev_priv,PUNIT_REG_DSPFREQ ); +if (enable) + val |=DSP_MAXFIFO_PM5_ENABLE ; +else + val &= ~DSP_MAXFIFO_PM5_ENABLE ; +vlv_punit_write (dev_priv,PUNIT_REG_DSPFREQ , val); +mutex_unlock (&dev_priv->rps.hw_lock); + }else if (IS_VALLEYVIEW (dev)) {
Quoted 8 lines
drivers/gpu/drm/i915/intel_pm.c void intel_set_memory_cxsr(struct drm_i915_private *dev_priv, bool enable) · line 257
Quoted 3 lines
drivers/gpu/drm/i915/intel_pm.c +0
-0I915_WRITE (FW_BLC_SELF_VLV , enable ?FW_CSPWRDWNEN :0 ); }else if (IS_G4X (dev) ||IS_CRESTLINE (dev)) {I915_WRITE (FW_BLC_SELF , enable ?FW_BLC_SELF_EN :0 );Since you are enabling MaxFIFO for multi plane in one of the previous patches, i guess PM5 will also be enabled when more than one plane is active in this flow.
Let's enable MaxFIFO and PM5 when only one plane is active for now. This is the only validated scenario by SV.
Yep that's good enough for me.
Quoted 12 lines
With this addressed,
Reviewed-by Vijay Purushothaman <[email protected]>Thanks,
Vijay_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Signature · 6 lines
Ville Syrjälä Intel OTC _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx