Re: [PATCH] drm/radeon: Always store CRTC relative radeon_crtc->cursor_x/y values

[Greg KH <greg@kroah.com>]

On Tue, Jan 10, 2017 at 03:40:12PM +0900, Michel D�nzer wrote:
> From: Michel D�nzer <michel.daenzer@amd.com>
> 
> commit 4349bd775cc8fd75cb648e3a2036a690f497de5c upstream.
> 
> We were storing viewport relative coordinates for AVIVO/DCE display
> engines. However, radeon_crtc_cursor_set2 and radeon_cursor_reset pass
> radeon_crtc->cursor_x/y as the x/y parameters of
> radeon_cursor_move_locked, which would break if the CRTC isn't located
> at (0, 0).
> 
> Cc: stable@vger.kernel.org
> Signed-off-by: Michel D�nzer <michel.daenzer@amd.com>
> Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> ---
> 
> This is a backport for the 4.9 and possibly older stable branches.
> 
> BTW, this manual backport shouldn't have been necessary if this commit
> and surrounding commits to the same file had been cherry-picked in the
> same order as they are in mainline. Maybe any scripts used for that
> could be improved accordingly.

Sorry about that, normally I work off of the patch date in order to
determine the order, but sometimes get it wrong, as is the case here, my
fault.

Many thanks for the backport, now queued up.

greg k-h