From: Jean Delvare <jdelvare@suse.de>
To: "Y.C. Chen" <yacheng600221@gmail.com>
Cc: dri-devel@lists.freedesktop.org, airlied@redhat.com,
stable@vger.kernel.org, eich@suse.com
Subject: Re: [PATCH] drm/ast: change resolution may cause screen blurred
Date: Wed, 21 Nov 2018 15:49:03 +0100 [thread overview]
Message-ID: <20181121154903.4fe06db4@endymion> (raw)
In-Reply-To: <1538549867-1014-1-git-send-email-yc_chen@aspeedtech.com>
On Wed, 3 Oct 2018 14:57:47 +0800, Y.C. Chen wrote:
> From: "Y.C. Chen" <yc_chen@aspeedtech.com>
>
> The value of pitches is not correct while calling mode_set.
> The issue we found so far on following system:
> - Debian8 with XFCE Desktop
> - Ubuntu with KDE Desktop
> - SUSE15 with KDE Desktop
>
> Signed-off-by: Y.C. Chen <yc_chen@aspeedtech.com>
> ---
> drivers/gpu/drm/ast/ast_mode.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/ast/ast_mode.c b/drivers/gpu/drm/ast/ast_mode.c
> index 5e77d45..f06aae7 100644
> --- a/drivers/gpu/drm/ast/ast_mode.c
> +++ b/drivers/gpu/drm/ast/ast_mode.c
> @@ -568,6 +568,7 @@ static int ast_crtc_do_set_base(struct drm_crtc *crtc,
> }
> ast_bo_unreserve(bo);
>
> + ast_set_offset_reg(crtc);
> ast_set_start_address_crt1(crtc, (u32)gpu_addr);
>
> return 0;
Tested-by: Jean Delvare <jdelvare@suse.de>
Reviewed-by: Jean Delvare <jdelvare@suse.de>
I did experience the mentioned display corruption on resolution change
on an ASPEED 1100/2050 chipset, under Plasma (KDE). I can confirm that
the patch above prevents it.
There is also a report in openSUSE's bugzilla:
https://bugzilla.opensuse.org/show_bug.cgi?id=1112963
where the user tested the patch above successfully on an ASPEED 2500
chipset.
Can we get the fix merged now?
Thanks,
--
Jean Delvare
SUSE L3 Support
prev parent reply other threads:[~2018-11-22 1:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 6:57 [PATCH] drm/ast: change resolution may cause screen blurred Y.C. Chen
2018-10-03 9:22 ` Daniel Vetter
2018-11-21 14:49 ` Jean Delvare [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=20181121154903.4fe06db4@endymion \
--to=jdelvare@suse.de \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eich@suse.com \
--cc=stable@vger.kernel.org \
--cc=yacheng600221@gmail.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