From: Carsten Behling <carsten.behling-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
To: Archit Taneja <architt-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
Cc: Carsten Behling
<carsten.behling-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Steve Kowalik <steven-6LFzBC5e86lrQi2OjOYqKQ@public.gmane.org>,
David Airlie <airlied-cv59FeDIM0c@public.gmane.org>,
Daniel Vetter <daniel.vetter-/w4YWyX8dFk@public.gmane.org>,
linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Maarten Lankhorst
<maarten.lankhorst-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
Rob Clark <robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Sean Paul <seanpaul-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
Viresh Kumar
<viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH v2] drm/msm/display: negative x/y in cursor move
Date: Wed, 25 Jul 2018 17:10:05 +0200 [thread overview]
Message-ID: <CAPuGWB9oBN4U6OS8FLDQ1m6eO3n4mT-UG3QWHdjuM9XgSLG8iQ@mail.gmail.com> (raw)
In-Reply-To: <99e72f0c-e753-cff9-9a58-50d919d472a5-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 7278 bytes --]
Hi,
> Thanks for the patch. Could you tell how to reproduce this issue
> on a db410c?
>
> I was playing with xrandr's --rotate and --reflect options to get
> a rotated output, but wasn't able to generate negative x/y
> co-ordinates. I'm using linaro's debian userspace, running lxqt.
I used Yocto Rocko from 96Boards
https://github.com/96boards/oe-rpb-manifest/tree/rocko
MACHINE=dragonboard-410c
DISTRO=rpb
rpb-desktop-image
Connect HDMI monitor and USB mouse, then
1.) Just boot. Wait for X-Server up.
2.) From my serial console:
DISPLAY=:0.0 xrandr -o 2
3.) Try to move the mouse to the upper (the rotated lower) border.
Interesting to know that your debian user space is ok. The yocto X11
configuration is very basic.
There may be a X11 configuration or extension that does the trick on Debian.
Therefore, I asked the X11 people where to fix:
https://www.spinics.net/lists/xorg/msg58969.html
Best regards
-Carsten
2018-07-24 19:33 GMT+02:00 Archit Taneja <architt-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>:
> Hi,
>
> On Tuesday 17 July 2018 04:33 AM, Carsten Behling wrote:
>
>> modesetting X11 driver may provide negative x/y cordinates in
>> mdp5_crtc_cursor_move call when rotation is enabled.
>>
>> Cursor buffer can overlap down to its negative width/height.
>>
>> ROI has to be recalculated for negative x/y indicating using the
>> lower/right corner of the cursor buffer and hotspot must be set
>> in MDP5_LM_CURSOR_XY_SRC_Y MDP5_LM_CURSOR_XY_SRC_X.
>>
>
> Thanks for the patch. Could you tell how to reproduce this issue
> on a db410c?
>
> I was playing with xrandr's --rotate and --reflect options to get
> a rotated output, but wasn't able to generate negative x/y
> co-ordinates. I'm using linaro's debian userspace, running lxqt.
>
> Thanks,
> Archit
>
>
>
>> Signed-off-by: Carsten Behling <carsten.behling-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>> ---
>> Changes in v2:
>> - fixed format specifier in debug message
>>
>> drivers/gpu/drm/msm/disp/mdp5/mdp5_crtc.c | 51
>> ++++++++++++++++++++++++++-----
>> 1 file changed, 43 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/msm/disp/mdp5/mdp5_crtc.c
>> b/drivers/gpu/drm/msm/disp/mdp5/mdp5_crtc.c
>> index 10271359789e..a7f4a6688fec 100644
>> --- a/drivers/gpu/drm/msm/disp/mdp5/mdp5_crtc.c
>> +++ b/drivers/gpu/drm/msm/disp/mdp5/mdp5_crtc.c
>> @@ -65,7 +65,7 @@ struct mdp5_crtc {
>> struct drm_gem_object *scanout_bo;
>> uint64_t iova;
>> uint32_t width, height;
>> - uint32_t x, y;
>> + int x, y;
>> } cursor;
>> };
>> #define to_mdp5_crtc(x) container_of(x, struct mdp5_crtc, base)
>> @@ -760,20 +760,31 @@ static void get_roi(struct drm_crtc *crtc, uint32_t
>> *roi_w, uint32_t *roi_h)
>> * Cursor Region Of Interest (ROI) is a plane read from cursor
>> * buffer to render. The ROI region is determined by the
>> visibility of
>> * the cursor point. In the default Cursor image the cursor point
>> will
>> - * be at the top left of the cursor image, unless it is specified
>> - * otherwise using hotspot feature.
>> + * be at the top left of the cursor image.
>> *
>> + * Without rotation:
>> * If the cursor point reaches the right (xres - x <
>> cursor.width) or
>> * bottom (yres - y < cursor.height) boundary of the screen, then
>> ROI
>> * width and ROI height need to be evaluated to crop the cursor
>> image
>> * accordingly.
>> * (xres-x) will be new cursor width when x > (xres -
>> cursor.width)
>> * (yres-y) will be new cursor height when y > (yres -
>> cursor.height)
>> + *
>> + * With rotation:
>> + * We get negative x and/or y coordinates.
>> + * (cursor.width - abs(x)) will be new cursor width when x < 0
>> + * (cursor.height - abs(y)) will be new cursor width when y < 0
>> */
>> - *roi_w = min(mdp5_crtc->cursor.width, xres -
>> + if (mdp5_crtc->cursor.x >= 0)
>> + *roi_w = min(mdp5_crtc->cursor.width, xres -
>> mdp5_crtc->cursor.x);
>> - *roi_h = min(mdp5_crtc->cursor.height, yres -
>> + else
>> + *roi_w = mdp5_crtc->cursor.width -
>> abs(mdp5_crtc->cursor.x);
>> + if (mdp5_crtc->cursor.y >= 0)
>> + *roi_h = min(mdp5_crtc->cursor.height, yres -
>> mdp5_crtc->cursor.y);
>> + else
>> + *roi_h = mdp5_crtc->cursor.height -
>> abs(mdp5_crtc->cursor.y);
>> }
>> static void mdp5_crtc_restore_cursor(struct drm_crtc *crtc)
>> @@ -783,7 +794,7 @@ static void mdp5_crtc_restore_cursor(struct drm_crtc
>> *crtc)
>> struct mdp5_kms *mdp5_kms = get_kms(crtc);
>> const enum mdp5_cursor_alpha cur_alpha = CURSOR_ALPHA_PER_PIXEL;
>> uint32_t blendcfg, stride;
>> - uint32_t x, y, width, height;
>> + uint32_t x, y, src_x, src_y, width, height;
>> uint32_t roi_w, roi_h;
>> int lm;
>> @@ -800,6 +811,26 @@ static void mdp5_crtc_restore_cursor(struct
>> drm_crtc *crtc)
>> get_roi(crtc, &roi_w, &roi_h);
>> + /* If cusror buffer overlaps due to rotation on the
>> + * upper or left screen border the pixel offset inside
>> + * the cursor buffer of the ROI is the positive overlap
>> + * distance.
>> + */
>> + if (mdp5_crtc->cursor.x < 0) {
>> + src_x = abs(mdp5_crtc->cursor.x);
>> + x = 0;
>> + } else {
>> + src_x = 0;
>> + }
>> + if (mdp5_crtc->cursor.y < 0) {
>> + src_y = abs(mdp5_crtc->cursor.y);
>> + y = 0;
>> + } else {
>> + src_y = 0;
>> + }
>> + DBG("%s: x=%u, y=%u roi_w=%u roi_h=%u src_x=%u src_y=%u",
>> + crtc->name, x, y, roi_w, roi_h, src_x, src_y);
>> +
>> mdp5_write(mdp5_kms, REG_MDP5_LM_CURSOR_STRIDE(lm), stride);
>> mdp5_write(mdp5_kms, REG_MDP5_LM_CURSOR_FORMAT(lm),
>> MDP5_LM_CURSOR_FORMAT_FORMAT(C
>> URSOR_FMT_ARGB8888));
>> @@ -812,6 +843,9 @@ static void mdp5_crtc_restore_cursor(struct drm_crtc
>> *crtc)
>> mdp5_write(mdp5_kms, REG_MDP5_LM_CURSOR_START_XY(lm),
>> MDP5_LM_CURSOR_START_XY_Y_START(y) |
>> MDP5_LM_CURSOR_START_XY_X_START(x));
>> + mdp5_write(mdp5_kms, REG_MDP5_LM_CURSOR_XY(lm),
>> + MDP5_LM_CURSOR_XY_SRC_Y(src_y) |
>> + MDP5_LM_CURSOR_XY_SRC_X(src_x));
>> mdp5_write(mdp5_kms, REG_MDP5_LM_CURSOR_BASE_ADDR(lm),
>> mdp5_crtc->cursor.iova);
>> @@ -932,8 +966,9 @@ static int mdp5_crtc_cursor_move(struct drm_crtc
>> *crtc, int x, int y)
>> if (unlikely(!crtc->state->enable))
>> return 0;
>> - mdp5_crtc->cursor.x = x = max(x, 0);
>> - mdp5_crtc->cursor.y = y = max(y, 0);
>> + /* accept negative x/y coordinates up to maximum cursor overlap */
>> + mdp5_crtc->cursor.x = x = max(x, -(int)mdp5_crtc->cursor.width);
>> + mdp5_crtc->cursor.y = y = max(y, -(int)mdp5_crtc->cursor.height);
>> get_roi(crtc, &roi_w, &roi_h);
>>
>>
>
[-- Attachment #1.2: Type: text/html, Size: 10773 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Freedreno mailing list
Freedreno@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/freedreno
next prev parent reply other threads:[~2018-07-25 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 17:49 [PATCH] drm/msm/display: negative x/y in cursor move Carsten Behling
2018-07-16 22:06 ` kbuild test robot
[not found] ` <201807170504.KBRX6Bew%fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2018-07-16 23:03 ` [PATCH v2] " Carsten Behling
[not found] ` <20180716230314.3527-1-carsten.behling-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-07-24 17:33 ` Archit Taneja
[not found] ` <99e72f0c-e753-cff9-9a58-50d919d472a5-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-07-25 15:10 ` Carsten Behling [this message]
[not found] ` <CAPuGWB9oBN4U6OS8FLDQ1m6eO3n4mT-UG3QWHdjuM9XgSLG8iQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-07-26 7:25 ` Archit Taneja
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=CAPuGWB9oBN4U6OS8FLDQ1m6eO3n4mT-UG3QWHdjuM9XgSLG8iQ@mail.gmail.com \
--to=carsten.behling-gm/ye1e23mwn+bqq9rbeug@public.gmane.org \
--cc=airlied-cv59FeDIM0c@public.gmane.org \
--cc=architt-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=carsten.behling-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=daniel.vetter-/w4YWyX8dFk@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=maarten.lankhorst-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=seanpaul-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=steven-6LFzBC5e86lrQi2OjOYqKQ@public.gmane.org \
--cc=viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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;
as well as URLs for NNTP newsgroup(s).