From: Dave Gordon <david.s.gordon@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, akshu.agrawal@intel.com
Subject: Re: [PATCH 2/2] drm/i915: Crop cursor image for CHV pipe C cursor issue
Date: Wed, 8 Jun 2016 11:18:57 +0100 [thread overview]
Message-ID: <5757F111.2020801@intel.com> (raw)
In-Reply-To: <20160608084035.GL3363@phenom.ffwll.local>
On 08/06/16 09:40, Daniel Vetter wrote:
> On Wed, Jun 08, 2016 at 01:57:44PM +0530, Akshu Agrawal wrote:
>> CHV pipe C hits underrun when we get -ve X values of cursor. To avoid
>> this we crop the cursor image for by -ve X value and thus use '0' as
>> least X value.
>
> You're talking about "-ve" here and there's absolutely no "-ve" anywhere
> in your patch. That makes your commit message non-understandable.
That's shorthand for "negative", and some of the code below is indeed
testing for a negative X coordinate, e.g:
[snip]
>> + /*
>> + * There is an issue in CHV PIPE C where we hit underrun on
>> + * -ve value of cursor. To avoid this we are cropping the
>> + * image for all PIPE C -ve values.
>> + */
>> + if (IS_CHERRYVIEW(plane->dev)) {
>> + if (pipe == PIPE_C && state->visible &&
>> + state->base.crtc_x < 0) {
>> + ret = vlv_cursor_crop(state, crtc_prev_x);
>> + if (ret)
>> + return -ENOMEM;
>> + } else if (crtc_prev_x < 0) { /* Restore the image back */
>> + char __iomem *base;
>> + char __iomem *org_image = state->vlv_cursor_image;
>> + int size = obj->base.size;
>> +
>> + if (org_image == NULL)
>> + return -ENOMEM;
>> + base = vlv_pin_and_map_buffer_obj(obj);
>> + if (base == NULL)
>> + return -ENOMEM;
>> + memcpy(base, org_image, size);
>> + vlv_unpin_buffer_obj(obj, base);
>> + }
>> + }
HTH,
.Dave.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-06-08 10:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 8:27 [PATCH 1/2] Revert "drm/i915: Workaround CHV pipe C cursor fail" Akshu Agrawal
2016-06-08 8:27 ` [PATCH 2/2] drm/i915: Crop cursor image for CHV pipe C cursor issue Akshu Agrawal
2016-06-08 8:40 ` Daniel Vetter
2016-06-08 10:18 ` Dave Gordon [this message]
2016-06-09 17:03 ` Daniel Vetter
2016-06-10 9:44 ` Agrawal, Akshu
2016-06-13 14:22 ` Daniel Vetter
2016-06-27 9:09 ` Shobhit Kumar
2016-06-28 12:27 ` [RFC] drm/i915/chv: Clip cursor for CHV pipe C HW Cursor pos < 0 Shobhit Kumar
2016-06-28 12:32 ` Shobhit Kumar
2016-06-29 12:54 ` [RFC v2] " Shobhit Kumar
2016-06-29 13:02 ` Shobhit Kumar
2016-07-01 8:00 ` Shobhit Kumar
2016-07-08 9:01 ` Shobhit Kumar
2016-06-08 8:51 ` [PATCH 2/2] drm/i915: Crop cursor image for CHV pipe C cursor issue kbuild test robot
2016-06-08 11:09 ` kbuild test robot
2016-06-08 8:31 ` ✗ Ro.CI.BAT: failure for series starting with [1/2] Revert "drm/i915: Workaround CHV pipe C cursor fail" Patchwork
2016-06-28 13:04 ` ✗ Ro.CI.BAT: failure for series starting with [1/2] Revert "drm/i915: Workaround CHV pipe C cursor fail" (rev2) Patchwork
2016-06-29 13:20 ` ✓ Ro.CI.BAT: success for series starting with [1/2] Revert "drm/i915: Workaround CHV pipe C cursor fail" (rev3) Patchwork
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=5757F111.2020801@intel.com \
--to=david.s.gordon@intel.com \
--cc=akshu.agrawal@intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
/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