linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: Pavel Machek <pavel@ucw.cz>, Alex Deucher <alexdeucher@gmail.com>
Cc: "Deucher, Alexander" <alexander.deucher@amd.com>,
	"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
	"kernel list" <linux-kernel@vger.kernel.org>,
	"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>,
	"Christian König" <christian.koenig@amd.com>
Subject: Re: Mobility Radeon HD 4530/4570/545v: flicker in 1920x1080
Date: Fri, 06 Nov 2015 02:25:09 +0000	[thread overview]
Message-ID: <563C0F85.8070204@daenzer.net> (raw)
In-Reply-To: <20151105202301.GA3624@amd>

On 06.11.2015 05:23, Pavel Machek wrote:
> Hi!
> 
>>>> The flickering would vanish completely if that's the reason for the issue
>>>> you are seeing.
>>>
>>>> Try setting ref_div_min and ref_div_max to 2 in
>>>>  radeon_compute_pll_avivo().
>>>
>>> Ok, I did this, but no luck, still flickers. But the flicker only
>>> happens when something changes on screen, like dragging a big
>>> window. Is that consistent with wrong PLL timings?
>>
>> Does it go away with radeon.dpm=0?  Sounds more like either memory
>> reclocking happening outside of vblank, or underflow to the display
>> controllers.
> 
> No, it does not:
> 
> pavel@half:~$ cat /proc/cmdline
> BOOT_IMAGE=(hd0,2)/l/linux/arch/x86/boot/bzImage root=/dev/sda4
> resume=/dev/sda1 radeon.dpm=0
> 
> ..and same issue. And yes, it looks like an underflow to me. How can I
> debug reclocking / underflows?

Does radeon.disp_priority=2 help?


-- 
Earthling Michel Dänzer               |               http://www.amd.com
Libre software enthusiast             |             Mesa and X developer

  reply	other threads:[~2015-11-06  2:25 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
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 [this message]
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=563C0F85.8070204@daenzer.net \
    --to=michel@daenzer.net \
    --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 \
    --cc=pavel@ucw.cz \
    /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).