A few cursor fixups after the multi-size patches
Subsystems (2)
cover A few cursor fixups after the multi-size patches
Noticed that, if I'm not mistaken, we were misunderstanding the intention of mode_config.cursor_{width,height}, and those 3 patches are the resulting fixes.
Damien Lespiau (3):
drm/i915: Don't set mode_config's cursor size drm/i915: Remove max_cursor_{width,height} from the crtc drm/i915: Use the actual cursor width for WM computation
drivers/gpu/drm/i915/intel_display.c | 10 ---------- drivers/gpu/drm/i915/intel_drv.h | 7 ------- drivers/gpu/drm/i915/intel_pm.c | 2 +- 3 files changed, 1 insertion(+), 18 deletions(-)
Signature · 1 line
1.8.3.1
PATCH 1/3 drm/i915: Don't set mode_config's cursor size
Those fields are supposed to be a good default value for the cursor size, intended for the case where the hardware doesn't support 64x64 cursors, for use with a hw agnostic DDX driver for instance.
We're fine with 64x64 cursors though and don't need to set those fields (DRM core will return 64 is we don't). If we declare 256x256, that generic driver will use a big buffer for the cursor, without any good reason.
--- drivers/gpu/drm/i915/intel_display.c | 2 -- 1 file changed, 2 deletions(-)
drivers/gpu/drm/i915/intel_display.c +0 -2
@@ -10557,8 +10557,6 @@ static void intel_crtc_init(struct drm_device *dev, int pipe) intel_crtc->max_cursor_width =CURSOR_WIDTH ; intel_crtc->max_cursor_height =CURSOR_HEIGHT ; } - dev->mode_config.cursor_width = intel_crtc->max_cursor_width; - dev->mode_config.cursor_height = intel_crtc->max_cursor_height;drm_mode_crtc_set_gamma_size (&intel_crtc->base,256 );for (i =0 ; i <256 ; i++) {
Signature · 1 line
1.8.3.1
Re: [PATCH 1/3] drm/i915: Don't set mode_config's cursor size
Quoted 8 lines · Damien Lespiau
Those fields are supposed to be a good default value for the cursor size, intended for the case where the hardware doesn't support 64x64 cursors, for use with a hw agnostic DDX driver for instance.
We're fine with 64x64 cursors though and don't need to set those fields (DRM core will return 64 is we don't). If we declare 256x256, that generic driver will use a big buffer for the cursor, without any good reason.
How does userspace now know that 256x256 cursors are support for HiDPI? -Chris
Signature · 1 line
Chris Wilson, Intel Open Source Technology Centre
Re: [PATCH 1/3] drm/i915: Don't set mode_config's cursor size
Quoted 11 lines · Chris Wilson
Quoted 8 lines · Damien Lespiau
Those fields are supposed to be a good default value for the cursor size, intended for the case where the hardware doesn't support 64x64 cursors, for use with a hw agnostic DDX driver for instance.
We're fine with 64x64 cursors though and don't need to set those fields (DRM core will return 64 is we don't). If we declare 256x256, that generic driver will use a big buffer for the cursor, without any good reason.
How does userspace now know that 256x256 cursors are support for HiDPI?
It doesn't currently? a property on the cursor plane with the list of supported formats in the brave new full drm_plane world seems like a good option to me.
Signature · 1 line
Damien
Re: [PATCH 1/3] drm/i915: Don't set mode_config's cursor size
Quoted 11 lines · Damien Lespiau
Quoted 10 lines · Chris Wilson
Quoted 8 lines · Damien Lespiau
Those fields are supposed to be a good default value for the cursor size, intended for the case where the hardware doesn't support 64x64 cursors, for use with a hw agnostic DDX driver for instance.
We're fine with 64x64 cursors though and don't need to set those fields (DRM core will return 64 is we don't). If we declare 256x256, that generic driver will use a big buffer for the cursor, without any good reason.
Quoted 5 lines
Quoted 1 line
How does userspace now know that 256x256 cursors are support for HiDPI?
It doesn't currently? a property on the cursor plane with the list of supported formats in the brave new full
drm_planeworld seems like a good option to me.
Userspace currently uses this method to determine the largest cursor supported by the driver. That userspace is inept at resize the cursor bo as required is a probably that won't be solved by simply exposing it later.
-Chris
Signature · 1 line
Chris Wilson, Intel Open Source Technology Centre
Re: [PATCH 1/3] drm/i915: Don't set mode_config's cursor size
Quoted 14 lines · Chris Wilson
Quoted 13 lines · Damien Lespiau
Quoted 11 lines · Chris Wilson
Quoted 8 lines · Damien Lespiau
Those fields are supposed to be a good default value for the cursor size, intended for the case where the hardware doesn't support 64x64 cursors, for use with a hw agnostic DDX driver for instance.
We're fine with 64x64 cursors though and don't need to set those fields (DRM core will return 64 is we don't). If we declare 256x256, that generic driver will use a big buffer for the cursor, without any good reason.
How does userspace now know that 256x256 cursors are support for HiDPI?
Quoted 8 lines
Quoted 3 lines
It doesn't currently? a property on the cursor plane with the list of supported formats in the brave new full
drm_planeworld seems like a good option to me.Userspace currently uses this method to determine the largest cursor supported by the driver. That userspace is inept at resize the cursor bo as required is a probably that won't be solved by simply exposing it later.
That doesn't seem to be the intention of the original patch?
http://lists.freedesktop.org/archives/dri-devel/2014-February/053770.html
Are you saying the Intel DDX currently derives a different meaning to the intented behaviour? in which case it can still be changed to not do that?
Signature · 1 line
Damien
Re: [PATCH 1/3] drm/i915: Don't set mode_config's cursor size
Quoted 19 lines · Damien Lespiau
Quoted 18 lines · Chris Wilson
Quoted 16 lines · Damien Lespiau
Quoted 11 lines · Chris Wilson
Quoted 8 lines · Damien Lespiau
Those fields are supposed to be a good default value for the cursor size, intended for the case where the hardware doesn't support 64x64 cursors, for use with a hw agnostic DDX driver for instance.
We're fine with 64x64 cursors though and don't need to set those fields (DRM core will return 64 is we don't). If we declare 256x256, that generic driver will use a big buffer for the cursor, without any good reason.
How does userspace now know that 256x256 cursors are support for HiDPI?
It doesn't currently? a property on the cursor plane with the list of supported formats in the brave new full
drm_planeworld seems like a good option to me.
Quoted 8 lines
Quoted 4 lines
Userspace currently uses this method to determine the largest cursor supported by the driver. That userspace is inept at resize the cursor bo as required is a probably that won't be solved by simply exposing it later.
That doesn't seem to be the intention of the original patch?
http://lists.freedesktop.org/archives/dri-devel/2014-February/053770.html
For the record,
16:30 < agd5f> ickle, our GPUs don't have selectable cursor sizes 16:31 < agd5f> so on the newer ones, xf86-video-modesetting, etc. would allocate a 64x64 cursor and it would look squashed and funky since the hw expects 128x128
Which means I was confused when I thought part of the reasoning was indeed HiDPI support. (I'm still seem to remember that was part of the argument for large cursors anyway.)
Quoted 3 lines
Are you saying the Intel DDX currently derives a different meaning to the intented behaviour? in which case it can still be changed to not do that?
I still disagree though. This provides all the information I need to support variable sized cursors and we can use large cursors today. -Chris
Signature · 1 line
Chris Wilson, Intel Open Source Technology Centre
Re: [PATCH 1/3] drm/i915: Don't set mode_config's cursor size
Quoted 11 lines · Chris Wilson
For the record,
16:30 < agd5f> ickle, our GPUs don't have selectable cursor sizes 16:31 < agd5f> so on the newer ones, xf86-video-modesetting, etc. would allocate a 64x64 cursor and it would look squashed and funky since the hw expects 128x128
Which means I was confused when I thought part of the reasoning was indeed HiDPI support. (I'm still seem to remember that was part of the argument for large cursors anyway.)
Quoted 6 lines
Quoted 3 lines
Are you saying the Intel DDX currently derives a different meaning to the intented behaviour? in which case it can still be changed to not do that?
I still disagree though. This provides all the information I need to support variable sized cursors and we can use large cursors today.
I'd love the game to be about defining clear semantics more than "by interpreting that value this way, I got what I always wanted" :)
We can resolve that today with MAX_CURSOR_WIDTH, MAX_CURSOR_HEIGHT caps as well (if you're alluding at the fact that drm_planes may still be a few decades away).
We'll still need to expose the full list of supported cursor sizes for compositors at some point or another, my preferred way would be with a property in the exposed cursor drm_plane.
Signature · 1 line
Damien
Re: [PATCH 1/3] drm/i915: Don't set mode_config's cursor size
Quoted 22 lines · Damien Lespiau
Quoted 11 lines · Chris Wilson
For the record,
16:30 < agd5f> ickle, our GPUs don't have selectable cursor sizes 16:31 < agd5f> so on the newer ones, xf86-video-modesetting, etc. would allocate a 64x64 cursor and it would look squashed and funky since the hw expects 128x128
Which means I was confused when I thought part of the reasoning was indeed HiDPI support. (I'm still seem to remember that was part of the argument for large cursors anyway.)
Quoted 6 lines
Quoted 3 lines
Are you saying the Intel DDX currently derives a different meaning to the intented behaviour? in which case it can still be changed to not do that?
I still disagree though. This provides all the information I need to support variable sized cursors and we can use large cursors today.
I'd love the game to be about defining clear semantics more than "by interpreting that value this way, I got what I always wanted" :)
Quoted 7 lines
We can resolve that today with
MAX_CURSOR_WIDTH,MAX_CURSOR_HEIGHTcaps as well (if you're alluding at the fact thatdrm_planesmay still be a few decades away).We'll still need to expose the full list of supported cursor sizes for compositors at some point or another, my preferred way would be with a property in the exposed cursor
drm_plane.
For the record I'll restate my comment here about the larger problem:
Atm we have no way for userspace to figure out per-plane limits on sizes/strides, we only expose a lists of supported pixel formats.
Imo exposing cursor limits is just part of this larger issue, so if we can get the current stuff working with some legalese, then I'm ok with that. Solving the larger issue is much more work, and it's better to have a few more odd cases working than not. For planes I guess we could have a few limits:
min/max width height in pixels
min/max stride
alignment of stride
And a pile of flags
- needs pot stride/width/height
- needs square size
That should be enough to cover most single-plane things. For multiplanar I guess we might either just need 2nd/3rd set of those or some additional stuff expressed in flags (e.g. subsampled strides must be half of the Y stride). Or we'll throw our hands in the air for multi-planar for now ;-)
Or we simply do this per-pixel format with one for each framebuffer plane, i.e.
struct drm_get_plane_fb_limits {
uint32_t plane_id; /* in */
uint32_t fourcc; /* in */
struct drm_plane_limits limits[MAX_FOURCC_PLANES];
/* the stuff above for all possible planes of a fourcc code */
}Saner drivers could then return the same thing for all fourccs codes in their backend.
Just something to ponder.
Adding dri-devel, maybe we can get this discussion started. -Daniel
Signature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch
Re: [PATCH 1/3] drm/i915: Don't set mode_config's cursor size
Quoted 42 lines · Daniel Vetter
Quoted 22 lines · Damien Lespiau
Quoted 11 lines · Chris Wilson
For the record,
16:30 < agd5f> ickle, our GPUs don't have selectable cursor sizes 16:31 < agd5f> so on the newer ones, xf86-video-modesetting, etc. would allocate a 64x64 cursor and it would look squashed and funky since the hw expects 128x128
Which means I was confused when I thought part of the reasoning was indeed HiDPI support. (I'm still seem to remember that was part of the argument for large cursors anyway.)
Quoted 6 lines
Quoted 3 lines
Are you saying the Intel DDX currently derives a different meaning to the intented behaviour? in which case it can still be changed to not do that?
I still disagree though. This provides all the information I need to support variable sized cursors and we can use large cursors today.
I'd love the game to be about defining clear semantics more than "by interpreting that value this way, I got what I always wanted" :)
Quoted 7 lines
We can resolve that today with
MAX_CURSOR_WIDTH,MAX_CURSOR_HEIGHTcaps as well (if you're alluding at the fact thatdrm_planesmay still be a few decades away).We'll still need to expose the full list of supported cursor sizes for compositors at some point or another, my preferred way would be with a property in the exposed cursor
drm_plane.For the record I'll restate my comment here about the larger problem:
Atm we have no way for userspace to figure out per-plane limits on sizes/strides, we only expose a lists of supported pixel formats.
Imo exposing cursor limits is just part of this larger issue, so if we can get the current stuff working with some legalese, then I'm ok with that. Solving the larger issue is much more work, and it's better to have a few more odd cases working than not. For planes I guess we could have a few limits:
Quoted 7 lines
min/max width height in pixels
min/max stride
alignment of strideAnd a pile of flags
- needs pot stride/width/height
- needs square size
Already new ones:
- stride must match width*bpp
This will be fun if we ever do it ...
-Daniel
Quoted 27 lines
That should be enough to cover most single-plane things. For multiplanar I guess we might either just need 2nd/3rd set of those or some additional stuff expressed in flags (e.g. subsampled strides must be half of the Y stride). Or we'll throw our hands in the air for multi-planar for now ;-)
Or we simply do this per-pixel format with one for each framebuffer plane, i.e.
struct drm_get_plane_fb_limits { uint32_t plane_id; /* in */ uint32_t fourcc; /* in */ struct drm_plane_limits limits[MAX_FOURCC_PLANES]; /* the stuff above for all possible planes of a fourcc code */ }Saner drivers could then return the same thing for all fourccs codes in their backend.
Just something to ponder.
Adding dri-devel, maybe we can get this discussion started. -Daniel
Signature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch
Signature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch
Re: [PATCH 1/3] drm/i915: Don't set mode_config's cursor size
In reply to Daniel VetterQuoted 10 lines · Daniel Vetter
Or we simply do this per-pixel format with one for each framebuffer plane, i.e.
struct drm_get_plane_fb_limits { uint32_t plane_id; /* in */ uint32_t fourcc; /* in */ struct drm_plane_limits limits[MAX_FOURCC_PLANES]; /* the stuff above for all possible planes of a fourcc code */ }
Quoted 2 lines
Saner drivers could then return the same thing for all fourccs codes in their backend.
Some of the limits are definitely per format. Plane max dimensions are a good example of a limit that can change per-format (8bpp Vs 10bpp to be contained within the same max bandwidth of the hw).
Signature · 1 line
Damien
Re: [PATCH 1/3] drm/i915: Don't set mode_config's cursor size
Quoted 11 lines · Damien Lespiau
Quoted 10 lines · Daniel Vetter
Or we simply do this per-pixel format with one for each framebuffer plane, i.e.
struct drm_get_plane_fb_limits { uint32_t plane_id; /* in */ uint32_t fourcc; /* in */ struct drm_plane_limits limits[MAX_FOURCC_PLANES]; /* the stuff above for all possible planes of a fourcc code */ }
Quoted 6 lines
Quoted 2 lines
Saner drivers could then return the same thing for all fourccs codes in their backend.
Some of the limits are definitely per format. Plane max dimensions are a good example of a limit that can change per-format (8bpp Vs 10bpp to be contained within the same max bandwidth of the hw).
One thing I've completely missed btw is scaling limits. How we then need to factor in bandwidth I have no idea about ... I guess at one point it boils down to "try it and give up if it doesn't work". And I think we need a few scaling related flags like "can't scale at all" or sub-sampling restrictions. Who knows ...
-Daniel
Signature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch
Re: [PATCH 1/3] drm/i915: Don't set mode_config's cursor size
In reply to Chris WilsonQuoted 6 lines · Chris Wilson
Quoted 3 lines
Are you saying the Intel DDX currently derives a different meaning to the intented behaviour? in which case it can still be changed to not do that?
I still disagree though. This provides all the information I need to support variable sized cursors and we can use large cursors today.
Note that I won't fight if you find it useful and people are fine with that new meaning. Can we just throw a patch actually documented what you want those values to be?
The WM patch still needs to take the actual cursor size though. Keeping those global limits on the crtc struct still looks weird.
Signature · 1 line
Damien
Re: [PATCH 1/3] drm/i915: Don't set mode_config's cursor size
In reply to Damien LespiauQuoted 11 lines · Damien Lespiau
Quoted 10 lines · Chris Wilson
Quoted 8 lines · Damien Lespiau
Those fields are supposed to be a good default value for the cursor size, intended for the case where the hardware doesn't support 64x64 cursors, for use with a hw agnostic DDX driver for instance.
We're fine with 64x64 cursors though and don't need to set those fields (DRM core will return 64 is we don't). If we declare 256x256, that generic driver will use a big buffer for the cursor, without any good reason.
Quoted 5 lines
Quoted 1 line
How does userspace now know that 256x256 cursors are support for HiDPI?
It doesn't currently? a property on the cursor plane with the list of supported formats in the brave new full
drm_planeworld seems like a good option to me.
How do we handle cursor size cap that was added with
http://lists.freedesktop.org/archives/dri-devel/2014-February/053770.html.
Will change i-g-t kms_cursor_crc accordingly as well since it depends on this cap.
Quoted 1 line
Re: [PATCH 1/3] drm/i915: Don't set mode_config's cursor size
In reply to Damien LespiauQuoted 21 lines · Damien Lespiau
Those fields are supposed to be a good default value for the cursor size, intended for the case where the hardware doesn't support 64x64 cursors, for use with a hw agnostic DDX driver for instance.
We're fine with 64x64 cursors though and don't need to set those fields (DRM core will return 64 is we don't). If we declare 256x256, that generic driver will use a big buffer for the cursor, without any good reason.
Cc Sagar Kamble <[email protected]>Cc Imre Deak <[email protected]>Signed-off-by Damien Lespiau <[email protected]>--- drivers/gpu/drm/i915/intel_display.c | 2 -- 1 file changed, 2 deletions(-)drivers/gpu/drm/i915/intel_display.c +0
-0
drivers/gpu/drm/i915/intel_display.c static void intel_crtc_init(struct drm_device *dev, int pipe) · line 10561
Quoted 5 lines
drivers/gpu/drm/i915/intel_display.c +0
-2@@ -10557,8 +10557,6 @@ static void intel_crtc_init(struct drm_device *dev, int pipe) intel_crtc->max_cursor_width =CURSOR_WIDTH ; intel_crtc->max_cursor_height =CURSOR_HEIGHT ; } - dev->mode_config.cursor_width = intel_crtc->max_cursor_width; - dev->mode_config.cursor_height = intel_crtc->max_cursor_height;
I thought drm_getcap should return the max cursor size, using these two fields.
--Imre
drivers/gpu/drm/i915/intel_display.c static void intel_crtc_init(struct drm_device *dev, int pipe) · line 10562
Quoted 3 lines
drivers/gpu/drm/i915/intel_display.c +0
-0drm_mode_crtc_set_gamma_size (&intel_crtc->base,256 );for (i =0 ; i <256 ; i++) {
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 2/3 drm/i915: Remove max_cursor_{width, height} from the crtc
In reply to Damien LespiauWe don't need them anymore as they were used to initialize DRM's mode_config.
As a side note, it was a bit strange to put them on the CRTC object, they are global values, not specific to a CRTC.
As another side note, those values were only used in that one function, so we didn't need to store them elsewhere.
--- drivers/gpu/drm/i915/intel_display.c | 8 -------- drivers/gpu/drm/i915/intel_drv.h | 7 ------- 2 files changed, 15 deletions(-)
drivers/gpu/drm/i915/intel_display.c +0 -8
@@ -10550,14 +10550,6 @@ static void intel_crtc_init(struct drm_device *dev, int pipe)drm_crtc_init (dev, &intel_crtc->base, &intel_crtc_funcs); -if (IS_GEN2 (dev)) { - intel_crtc->max_cursor_width =GEN2_CURSOR_WIDTH ; - intel_crtc->max_cursor_height =GEN2_CURSOR_HEIGHT ; - }else { - intel_crtc->max_cursor_width =CURSOR_WIDTH ; - intel_crtc->max_cursor_height =CURSOR_HEIGHT ; - } -drm_mode_crtc_set_gamma_size (&intel_crtc->base,256 );for (i =0 ; i <256 ; i++) { intel_crtc->lut_r[i] = i;
drivers/gpu/drm/i915/intel_drv.h +0 -7
@@ -78,12 +78,6 @@#define MAX_OUTPUTS 6/* maximum connectors per crtcs in the mode set */ -/* Maximum cursor sizes */ -#define GEN2_CURSOR_WIDTH 64 -#define GEN2_CURSOR_HEIGHT 64 -#define CURSOR_WIDTH 256 -#define CURSOR_HEIGHT 256 -#define INTEL_I2C_BUS_DVO 1#define INTEL_I2C_BUS_SDVO 2
@@ -373,7 +367,6 @@ struct intel_crtc {uint32_t cursor_addr;int16_t cursor_x, cursor_y;int16_t cursor_width, cursor_height; -int16_t max_cursor_width, max_cursor_height;bool cursor_visible;struct intel_plane_config plane_config;
Signature · 1 line
1.8.3.1
PATCH 3/3 drm/i915: Use the actual cursor width for WM computation
In reply to Damien LespiauNow that we can use different cursor sizes, we can't hardcode 64 pixels as the cursor width anymore.
--- drivers/gpu/drm/i915/intel_pm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/i915/intel_pm.c +1 -1
@@ -2120,7 +2120,7 @@ static void ilk_compute_wm_parameters(struct drm_crtc *crtc, p->pri.bytes_per_pixel = crtc->fb->bits_per_pixel /8 ; p->cur.bytes_per_pixel =4 ; p->pri.horiz_pixels = intel_crtc->config.pipe_src_w; - p->cur.horiz_pixels =64 ; + p->cur.horiz_pixels = intel_crtc->cursor_width;/* TODO: for now, assume primary and cursor planes are always enabled. */ p->pri.enabled = true; p->cur.enabled = true;
Signature · 1 line
1.8.3.1
Re: [PATCH 3/3] drm/i915: Use the actual cursor width for WM computation
Quoted 2 lines · Damien Lespiau
Now that we can use different cursor sizes, we can't hardcode 64 pixels as the cursor width anymore.
We also need fixes for i965 and g4x (normal and srwm). Not sure about vlv, it has a hardcoded 64 for computing the cursor wm, but I don't know if that is actually the cursor width.
-Chris
Signature · 1 line
Chris Wilson, Intel Open Source Technology Centre
Re: [PATCH 3/3] drm/i915: Use the actual cursor width for WM computation
In reply to Damien LespiauQuoted 2 lines · Damien Lespiau
Now that we can use different cursor sizes, we can't hardcode 64 pixels as the cursor width anymore.
Also missing is recomputing the WM when the cursor size changes. -Chris
Signature · 1 line
Chris Wilson, Intel Open Source Technology Centre
PATCH 1/2 drm/i915: Compute WM for current cursor size
In reply to Damien LespiauNow that we can use different cursor size, we can not hardcode 64 pixels as the cursor width anymore.
v2: Apply to 965gm/g4x paths as well
--- drivers/gpu/drm/i915/intel_pm.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/gpu/drm/i915/intel_pm.c +4 -4
@@ -1136,7 +1136,7 @@ static bool g4x_compute_wm0(struct drm_device *dev,/* Use the large buffer method to calculate cursor watermark */ line_time_us =max (htotal *1000 / clock,1 ); line_count = (cursor_latency_ns / line_time_us +1000 ) /1000 ; - entries = line_count *64 * pixel_size; + entries = line_count *to_intel_crtc (crtc)->cursor_width * pixel_size; tlb_miss = cursor->fifo_size*cursor->cacheline_size - hdisplay *8 ;if (tlb_miss >0 ) entries += tlb_miss;
@@ -1222,7 +1222,7 @@ static bool g4x_compute_srwm(struct drm_device *dev, *display_wm = entries + display->guard_size;/* calculate the self-refresh watermark for display cursor */ - entries = line_count * pixel_size *64 ; + entries = line_count * pixel_size *to_intel_crtc (crtc)->cursor_width; entries =DIV_ROUND_UP (entries, cursor->cacheline_size); *cursor_wm = entries + cursor->guard_size;
@@ -1457,7 +1457,7 @@ static void i965_update_wm(struct drm_crtc *unused_crtc) entries, srwm); entries = (((sr_latency_ns / line_time_us) +1000 ) /1000 ) * - pixel_size *64 ; + pixel_size *to_intel_crtc (crtc)->cursor_width; entries =DIV_ROUND_UP (entries, i965_cursor_wm_info.cacheline_size); cursor_sr = i965_cursor_wm_info.fifo_size -
@@ -2120,7 +2120,7 @@ static void ilk_compute_wm_parameters(struct drm_crtc *crtc, p->pri.bytes_per_pixel = crtc->fb->bits_per_pixel /8 ; p->cur.bytes_per_pixel =4 ; p->pri.horiz_pixels = intel_crtc->config.pipe_src_w; - p->cur.horiz_pixels =64 ; + p->cur.horiz_pixels = intel_crtc->cursor_width;/* TODO: for now, assume primary and cursor planes are always enabled. */ p->pri.enabled = true; p->cur.enabled = true;
Signature · 1 line
1.9.1
PATCH 2/2 drm/i915: Recompute WM when the cursor size changes
If the cursor width is changed, we may need to recompute our WM to prevent untold flickering. We hope that the registers are flushed on the same vblank to prevent underruns...
--- drivers/gpu/drm/i915/intel_display.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/intel_display.c +7 -1
@@ -7763,6 +7763,7 @@ static int intel_crtc_cursor_set(struct drm_crtc *crtc,struct drm_i915_private *dev_priv = dev->dev_private;struct intel_crtc *intel_crtc =to_intel_crtc (crtc);struct drm_i915_gem_object *obj; +unsigned old_width;uint32_t addr;int ret;
@@ -7853,13 +7854,18 @@ static int intel_crtc_cursor_set(struct drm_crtc *crtc,mutex_unlock (&dev->struct_mutex); + old_width = intel_crtc->cursor_width; + intel_crtc->cursor_addr = addr; intel_crtc->cursor_bo = obj; intel_crtc->cursor_width = width; intel_crtc->cursor_height = height; -if (intel_crtc->active) +if (intel_crtc->active) { +if (old_width != width) +intel_update_watermarks (crtc);intel_crtc_update_cursor (crtc, intel_crtc->cursor_bo !=NULL ); + }return 0 ; fail_unpin:
Signature · 1 line
1.9.1
Re: [PATCH 2/2] drm/i915: Recompute WM when the cursor size changes
Quoted 28 lines · Chris Wilson
If the cursor width is changed, we may need to recompute our WM to prevent untold flickering. We hope that the registers are flushed on the same vblank to prevent underruns...
Cc Damien Lespiau <[email protected]>Cc Sagar Kamble <[email protected]>Signed-off-by Chris Wilson <[email protected]>--- drivers/gpu/drm/i915/intel_display.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/intel_display.c +2
-0@@ -7763,6 +7763,7 @@ static int intel_crtc_cursor_set(struct drm_crtc *crtc,struct drm_i915_private *dev_priv = dev->dev_private;struct intel_crtc *intel_crtc =to_intel_crtc (crtc);struct drm_i915_gem_object *obj; +unsigned old_width;uint32_t addr;int ret;@@ -7853,13 +7854,18 @@ static int intel_crtc_cursor_set(struct drm_crtc *crtc,mutex_unlock (&dev->struct_mutex); + old_width = intel_crtc->cursor_width;
drivers/gpu/drm/i915/intel_display.c static int intel_crtc_cursor_set(struct drm_crtc *crtc, · line 7866
Quoted 10 lines
drivers/gpu/drm/i915/intel_display.c +4
-1+ intel_crtc->cursor_addr = addr; intel_crtc->cursor_bo = obj; intel_crtc->cursor_width = width; intel_crtc->cursor_height = height; -if (intel_crtc->active) +if (intel_crtc->active) { +if (old_width != width) +intel_update_watermarks (crtc);
Shouldn't we recompute when shrinking after and when growing before we change the cursor size? vblank-syncing maybe even. Given all the amotic foo we currently have I expect that cursors are as underrun prone as all the other stuff is, too.
But can be done in a later patch, together with the nasty igt which walks the cursor all over the place while changing the size ;-) And I guess Ville gets to pimp his atomic update code and wm 2-stage update for this stuff here, too.
I get a feeling this isn't quite as simple as Sagar's first patch suggested ...
-Daniel
Quoted 12 lines
drivers/gpu/drm/i915/intel_display.c +1
-0intel_crtc_update_cursor (crtc, intel_crtc->cursor_bo !=NULL ); + }return 0 ; fail_unpin:Signature · 6 lines
1.9.1 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Signature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch
Re: [PATCH 2/2] drm/i915: Recompute WM when the cursor size changes
In reply to Chris WilsonQuoted 7 lines · Chris Wilson
If the cursor width is changed, we may need to recompute our WM to prevent untold flickering. We hope that the registers are flushed on the same vblank to prevent underruns...
Cc Damien Lespiau <[email protected]>Cc Sagar Kamble <[email protected]>Signed-off-by Chris Wilson <[email protected]>
Indeed, I'll learn to see the bigger picture one day, one day...
Quoted 39 lines
--- drivers/gpu/drm/i915/intel_display.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/intel_display.c +7
-1@@ -7763,6 +7763,7 @@ static int intel_crtc_cursor_set(struct drm_crtc *crtc,struct drm_i915_private *dev_priv = dev->dev_private;struct intel_crtc *intel_crtc =to_intel_crtc (crtc);struct drm_i915_gem_object *obj; +unsigned old_width;uint32_t addr;int ret;@@ -7853,13 +7854,18 @@ static int intel_crtc_cursor_set(struct drm_crtc *crtc,mutex_unlock (&dev->struct_mutex); + old_width = intel_crtc->cursor_width; + intel_crtc->cursor_addr = addr; intel_crtc->cursor_bo = obj; intel_crtc->cursor_width = width; intel_crtc->cursor_height = height; -if (intel_crtc->active) +if (intel_crtc->active) { +if (old_width != width) +intel_update_watermarks (crtc);intel_crtc_update_cursor (crtc, intel_crtc->cursor_bo !=NULL ); + }return 0 ; fail_unpin:Signature · 1 line
1.9.1
Re: [PATCH 2/2] drm/i915: Recompute WM when the cursor size changes
Quoted 5 lines · Damien Lespiau
Quoted 4 lines · Chris Wilson
If the cursor width is changed, we may need to recompute our WM to prevent untold flickering. We hope that the registers are flushed on the same vblank to prevent underruns...
Quoted 7 lines
Quoted 3 lines
Cc Damien Lespiau <[email protected]>Cc Sagar Kamble <[email protected]>Signed-off-by Chris Wilson <[email protected]>Indeed, I'll learn to see the bigger picture one day, one day...
Reviewed-by Damien Lespiau <[email protected]>
Both merged, thanks for patches&review.
-Daniel
Quoted 44 lines
Quoted 40 lines
--- drivers/gpu/drm/i915/intel_display.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/intel_display.c +7
-1@@ -7763,6 +7763,7 @@ static int intel_crtc_cursor_set(struct drm_crtc *crtc,struct drm_i915_private *dev_priv = dev->dev_private;struct intel_crtc *intel_crtc =to_intel_crtc (crtc);struct drm_i915_gem_object *obj; +unsigned old_width;uint32_t addr;int ret;@@ -7853,13 +7854,18 @@ static int intel_crtc_cursor_set(struct drm_crtc *crtc,mutex_unlock (&dev->struct_mutex); + old_width = intel_crtc->cursor_width; + intel_crtc->cursor_addr = addr; intel_crtc->cursor_bo = obj; intel_crtc->cursor_width = width; intel_crtc->cursor_height = height; -if (intel_crtc->active) +if (intel_crtc->active) { +if (old_width != width) +intel_update_watermarks (crtc);intel_crtc_update_cursor (crtc, intel_crtc->cursor_bo !=NULL ); + }return 0 ; fail_unpin:Signature · 1 line
1.9.1_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Signature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch
Re: [PATCH 1/2] drm/i915: Compute WM for current cursor size
In reply to Chris WilsonQuoted 8 lines · Chris Wilson
Now that we can use different cursor size, we can not hardcode 64 pixels as the cursor width anymore.
v2: Apply to 965gm/g4x paths as well
Cc Damien Lespiau <[email protected]>Cc Sagar Kamble <[email protected]>Signed-off-by Chris Wilson <[email protected]>
Quoted 47 lines
--- drivers/gpu/drm/i915/intel_pm.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)drivers/gpu/drm/i915/intel_pm.c +4
-4@@ -1136,7 +1136,7 @@ static bool g4x_compute_wm0(struct drm_device *dev,/* Use the large buffer method to calculate cursor watermark */ line_time_us =max (htotal *1000 / clock,1 ); line_count = (cursor_latency_ns / line_time_us +1000 ) /1000 ; - entries = line_count *64 * pixel_size; + entries = line_count *to_intel_crtc (crtc)->cursor_width * pixel_size; tlb_miss = cursor->fifo_size*cursor->cacheline_size - hdisplay *8 ;if (tlb_miss >0 ) entries += tlb_miss;@@ -1222,7 +1222,7 @@ static bool g4x_compute_srwm(struct drm_device *dev, *display_wm = entries + display->guard_size;/* calculate the self-refresh watermark for display cursor */ - entries = line_count * pixel_size *64 ; + entries = line_count * pixel_size *to_intel_crtc (crtc)->cursor_width; entries =DIV_ROUND_UP (entries, cursor->cacheline_size); *cursor_wm = entries + cursor->guard_size;@@ -1457,7 +1457,7 @@ static void i965_update_wm(struct drm_crtc *unused_crtc) entries, srwm); entries = (((sr_latency_ns / line_time_us) +1000 ) /1000 ) * - pixel_size *64 ; + pixel_size *to_intel_crtc (crtc)->cursor_width; entries =DIV_ROUND_UP (entries, i965_cursor_wm_info.cacheline_size); cursor_sr = i965_cursor_wm_info.fifo_size -@@ -2120,7 +2120,7 @@ static void ilk_compute_wm_parameters(struct drm_crtc *crtc, p->pri.bytes_per_pixel = crtc->fb->bits_per_pixel /8 ; p->cur.bytes_per_pixel =4 ; p->pri.horiz_pixels = intel_crtc->config.pipe_src_w; - p->cur.horiz_pixels =64 ; + p->cur.horiz_pixels = intel_crtc->cursor_width;/* TODO: for now, assume primary and cursor planes are always enabled. */ p->pri.enabled = true; p->cur.enabled = true;Signature · 1 line
1.9.1