<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Weird colours on usb-c to hdmi output" href="https://bugs.freedesktop.org/show_bug.cgi?id=99137#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Weird colours on usb-c to hdmi output" href="https://bugs.freedesktop.org/show_bug.cgi?id=99137">bug 99137</a> from <a class="email" href="mailto:ville.syrjala@linux.intel.com" title="Ville Syrjala <ville.syrjala@linux.intel.com>"> Ville Syrjala</a> <pre>I'm not really sure how the DP->HDMI branch devices handle color depth. ATM we assume we can feed whatever bpc to DP sinks that are reported as supported in DPCD. But if the DP->HDMI conversion doesn't do anything to adjust the bpc, then we'll be feeding that all the way to the sink. Which means we should be checking the sink capabilities as well. Currently we only check for sink deep color support, but we fail to account for the sink max TMDS clock (or the DP++ dongle max TMDS clock if we have a DP->DP++->HDMI type of setup). Also the sink should be told what the color depth is with the GCP infoframe. Whether or not that would be done automagically by the DP->HDMI device, or if we would have to send out that infoframe all the way from the source is totally left out from the DP spec. For this it would be extremely nice to see the infoframes the sink is actually receiving (doable with the chamelium?).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>