Plane support for SNB and IVB
Subsystems (2)
I think the core support is ready now, but I'd like feedback on the color key ioctl. It would be good to have a way to disable it at runtime (w/o color keying enabled, the sprite will always sit on top of the primary), and potentially add alpha support at some point.
Would 0 as the color key work well enough as a "disable" flag? Or should I add a separate field to the ioctl? Anyone have a preference?
Thanks,
Jesse
PATCH 1/3 drm/i915: add SNB and IVB video sprite support v5
The video sprites support various video surface formats natively and can handle scaling as well. So add support for them using the new DRM core sprite support functions.
v2: use drm specific fourcc header and defines
v3: address Daniel's comments:
- don't take struct mutex around register access (only needed for regs in the GT power well)
- don't hold struct mutex across vblank waits
- fix up update_plane API (pass obj instead of GTT offset)
- add interlaced defines for sprite regs
- drop unnecessary 'reg' variables
- comment double buffered reg flushing
Also fix w/h confusion when writing the scaling reg.
v4: more fixes, address more comments from Daniel, and include Hai's fix
- prevent divide by zero in scaling calculation (Hai Lan)
- update to Ville's new DRM_FORMAT_* types
- fix sprite watermark handling (calc based on CRTC size, separate from normal display wm)
- remove private refcounts now that the fb cleanups handles things
v5: add linear surface support
For this version, I tested DPMS since it came up in the last review; DPMS off/on works ok when a video player is working under X, but for power saving we'll probably want to do something smarter. I'll leave that for a separate patch on top. Likewise with the refcounting/fb layer handling, which are really separate cleanups.
--- drivers/gpu/drm/i915/Makefile | 1 + drivers/gpu/drm/i915/i915_drv.h | 3 + drivers/gpu/drm/i915/i915_reg.h | 133 ++++++++++ drivers/gpu/drm/i915/intel_display.c | 174 +++++++++++++- drivers/gpu/drm/i915/intel_drv.h | 28 ++ drivers/gpu/drm/i915/intel_fb.c | 6 + drivers/gpu/drm/i915/intel_sprite.c | 452 ++++++++++++++++++++++++++++++++++ 7 files changed, 790 insertions(+), 7 deletions(-) create mode 100644 drivers/gpu/drm/i915/intel_sprite.c
drivers/gpu/drm/i915/Makefile +1 -0
@@ -28,6 +28,7 @@ i915-y := i915_drv.o i915_dma.o i915_irq.o i915_mem.o \ intel_dvo.o \ intel_ringbuffer.o \ intel_overlay.o \ + intel_sprite.o \ intel_opregion.o \ dvo_ch7xxx.o \ dvo_ch7017.o \
drivers/gpu/drm/i915/i915_drv.h +3 -0
@@ -206,6 +206,8 @@ struct drm_i915_display_funcs {int (*get_display_clock_speed)(struct drm_device *dev);int (*get_fifo_size)(struct drm_device *dev,int plane);void (*update_wm)(struct drm_device *dev); +void (*update_sprite_wm)(struct drm_device *dev,int pipe, +uint32_t sprite_width,int pixel_size); int (*crtc_mode_set)(struct drm_crtc *crtc, struct drm_display_mode *mode, struct drm_display_mode *adjusted_mode,
@@ -347,6 +349,7 @@ typedef struct drm_i915_private {/* overlay */ struct intel_overlay *overlay; +bool sprite_scaling_enabled;/* LVDS info */ int backlight_level;/* restore backlight to this value */
drivers/gpu/drm/i915/i915_reg.h +133 -0
145 lines not on this page · raw message
drivers/gpu/drm/i915/intel_display.c +167 -7
234 lines not on this page · raw message
drivers/gpu/drm/i915/intel_drv.h +28 -0
@@ -176,10 +176,27 @@ struct intel_crtc {bool use_pll_a; }; +struct intel_plane { +struct drm_plane base; +enum pipe pipe; +struct drm_i915_gem_object *obj; +int max_downscale; +u32 lut_r[1024 ], lut_g[1024 ], lut_b[1024 ]; +void (*update_plane)(struct drm_plane *plane, +struct drm_framebuffer *fb, +struct drm_i915_gem_object *obj, +int crtc_x,int crtc_y, +unsigned int crtc_w,unsigned int crtc_h, +uint32_t x,uint32_t y, +uint32_t src_w,uint32_t src_h); +void (*disable_plane)(struct drm_plane *plane); +}; +#define to_intel_crtc (x) container_of(x, struct intel_crtc, base)#define to_intel_connector (x) container_of(x, struct intel_connector, base)#define to_intel_encoder (x) container_of(x, struct intel_encoder, base)#define to_intel_framebuffer (x) container_of(x, struct intel_framebuffer, base) +#define to_intel_plane (x) container_of(x, struct intel_plane, base)#define DIP_HEADER_SIZE 5
@@ -289,6 +306,7 @@ intel_dp_set_m_n(struct drm_crtc *crtc, struct drm_display_mode *mode,extern bool intel_dpd_is_edp (struct drm_device *dev);extern void intel_edp_link_config (struct intel_encoder *,int *,int *);extern bool intel_encoder_is_pch_edp (struct drm_encoder *encoder); +extern int intel_plane_init (struct drm_device *dev,enum pipe pipe);/* intel_panel.c */ extern void intel_fixed_panel_mode(struct drm_display_mode *fixed_mode,
@@ -379,9 +397,19 @@ extern int intel_overlay_attrs(struct drm_device *dev, void *data,extern void intel_fb_output_poll_changed (struct drm_device *dev);extern void intel_fb_restore_mode (struct drm_device *dev); +extern void assert_pipe (struct drm_i915_private *dev_priv,enum pipe pipe, +bool state); +#define assert_pipe_enabled (d, p) assert_pipe(d, p, true) +#define assert_pipe_disabled (d, p) assert_pipe(d, p, false) +extern void intel_init_clock_gating (struct drm_device *dev);extern void intel_write_eld (struct drm_encoder *encoder,struct drm_display_mode *mode);extern void intel_cpt_verify_modeset (struct drm_device *dev,int pipe); +/* For use by IVB LP watermark workaround in intel_sprite.c */ +extern void sandybridge_update_wm (struct drm_device *dev); +extern void intel_update_sprite_watermarks (struct drm_device *dev,int pipe, +uint32_t sprite_width, +int pixel_size);#endif /* __INTEL_DRV_H__ */
drivers/gpu/drm/i915/intel_fb.c +6 -0
@@ -270,8 +270,14 @@ void intel_fb_restore_mode(struct drm_device *dev) {int ret;drm_i915_private_t *dev_priv = dev->dev_private; +struct drm_mode_config *config = &dev->mode_config; +struct drm_plane *plane; ret =drm_fb_helper_restore_fbdev_mode (&dev_priv->fbdev->helper);if (ret)DRM_DEBUG ("failed to restore crtc mode\n" ); + +/* Be sure to shut off any planes that may be active */ +list_for_each_entry (plane, &config->plane_list, head) + plane->funcs->disable_plane (plane); }
drivers/gpu/drm/i915/intel_sprite.c new file +452 -0
452 lines not on this page · raw message
Signature · 6 lines
1.7.4.1 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 1/3] drm/i915: add SNB and IVB video sprite support v5
Quoted 22 lines · Jesse Barnes
The video sprites support various video surface formats natively and can handle scaling as well. So add support for them using the new DRM core sprite support functions.
v2: use drm specific fourcc header and defines
v3: address Daniel's comments:
- don't take struct mutex around register access (only needed for regs in the GT power well)
- don't hold struct mutex across vblank waits
- fix upupdate_planeAPI (pass obj instead of GTT offset)
- add interlaced defines for sprite regs
- drop unnecessary 'reg' variables
- comment double buffered reg flushing
Also fix w/h confusion when writing the scaling reg.
v4: more fixes, address more comments from Daniel, and include Hai's fix
- prevent divide by zero in scaling calculation (Hai Lan)
- update to Ville's new DRM_FORMAT_* types
- fix sprite watermark handling (calc based on CRTC size, separate from normal display wm)
- remove private refcounts now that the fb cleanups handles things
v5: add linear surface support
Quoted 7 lines
For this version, I tested DPMS since it came up in the last review; DPMS off/on works ok when a video player is working under X, but for power saving we'll probably want to do something smarter. I'll leave that for a separate patch on top. Likewise with the refcounting/fb layer handling, which are really separate cleanups.
Signed-off-by Jesse Barnes <[email protected]>
I didn't bother to recheck the regs and and the wm stuff looks like the usual magic ;-) Otherwise you've implemented way more of my review comments than I could possibly still remember, so it must be good.
Signature · 3 lines
Daniel Vetter Mail: [email protected] Mobile: +41 (0)79 365 57 48
Re: [PATCH 1/3] drm/i915: add SNB and IVB video sprite support v5
Quoted 29 lines · On Mon, 12 Dec 2011 22:56:34 +0100 Daniel Vetter <[email protected]> wrote:
Quoted 28 lines · Jesse Barnes
The video sprites support various video surface formats natively and can handle scaling as well. So add support for them using the new DRM core sprite support functions.
v2: use drm specific fourcc header and defines
v3: address Daniel's comments:
- don't take struct mutex around register access (only needed for regs in the GT power well)
- don't hold struct mutex across vblank waits
- fix upupdate_planeAPI (pass obj instead of GTT offset)
- add interlaced defines for sprite regs
- drop unnecessary 'reg' variables
- comment double buffered reg flushing
Also fix w/h confusion when writing the scaling reg.
v4: more fixes, address more comments from Daniel, and include Hai's fix
- prevent divide by zero in scaling calculation (Hai Lan)
- update to Ville's new DRM_FORMAT_* types
- fix sprite watermark handling (calc based on CRTC size, separate from normal display wm)
- remove private refcounts now that the fb cleanups handles things
v5: add linear surface supportFor this version, I tested DPMS since it came up in the last review; DPMS off/on works ok when a video player is working under X, but for power saving we'll probably want to do something smarter. I'll leave that for a separate patch on top. Likewise with the refcounting/fb layer handling, which are really separate cleanups.
Quoted 7 lines
Quoted 1 line
Signed-off-by Jesse Barnes <[email protected]>I didn't bother to recheck the regs and and the wm stuff looks like the usual magic ;-) Otherwise you've implemented way more of my review comments than I could possibly still remember, so it must be good.
Reviewed-by Daniel Vetter <[email protected]>
The one thing I kept out was the "disable planes in generic code" call. The TI guys are working on using planes to represent all planes, not just additional overlays, so calling disable from generic code seemed unfriendly.
Keith, this one is ready for -next. I'll clean up the ioctl now and re-post; without it the overlays will always sit on top without blending, so the patch is still safe.
Thanks,
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 1/3] drm/i915: add SNB and IVB video sprite support v5
In reply to Daniel VetterQuoted 29 lines · On Mon, 12 Dec 2011 22:56:34 +0100 Daniel Vetter <[email protected]> wrote:
Quoted 28 lines · Jesse Barnes
The video sprites support various video surface formats natively and can handle scaling as well. So add support for them using the new DRM core sprite support functions.
v2: use drm specific fourcc header and defines
v3: address Daniel's comments:
- don't take struct mutex around register access (only needed for regs in the GT power well)
- don't hold struct mutex across vblank waits
- fix upupdate_planeAPI (pass obj instead of GTT offset)
- add interlaced defines for sprite regs
- drop unnecessary 'reg' variables
- comment double buffered reg flushing
Also fix w/h confusion when writing the scaling reg.
v4: more fixes, address more comments from Daniel, and include Hai's fix
- prevent divide by zero in scaling calculation (Hai Lan)
- update to Ville's new DRM_FORMAT_* types
- fix sprite watermark handling (calc based on CRTC size, separate from normal display wm)
- remove private refcounts now that the fb cleanups handles things
v5: add linear surface supportFor this version, I tested DPMS since it came up in the last review; DPMS off/on works ok when a video player is working under X, but for power saving we'll probably want to do something smarter. I'll leave that for a separate patch on top. Likewise with the refcounting/fb layer handling, which are really separate cleanups.
Quoted 7 lines
Quoted 1 line
Signed-off-by Jesse Barnes <[email protected]>I didn't bother to recheck the regs and and the wm stuff looks like the usual magic ;-) Otherwise you've implemented way more of my review comments than I could possibly still remember, so it must be good.
Reviewed-by Daniel Vetter <[email protected]>
I take it back, I need to re-post this one minus a few lines now that I'm updating the color key support. New series on its way.
Thanks,
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 2/3 drm/i915: add destination color key support
In reply to Jesse BarnesAdd new ioctls for getting and setting the current destination color key. This allows for simple overlay display control by matching a color key value in the primary plane before blending the overlay on top.
v2: remove unnecessary mutex acquire/release around reg accesses
--- drivers/gpu/drm/i915/i915_dma.c | 2 + drivers/gpu/drm/i915/i915_reg.h | 2 + drivers/gpu/drm/i915/intel_drv.h | 8 ++ drivers/gpu/drm/i915/intel_sprite.c | 138 +++++++++++++++++++++++++++++++++++ include/drm/i915_drm.h | 16 ++++ 5 files changed, 166 insertions(+), 0 deletions(-)
drivers/gpu/drm/i915/i915_dma.c +2 -0
@@ -2295,6 +2295,8 @@ struct drm_ioctl_desc i915_ioctls[] = {DRM_IOCTL_DEF_DRV (I915_GEM_MADVISE , i915_gem_madvise_ioctl,DRM_UNLOCKED ),DRM_IOCTL_DEF_DRV (I915_OVERLAY_PUT_IMAGE , intel_overlay_put_image,DRM_MASTER |DRM_CONTROL_ALLOW |DRM_UNLOCKED ),DRM_IOCTL_DEF_DRV (I915_OVERLAY_ATTRS , intel_overlay_attrs,DRM_MASTER |DRM_CONTROL_ALLOW |DRM_UNLOCKED ), +DRM_IOCTL_DEF_DRV (I915_SET_SPRITE_DESTKEY , intel_sprite_set_destkey,DRM_MASTER |DRM_CONTROL_ALLOW |DRM_UNLOCKED ), + DRM_IOCTL_DEF_DRV(I915_GET_SPRITE_DESTKEY, intel_sprite_get_destkey, DRM_MASTER|DRM_CONTROL_ALLOW|DRM_UNLOCKED), };int i915_max_ioctl =DRM_ARRAY_SIZE (i915_ioctls);
drivers/gpu/drm/i915/i915_reg.h +2 -0
@@ -2738,6 +2738,8 @@#define DVSSIZE (pipe) _PIPE(pipe, _DVSASIZE, _DVSBSIZE)#define DVSSCALE (pipe) _PIPE(pipe, _DVSASCALE, _DVSBSCALE)#define DVSTILEOFF (pipe) _PIPE(pipe, _DVSATILEOFF, _DVSBTILEOFF) +#define DVSKEYVAL (pipe) _PIPE(pipe, _DVSAKEYVAL, _DVSBKEYVAL) +#define DVSKEYMSK (pipe) _PIPE(pipe, _DVSAKEYMSK, _DVSBKEYMSK)#define _SPRA_CTL 0x70280#define SPRITE_ENABLE (1<<31)
drivers/gpu/drm/i915/intel_drv.h +8 -0
@@ -190,6 +190,8 @@ struct intel_plane { uint32_t x, uint32_t y, uint32_t src_w, uint32_t src_h);void (*disable_plane)(struct drm_plane *plane); +int (*update_destkey)(struct drm_plane *plane,u32 value); +u32 (*get_destkey)(struct drm_plane *plane); };#define to_intel_crtc (x) container_of(x, struct intel_crtc, base)
@@ -412,4 +414,10 @@ extern void sandybridge_update_wm(struct drm_device *dev);extern void intel_update_sprite_watermarks (struct drm_device *dev,int pipe,uint32_t sprite_width,int pixel_size); + +extern int intel_sprite_set_destkey (struct drm_device *dev,void *data, +struct drm_file *file_priv); +extern int intel_sprite_get_destkey (struct drm_device *dev,void *data, +struct drm_file *file_priv); +#endif /* __INTEL_DRV_H__ */
drivers/gpu/drm/i915/intel_sprite.c +138 -0
172 lines not on this page · raw message
include/drm/i915_drm.h +16 -0
@@ -198,6 +198,8 @@ typedef struct _drm_i915_sarea {#define DRM_I915_OVERLAY_PUT_IMAGE 0x27#define DRM_I915_OVERLAY_ATTRS 0x28#define DRM_I915_GEM_EXECBUFFER2 0x29 +#define DRM_I915_GET_SPRITE_DESTKEY 0x2a +#define DRM_I915_SET_SPRITE_DESTKEY 0x2b#define DRM_IOCTL_I915_INIT DRM_IOW( DRM_COMMAND_BASE + DRM_I915_INIT, drm_i915_init_t)#define DRM_IOCTL_I915_FLUSH DRM_IO ( DRM_COMMAND_BASE + DRM_I915_FLUSH)
@@ -239,6 +241,8 @@ typedef struct _drm_i915_sarea {#define DRM_IOCTL_I915_GEM_MADVISE DRM_IOWR(DRM_COMMAND_BASE + DRM_I915_GEM_MADVISE, struct drm_i915_gem_madvise)#define DRM_IOCTL_I915_OVERLAY_PUT_IMAGE DRM_IOW(DRM_COMMAND_BASE + DRM_I915_OVERLAY_PUT_IMAGE, struct drm_intel_overlay_put_image)#define DRM_IOCTL_I915_OVERLAY_ATTRS DRM_IOWR(DRM_COMMAND_BASE + DRM_I915_OVERLAY_ATTRS, struct drm_intel_overlay_attrs) +#define DRM_IOCTL_I915_SET_SPRITE_DESTKEY DRM_IOWR(DRM_COMMAND_BASE + DRM_I915_SET_SPRITE_DESTKEY, struct drm_intel_set_sprite_destkey) +#define DRM_IOCTL_I915_GET_SPRITE_DESTKEY DRM_IOWR(DRM_COMMAND_BASE + DRM_I915_SET_SPRITE_DESTKEY, struct drm_intel_get_sprite_destkey)/* Allow drivers to submit batchbuffers directly to hardware, relying * on the security mechanisms provided by hardware.
@@ -844,4 +848,16 @@ struct drm_intel_overlay_attrs { __u32 gamma5; }; +/* Set the destination color key on a given sprite */ +struct drm_intel_set_sprite_destkey { +__u32 plane_id; +__u32 value; +}; + +/* Get the current destination color key on a given sprite */ +struct drm_intel_get_sprite_destkey { +__u32 plane_id; +__u32 value; +}; +#endif /* _I915_DRM_H_ */
Signature · 1 line
1.7.4.1
Re: [PATCH 2/3] drm/i915: add destination color key support
Quoted 7 lines · Jesse Barnes
Add new ioctls for getting and setting the current destination color key. This allows for simple overlay display control by matching a color key value in the primary plane before blending the overlay on top.
v2: remove unnecessary mutex acquire/release around reg accesses
Signed-off-by Jesse Barnes <[email protected]>
[snip]
include/drm/i915_drm.h struct drm_intel_overlay_attrs { · line 861
Quoted 11 lines
include/drm/i915_drm.h +11
-0+/* Set the destination color key on a given sprite */ +struct drm_intel_set_sprite_destkey { +__u32 plane_id; +__u32 value; +}; + +/* Get the current destination color key on a given sprite */ +struct drm_intel_get_sprite_destkey { +__u32 plane_id; +__u32 value; +};
As explained in my top-reply, I think we want a __u32 flags here to enable the colorkey (and maybe switch between dst/src color key). Nothing else to complain about here.
-Daniel
Signature · 3 lines
Daniel Vetter Mail: [email protected] Mobile: +41 (0)79 365 57 48
PATCH 3/3 drm/i915: track sprite coverage and disable primary plane if possible
In reply to Jesse BarnesTo save power when the sprite is full screen, we can disable the primary plane on the same pipe. Track the sprite status and enable/disable the primary opportunistically.
v2: remove primary plane enable/disable hooks; they're identical
--- drivers/gpu/drm/i915/intel_drv.h | 1 + drivers/gpu/drm/i915/intel_sprite.c | 41 +++++++++++++++++++++++++++++++++++ 2 files changed, 42 insertions(+), 0 deletions(-)
drivers/gpu/drm/i915/intel_drv.h +1 -0
@@ -180,6 +180,7 @@ struct intel_plane {struct drm_plane base;enum pipe pipe;struct drm_i915_gem_object *obj; +bool primary_disabled;int max_downscale;u32 lut_r[1024 ], lut_g[1024 ], lut_b[1024 ]; void (*update_plane)(struct drm_plane *plane,
drivers/gpu/drm/i915/intel_sprite.c +41 -0
62 lines not on this page · raw message
Signature · 1 line
1.7.4.1
Re: [PATCH 3/3] drm/i915: track sprite coverage and disable primary plane if possible
Quoted 7 lines · Jesse Barnes
To save power when the sprite is full screen, we can disable the primary plane on the same pipe. Track the sprite status and enable/disable the primary opportunistically.
v2: remove primary plane enable/disable hooks; they're identical
Signed-off-by Jesse Barnes
Minor nitpick on patch-splitting: You've left the disable_primary calculations in the 1st patch. But since I didn't notice it there, I can't be that bad ;-)
Signature · 3 lines
Daniel Vetter Mail: [email protected] Mobile: +41 (0)79 365 57 48
2011/12/8 Jesse Barnes <[email protected]>
Quoted 9 lines
I think the core support is ready now, but I'd like feedback on the color key ioctl. It would be good to have a way to disable it at runtime (w/o color keying enabled, the sprite will always sit on top of the primary), and potentially add alpha support at some point.
Would 0 as the color key work well enough as a "disable" flag? Or should I add a separate field to the ioctl? Anyone have a preference?
Do you mean whether to use colorkey value 0 as a disabled flag? I don't think we can use 0 as disabled colorkey because sometimes we need to set the colorkey as 0.
So I think it's better to use a separate field of ioctl.
Thanks and best regards.
Hai Lan
Quoted 7 lines · Jesse Barnes
I think the core support is ready now, but I'd like feedback on the color key ioctl. It would be good to have a way to disable it at runtime (w/o color keying enabled, the sprite will always sit on top of the primary), and potentially add alpha support at some point.
Would 0 as the color key work well enough as a "disable" flag? Or should I add a separate field to the ioctl? Anyone have a preference?
0 is black and I can image a legit color key with "black bars". Any other value makes the interface kinda ad-hoc. So a separate field preferred. -Daniel
Signature · 3 lines
Daniel Vetter Mail: [email protected] Mobile: +41 (0)79 365 57 48