From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 77009] 24P playback video signal loss with latest DRI patches
Date: Thu, 10 Apr 2014 14:00:45 +0000 [thread overview]
Message-ID: <bug-77009-502-gbmfrYb0bi@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-77009-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1642 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=77009
--- Comment #29 from Garrett <socalfisher@gmail.com> ---
(In reply to comment #28)
> Depending on the details of their electrical implementation all PLLs behave
> more or less like this. The trick is to know how to find the right numbers
> without violating the contrains.
yup.. This is a fun one to deal with in the embedded environment (love that
scope.). I consider this bug fixed. I am not sure if I am supposed to mark it
ok or something. Else I will leave it.
I thought about the pll thing. I don't know the HDMI message layer at all. I
am not sure it is public knowledge anyhow.
To get higher divs, I was thinking a potential algo could go (MUCH easier said
than done, I know):
1) Run a setup program each time a hardware change is detected. (EDID or GPU)
2) Test LCD/Panel at various popular refresh rates.
a) crank up the pll with your new algo.
>> *test* if tv accepted it. (requires a knowledge of protocol to
check display state, or have user answer ok with a timeout in case it is not
readable)
>> save the new div setting (maybe the 10% lower ones to be safe) to a
config with a table for that hardware/refresh.
3) on reboot load new optimized saved PLL dividers from the table. And on each
refresh rate change use the table.
But that said. It does not really matter for me to make it closer. Your new
algo with your "arbitrary" 100 limit works well on my hardware. I tested 368
and it looked great, too. 368 vs 100 on 24P made vary little difference too
me.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2522 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-04-10 14:00 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 14:56 [Bug 77009] New: 24P playback video signal loss with latest DRI patches bugzilla-daemon
2014-04-03 15:39 ` [Bug 77009] " bugzilla-daemon
2014-04-03 16:03 ` bugzilla-daemon
2014-04-03 21:06 ` bugzilla-daemon
2014-04-04 11:59 ` bugzilla-daemon
2014-04-04 12:06 ` bugzilla-daemon
2014-04-04 14:18 ` bugzilla-daemon
2014-04-04 17:45 ` bugzilla-daemon
2014-04-04 17:49 ` bugzilla-daemon
2014-04-04 17:49 ` bugzilla-daemon
2014-04-04 18:10 ` bugzilla-daemon
2014-04-05 22:44 ` bugzilla-daemon
2014-04-05 22:46 ` bugzilla-daemon
2014-04-06 4:02 ` bugzilla-daemon
2014-04-06 4:13 ` bugzilla-daemon
2014-04-06 20:59 ` bugzilla-daemon
2014-04-06 21:00 ` bugzilla-daemon
2014-04-06 21:01 ` bugzilla-daemon
2014-04-07 0:32 ` bugzilla-daemon
2014-04-07 0:37 ` bugzilla-daemon
2014-04-07 7:28 ` bugzilla-daemon
2014-04-07 7:28 ` bugzilla-daemon
2014-04-07 7:29 ` bugzilla-daemon
2014-04-07 7:29 ` bugzilla-daemon
2014-04-07 7:30 ` bugzilla-daemon
2014-04-07 7:39 ` bugzilla-daemon
2014-04-07 15:45 ` bugzilla-daemon
2014-04-08 5:01 ` bugzilla-daemon
2014-04-08 13:29 ` bugzilla-daemon
2014-04-08 14:00 ` bugzilla-daemon
2014-04-08 14:15 ` bugzilla-daemon
2014-04-08 14:31 ` bugzilla-daemon
2014-04-09 2:23 ` bugzilla-daemon
2014-04-09 12:17 ` bugzilla-daemon
2014-04-10 14:00 ` bugzilla-daemon [this message]
2014-04-11 13:41 ` bugzilla-daemon
2014-04-22 14:53 ` bugzilla-daemon
2014-05-08 19:01 ` bugzilla-daemon
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=bug-77009-502-gbmfrYb0bi@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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