From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Paulo Zanoni" <przanoni@gmail.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 1/4] drm/i915: Don't try to enable cursor from setplane when crtc is disabled
Date: Thu, 14 Aug 2014 17:31:47 +0300 [thread overview]
Message-ID: <87tx5fp2gc.fsf@intel.com> (raw)
In-Reply-To: <CA+gsUGQ_uV8rhzvAPZYjacqxLSU29ALzK0a9ZnuG0=CQD2-poQ@mail.gmail.com>
On Tue, 12 Aug 2014, Paulo Zanoni <przanoni@gmail.com> wrote:
> 2014-08-12 13:39 GMT-03:00 <ville.syrjala@linux.intel.com>:
>> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>>
>> Make sure the cursor gets fully clipped when enabling it on a disabled
>> crtc via setplane. This will prevent the lower level code from
>> attempting to enable the cursor in hardware.
>
> If this is going to replace part of the fix I recently submitted, it
> needs Cc: stable@vger.kernel.org.
Picked this up for -fixes.
BR,
Jani.
>
> I briefly smoke-tested it and it appears to properly replace the
> "intel_crtc->active" early return which you pointed.
>
>>
>> Cc: Paulo Zanoni <przanoni@gmail.com>
>> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> ---
>> drivers/gpu/drm/i915/intel_display.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
>> index 511c8f4..123cbf1 100644
>> --- a/drivers/gpu/drm/i915/intel_display.c
>> +++ b/drivers/gpu/drm/i915/intel_display.c
>> @@ -11701,8 +11701,8 @@ intel_cursor_plane_update(struct drm_plane *plane, struct drm_crtc *crtc,
>> };
>> const struct drm_rect clip = {
>> /* integer pixels */
>> - .x2 = intel_crtc->config.pipe_src_w,
>> - .y2 = intel_crtc->config.pipe_src_h,
>> + .x2 = intel_crtc->active ? intel_crtc->config.pipe_src_w : 0,
>> + .y2 = intel_crtc->active ? intel_crtc->config.pipe_src_h : 0,
>> };
>> bool visible;
>> int ret;
>> --
>> 1.8.5.5
>>
>
>
>
> --
> Paulo Zanoni
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-08-14 14:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 16:39 [PATCH 0/4] drm/i915: Cursor fixes and cleanups ville.syrjala
2014-08-12 16:39 ` [PATCH 1/4] drm/i915: Don't try to enable cursor from setplane when crtc is disabled ville.syrjala
2014-08-12 18:01 ` Paulo Zanoni
2014-08-14 14:31 ` Jani Nikula [this message]
2014-08-12 16:39 ` [PATCH 2/4] drm/i915: Move CURSIZE setup to i845_update_cursor() ville.syrjala
2014-08-12 16:39 ` [PATCH 3/4] drm/i915: Unify ivb_update_cursor() and i9xx_update_cursor() ville.syrjala
2014-08-12 16:39 ` [PATCH 4/4] drm/i915: Add support for variable cursor size on 845/865 ville.syrjala
2014-08-12 16:52 ` Chris Wilson
2014-08-13 7:05 ` Chris Wilson
2014-08-13 7:12 ` Chris Wilson
2014-08-13 7:18 ` Chris Wilson
2014-08-13 8:57 ` [PATCH v4 " ville.syrjala
2014-08-13 11:34 ` Daniel Vetter
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=87tx5fp2gc.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=przanoni@gmail.com \
--cc=ville.syrjala@linux.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