Couple of patches on top of the SKL latency retrieval
Subsystems (2)
cover Couple of patches on top of the SKL latency retrieval
Ville had 2 comments on the SKL memory latency patch that are better addressed as separate patches on top.
Patch 1: SKL unifies the plane hw and their latencies to fech data from memory is identical. So SKL only needs a single array. We save some room by using anymous union/structs. However, last time I tried that (shared DPLL state), Daniel didn't like it. So separate that into its own patch so it can be easily rejected.
Patch 2: While it shouldn't cause any harm and DATA1 is likely unused by the pcode firmware, we don't actually know. So it's better to have as a separate patch, just in case a revert is needed (for testing or otherwise).
Signature · 14 lines
Damien
Damien Lespiau (2):
drm/i915: Use anonymous union/struct to save space taken by latency
values
drm/i915: Clear PCODE_DATA1 on SNB+
drivers/gpu/drm/i915/i915_drv.h | 38 +++++++++++++++++++++-----------------
drivers/gpu/drm/i915/i915_reg.h | 2 +-
drivers/gpu/drm/i915/intel_pm.c | 3 +--
3 files changed, 23 insertions(+), 20 deletions(-)
--
1.8.3.1PATCH 1/2 drm/i915: Use anonymous union/struct to save space taken by latency values
--- drivers/gpu/drm/i915/i915_drv.h | 38 +++++++++++++++++++++----------------- 1 file changed, 21 insertions(+), 17 deletions(-)
drivers/gpu/drm/i915/i915_drv.h +21 -17
@@ -1730,23 +1730,27 @@ struct drm_i915_private {struct vlv_s0ix_state vlv_s0ix_state;struct { -/* -* Raw watermark latency values: -* in 0.1us units for WM0, -* in 0.5us units for WM1+. -*/ -/* primary */ -uint16_t pri_latency[5 ]; -/* sprite */ -uint16_t spr_latency[5 ]; -/* cursor */ -uint16_t cur_latency[5 ]; -/* -* Raw watermark memory latency values -* for SKL for all 8 levels -* in 1us units. -*/ -uint16_t skl_latency[8 ]; +union { +/* +* Raw watermark latency values: +* in 0.1us units for WM0, +* in 0.5us units for WM1+. +*/ +struct { +/* primary */ +uint16_t pri_latency[5 ]; +/* sprite */ +uint16_t spr_latency[5 ]; +/* cursor */ +uint16_t cur_latency[5 ]; + }; + +/* +* Raw watermark memory latency values for SKL for all +* 8 levels. In 1us units. +*/ +uint16_t skl_latency[8 ]; + };/* * The skl_wm_values structure is a bit too big for stack
Signature · 6 lines
1.8.3.1 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 1/2] drm/i915: Use anonymous union/struct to save space taken by latency values
Quoted 2 lines · Damien Lespiau
Suggested-by Ville Syrjälä <[email protected]>Signed-off-by Damien Lespiau <[email protected]>
I think I'll punt on reviewing this for now. I need to go through the other skl wm stuff first, and then I probaly need to stare at the result a bit before I can think about unification.
Quoted 55 lines
--- drivers/gpu/drm/i915/i915_drv.h | 38 +++++++++++++++++++++----------------- 1 file changed, 21 insertions(+), 17 deletions(-)drivers/gpu/drm/i915/i915_drv.h +21
-17@@ -1730,23 +1730,27 @@ struct drm_i915_private {struct vlv_s0ix_state vlv_s0ix_state;struct { -/* -* Raw watermark latency values: -* in 0.1us units for WM0, -* in 0.5us units for WM1+. -*/ -/* primary */ -uint16_t pri_latency[5 ]; -/* sprite */ -uint16_t spr_latency[5 ]; -/* cursor */ -uint16_t cur_latency[5 ]; -/* -* Raw watermark memory latency values -* for SKL for all 8 levels -* in 1us units. -*/ -uint16_t skl_latency[8 ]; +union { +/* +* Raw watermark latency values: +* in 0.1us units for WM0, +* in 0.5us units for WM1+. +*/ +struct { +/* primary */ +uint16_t pri_latency[5 ]; +/* sprite */ +uint16_t spr_latency[5 ]; +/* cursor */ +uint16_t cur_latency[5 ]; + }; + +/* +* Raw watermark memory latency values for SKL for all +* 8 levels. In 1us units. +*/ +uint16_t skl_latency[8 ]; + };/* * The skl_wm_values structure is a bit too big for stack Signature · 1 line
1.8.3.1
Signature · 2 lines
Ville Syrjälä Intel OTC
PATCH 2/2 drm/i915: Clear PCODE_DATA1 on SNB+
In reply to Damien LespiauVille found out that the DATA1 register exists since SNB with some scarce apparitions in the specs throughout the times. In his own words:
Also according to Bspec the mailbox data1 register already existed since snb. The hsw cdclk change sequence also mentions that it should be set to 0, but eg. the bdw IPS sequence doesn't mention it. I guess in theory some pcode command might cause it to be clobbered, so I'm thinking we should just explicitly set it to 0 for all platforms in the pcode read/write functions
--- drivers/gpu/drm/i915/i915_reg.h | 2 +- drivers/gpu/drm/i915/intel_pm.c | 3 +-- 2 files changed, 2 insertions(+), 3 deletions(-)
drivers/gpu/drm/i915/i915_reg.h +1 -1
@@ -5952,8 +5952,8 @@ enum skl_disp_power_wells {#define GEN6_PCODE_DATA 0x138128#define GEN6_PCODE_FREQ_IA_RATIO_SHIFT 8#define GEN6_PCODE_FREQ_RING_RATIO_SHIFT 16 +#define GEN6_PCODE_DATA1 0x13812C -#define GEN9_PCODE_DATA1 0x13812C#define GEN9_PCODE_READ_MEM_LATENCY 0x6#define GEN9_MEM_LATENCY_LEVEL_MASK 0xFF#define GEN9_MEM_LATENCY_LEVEL_1_5_SHIFT 8
drivers/gpu/drm/i915/intel_pm.c +1 -2
@@ -8716,8 +8716,7 @@ int sandybridge_pcode_read(struct drm_i915_private *dev_priv, u8 mbox, u32 *val) }I915_WRITE (GEN6_PCODE_DATA , *val); -if (INTEL_INFO (dev_priv)->gen >=9 ) -I915_WRITE (GEN9_PCODE_DATA1 ,0 ); +I915_WRITE (GEN6_PCODE_DATA1 ,0 );I915_WRITE (GEN6_PCODE_MAILBOX ,GEN6_PCODE_READY | mbox); if (wait_for((I915_READ(GEN6_PCODE_MAILBOX) & GEN6_PCODE_READY) == 0,
Signature · 6 lines
1.8.3.1 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 2/2] drm/i915: Clear PCODE_DATA1 on SNB+
Quoted 10 lines · Damien Lespiau
Ville found out that the DATA1 register exists since SNB with some scarce apparitions in the specs throughout the times. In his own words:
Also according to Bspec the mailbox data1 register already existed since snb. The hsw cdclk change sequence also mentions that it should be set to 0, but eg. the bdw IPS sequence doesn't mention it. I guess in theory some pcode command might cause it to be clobbered, so I'm thinking we should just explicitly set it to 0 for all platforms in the pcode read/write functions
Quoted 2 lines
Suggested-by Ville Syrjälä <[email protected]>Signed-off-by Damien Lespiau <[email protected]>
Quoted 35 lines
--- drivers/gpu/drm/i915/i915_reg.h | 2 +- drivers/gpu/drm/i915/intel_pm.c | 3 +-- 2 files changed, 2 insertions(+), 3 deletions(-)drivers/gpu/drm/i915/i915_reg.h +1
-1@@ -5952,8 +5952,8 @@ enum skl_disp_power_wells {#define GEN6_PCODE_DATA 0x138128#define GEN6_PCODE_FREQ_IA_RATIO_SHIFT 8#define GEN6_PCODE_FREQ_RING_RATIO_SHIFT 16 +#define GEN6_PCODE_DATA1 0x13812C -#define GEN9_PCODE_DATA1 0x13812C#define GEN9_PCODE_READ_MEM_LATENCY 0x6#define GEN9_MEM_LATENCY_LEVEL_MASK 0xFF#define GEN9_MEM_LATENCY_LEVEL_1_5_SHIFT 8drivers/gpu/drm/i915/intel_pm.c +1
-2@@ -8716,8 +8716,7 @@ int sandybridge_pcode_read(struct drm_i915_private *dev_priv, u8 mbox, u32 *val) }I915_WRITE (GEN6_PCODE_DATA , *val); -if (INTEL_INFO (dev_priv)->gen >=9 ) -I915_WRITE (GEN9_PCODE_DATA1 ,0 ); +I915_WRITE (GEN6_PCODE_DATA1 ,0 );I915_WRITE (GEN6_PCODE_MAILBOX ,GEN6_PCODE_READY | mbox); if (wait_for((I915_READ(GEN6_PCODE_MAILBOX) & GEN6_PCODE_READY) == 0,Signature · 1 line
1.8.3.1
Signature · 2 lines
Ville Syrjälä Intel OTC
just a warn/heads-up: I had listed this one for -collector but got a conflict because skl latency retrieval didn't get merged yet.
Quoted 33 lines · Damien Lespiau
Ville had 2 comments on the SKL memory latency patch that are better addressed as separate patches on top.
Patch 1: SKL unifies the plane hw and their latencies to fech data from memory is identical. So SKL only needs a single array. We save some room by using anymous union/structs. However, last time I tried that (shared DPLL state), Daniel didn't like it. So separate that into its own patch so it can be easily rejected.
Patch 2: While it shouldn't cause any harm and DATA1 is likely unused by the pcode firmware, we don't actually know. So it's better to have as a separate patch, just in case a revert is needed (for testing or otherwise).
--
DamienDamien Lespiau (2):
drm/i915: Use anonymous union/struct to save space taken by latency
values
drm/i915: ClearPCODE_DATA1on SNB+drivers/gpu/drm/i915/i915_drv.h | 38 +++++++++++++++++++++----------------- drivers/gpu/drm/i915/i915_reg.h | 2 +- drivers/gpu/drm/i915/intel_pm.c | 3 +-- 3 files changed, 23 insertions(+), 20 deletions(-)--
1.8.3.1_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Signature · 6 lines
Rodrigo Vivi Blog: http://blog.vivi.eng.br _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 2 lines · Rodrigo Vivi
just a warn/heads-up: I had listed this one for -collector but got a conflict because skl latency retrieval didn't get merged yet.
I carry those in my SKL branch and will resend them as part of stage1 upstreaming, I think you can drop them from -collector.
Signature · 5 lines
Damien _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx