From: Nabendu Maiti <nabendu.bikash.maiti@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Correcting proper src & dst height - width comparision for 90/270 rotation.
Date: Mon, 7 Dec 2015 23:53:51 +0530 [thread overview]
Message-ID: <5665CEB7.6040902@intel.com> (raw)
In-Reply-To: <56575204.70208@intel.com>
On 11/27/2015 12:10 AM, Nabendu Maiti wrote:
>
>
> On 11/18/2015 05:44 PM, Ville Syrjälä wrote:
>> On Wed, Nov 18, 2015 at 05:19:26PM +0530, Nabendu Maiti wrote:
>>> On 90/270 rotation case source width and height was not compared
>>> properly with destination height and width check plane.Which added
>>> erroneous check while doing scaling or normal 90/270 rotation.
>>>
>>> Signed-off-by: Nabendu Maiti <nabendu.bikash.maiti@intel.com>
>>> ---
>>> drivers/gpu/drm/i915/intel_display.c | 22 ++++++++++++++++++++--
>>> 1 file changed, 20 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/i915/intel_display.c
>>> b/drivers/gpu/drm/i915/intel_display.c
>>> index 688d484..cd5bb28 100644
>>> --- a/drivers/gpu/drm/i915/intel_display.c
>>> +++ b/drivers/gpu/drm/i915/intel_display.c
>>> @@ -13723,6 +13723,9 @@ intel_check_primary_plane(struct drm_plane
>>> *plane,
>>> int min_scale = DRM_PLANE_HELPER_NO_SCALING;
>>> int max_scale = DRM_PLANE_HELPER_NO_SCALING;
>>> bool can_position = false;
>>> + struct drm_rect *src = &state->src;
>>> + struct drm_rect *dest = &state->dst;
>>> + int ret = -1;
>>> /* use scaler when colorkey is not required */
>>> if (INTEL_INFO(plane->dev)->gen >= 9 &&
>>> @@ -13732,11 +13735,26 @@ intel_check_primary_plane(struct drm_plane
>>> *plane,
>>> can_position = true;
>>> }
>>> - return drm_plane_helper_check_update(plane, crtc, fb,
>>> &state->src,
>>> - &state->dst, &state->clip,
>>> + /*
>>> + * FIXME the following code does a bunch of fuzzy adjustments
>>> to the
>>> + * coordinates and sizes for rotations. We probably need some
>>> way to
>>> + * decide whether more strict checking should be done instead.
>>> + */
>>> + if (fb)
>>> + drm_rect_rotate(src, fb->width << 16, fb->height << 16,
>>> + state->base.rotation);
>>> +
>>> + ret = drm_plane_helper_check_update(plane, crtc, fb, src,
>>> + dest, &state->clip,
>>> min_scale, max_scale,
>>> can_position, true,
>>> &state->visible);
>>> +
>>> + /* Restore the originl unrotated co-ordinates */
>>> + if (fb)
>>> + drm_rect_rotate_inv(src, fb->width << 16, fb->height << 16,
>>> + state->base.rotation);
>>
>> We should put the rotation handling into helper. And someone should
>> really just move all the good code from intel_sprite into the helper
>> instead of having two totally different ways of doing things.
> Yes right.I learned that there is an effort going on unification of
> primary and sprite plane. To put this in helper function is a bigger
> modifications .
> In the meantime in android we need this fix. So if you suggest I will
> hold the patch until the unification completes anf float it once again
> if required.
Any update on this patch or unification patch?
>>
>>> + return ret;
>>> }
>>> static void
>>> --
>>> 1.9.1
>>>
>>> _______________________________________________
>>> Intel-gfx mailing list
>>> Intel-gfx@lists.freedesktop.org
>>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-12-07 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 11:49 [PATCH] drm/i915: Correcting proper src & dst height - width comparision for 90/270 rotation Nabendu Maiti
2015-11-18 12:14 ` Ville Syrjälä
2015-11-26 18:40 ` Nabendu Maiti
2015-12-07 18:23 ` Nabendu Maiti [this message]
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=5665CEB7.6040902@intel.com \
--to=nabendu.bikash.maiti@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--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