From: Damien Lespiau <damien.lespiau@intel.com>
To: sagar.a.kamble@intel.com
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/1] drm/i915: Fixing cursor size parameters for wm calculation
Date: Tue, 25 Mar 2014 14:50:16 +0000 [thread overview]
Message-ID: <20140325145016.GC8248@strange.amr.corp.intel.com> (raw)
In-Reply-To: <1395742596-20235-1-git-send-email-sagar.a.kamble@intel.com>
On Tue, Mar 25, 2014 at 03:46:36PM +0530, sagar.a.kamble@intel.com wrote:
> From: Sagar Kamble <sagar.a.kamble@intel.com>
>
> Cursor size is changed now take care of larger cursor sizes.
> wm calculation was hardcoded to 64 before so changing it.
>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: Jani Nikula <jani.nikula@linux.intel.com>
> Cc: Damien Lespiau <damien.lespiau@intel.com>
> Signed-off-by: Sagar Kamble <sagar.a.kamble@intel.com>
> ---
> drivers/gpu/drm/i915/intel_pm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
> index ad58ce3..2177e3d 100644
> --- a/drivers/gpu/drm/i915/intel_pm.c
> +++ b/drivers/gpu/drm/i915/intel_pm.c
> @@ -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 = dev->mode_config.cursor_width;
Hum? It seems that mode_config.cursor_width is supposed to have the
preferred cursor size so a generic DDX (for instance) can select a size
that can be used. If we declare 256x256, that generic driver will use a
big buffer for the cursor, without any good reason.
A previous patch from you doesn't seem to to do that correctly by always
setting the max size, we're fine with the default 64x64 (I just sent a
patch to address that).
Instead of using the DRM cursor_config value the natural thing to do
would be to use the actual width being used (sent patch).
--
Damien
next prev parent reply other threads:[~2014-03-25 14:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 10:09 [PATCH 1/1] drm/i915: Enabling 128x128 and 256x256 ARGB Cursor Support sagar.a.kamble
2014-02-18 13:13 ` Ville Syrjälä
2014-02-24 15:41 ` [PATCH v2 " sagar.a.kamble
2014-02-24 16:06 ` Ville Syrjälä
2014-03-08 18:49 ` [PATCH v3 " sagar.a.kamble
2014-03-08 18:51 ` Alex Deucher
2014-03-08 19:04 ` Sagar Arun Kamble
2014-03-08 19:07 ` Sagar Arun Kamble
2014-03-10 9:29 ` [Intel-gfx] " Chris Wilson
2014-03-10 9:55 ` Daniel Vetter
2014-03-10 10:04 ` Chris Wilson
2014-03-10 10:07 ` Daniel Vetter
2014-03-10 10:39 ` Daniel Vetter
2014-03-10 10:03 ` Daniel Vetter
2014-03-10 11:36 ` [PATCH v4 " sagar.a.kamble
2014-03-17 5:47 ` Sagar Arun Kamble
2014-03-20 15:30 ` Imre Deak
2014-03-20 16:35 ` Daniel Vetter
2014-03-20 15:37 ` Imre Deak
2014-03-24 16:30 ` [PATCH v2 " Damien Lespiau
2014-03-25 10:16 ` [PATCH 1/1] drm/i915: Fixing cursor size parameters for wm calculation sagar.a.kamble
2014-03-25 14:50 ` Damien Lespiau [this message]
2014-02-25 11:35 ` [PATCH 1/1] drm/i915: Enabling 128x128 and 256x256 ARGB Cursor Support Thierry Reding
2014-02-25 11:56 ` Ville Syrjälä
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140325145016.GC8248@strange.amr.corp.intel.com \
--to=damien.lespiau@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=sagar.a.kamble@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox