From: Pavel Machek <pavel@ucw.cz>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: "Deucher, Alexander" <alexander.deucher@amd.com>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
"Christian König" <christian.koenig@amd.com>,
"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>,
"kernel list" <linux-kernel@vger.kernel.org>
Subject: Re: Mobility Radeon HD 4530/4570/545v: flicker in 1920x1080
Date: Tue, 03 Nov 2015 23:03:30 +0000 [thread overview]
Message-ID: <20151103230329.GA4167@amd> (raw)
In-Reply-To: <CADnq5_P8TOQ14NiWKgV-YUy0_8P+K842pZ4h7WuU6XBu4o9fyQ@mail.gmail.com>
Hi!
> >> >> >Any ideas?
> >> >>
> >> >> Alex probably knows more about this, but it sounds like problems with
> >> >> switching the memory clocks on 3D load.
> >> >
> >> >> Try to disable power management completely with radeon.dpm=0 on the kernel
> >> >> command line or nailing the hardware at a specific power level using
> >> >> sysfs.
> >> >
> >> > I tried that, but it still flickers.
> >>
> >> It's probably pll stability. There seem to be a number of regressions
> >> since the pll code was rewritten to support matching the hdmi clocks
> >> more closely. Does this patch help?
> >>
> >> diff --git a/drivers/gpu/drm/radeon/atombios_crtc.c
> >> b/drivers/gpu/drm/radeon/atombios_crtc.c
> >> index dac78ad..b86f06a 100644
> >> --- a/drivers/gpu/drm/radeon/atombios_crtc.c
> >> +++ b/drivers/gpu/drm/radeon/atombios_crtc.c
> >> @@ -569,6 +569,8 @@ static u32 atombios_adjust_pll(struct drm_crtc *crtc,
> >> radeon_crtc->pll_flags = 0;
> >>
> >> if (ASIC_IS_AVIVO(rdev)) {
> >> + radeon_crtc->pll_flags |= RADEON_PLL_PREFER_MINM_OVER_MAXP;
> >> +
> >> if ((rdev->family = CHIP_RS600) ||
> >> (rdev->family = CHIP_RS690) ||
> >> (rdev->family = CHIP_RS740))
> >>
> >
> > Help.. maybe... it is tricky to tell. It definitely does _not_ fix the
> > issue completely.
>
> You could also try the old pll algorithm:
I reverted the patch above, and switched to the old algorithm.
The flicker is still there. (But maybe its less horrible, like with
RADEON_PLL_PREFER_MINM_OVER_MAXP).
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2015-11-03 23:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-31 20:13 Mobility Radeon HD 4530/4570/545v: flicker in 1920x1080 Pavel Machek
2015-10-31 20:21 ` Christian König
2015-10-31 21:22 ` Pavel Machek
2015-11-02 15:20 ` Alex Deucher
2015-11-03 22:09 ` Pavel Machek
2015-11-03 22:25 ` Alex Deucher
2015-11-03 23:03 ` Pavel Machek [this message]
2015-11-04 7:36 ` Christian König
2015-11-04 22:10 ` Pavel Machek
2015-11-04 22:13 ` Alex Deucher
2015-11-05 10:43 ` Christian König
2015-11-05 20:26 ` Pavel Machek
2015-11-05 20:23 ` Pavel Machek
2015-11-06 2:25 ` Michel Dänzer
2015-11-06 12:45 ` Pavel Machek
2015-11-03 23:15 ` Pavel Machek
2015-11-02 7:31 ` Mobility Radeon HD 4530/4570/545v: warnings Pavel Machek
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=20151103230329.GA4167@amd \
--to=pavel@ucw.cz \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).