<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [dp] intel_dp.c:1554 WARN_ON(len <=8)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103347#c15">Comment # 15</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [dp] intel_dp.c:1554 WARN_ON(len <=8)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103347">bug 103347</a>
from <span class="vcard"><a class="email" href="mailto:shashank.sharma@intel.com" title="shashank.sharma@intel.com <shashank.sharma@intel.com>"> <span class="fn">shashank.sharma@intel.com</span></a>
</span></b>
<pre>(In reply to F.Hartung from <a href="show_bug.cgi?id=103347#c12">comment #12</a>)
<span class="quote">> I'm pretty sure it uses a LSPCON since I updated the hdmi firmware with this
> tool to 1.72
> (<a href="https://downloadcenter.intel.com/download/26609/NUCs-HDMI-2-0-Firmware">https://downloadcenter.intel.com/download/26609/NUCs-HDMI-2-0-Firmware</a>-
> Update-Tool-for-Intel-NUC-Kit-NUC6CAY-and-NUC7i3BN?product=95069)
> to solve audio issues.
>
> There is a whole thread about the problems of the Intel Apollo Lake platform
> and others with quite a similar board (J4205-ITX) report they also updated
> their hdmi firmware.
> <a href="https://forum.kodi.tv/showthread.php?tid=270298&pid=2553256#pid2553256">https://forum.kodi.tv/showthread.php?tid=270298&pid=2553256#pid2553256</a></span >
This is a different issue they are talking about, this is about getting HDR 10
bit output using HDMI 2.0 port (LSPCON), whereas this problem seems to be
basic.
<span class="quote">>
> The Apollo Lake boards use a "HDMI-2.0-LSPCon MegaChips MCDP2800", there is
> a similar chip on my board so I'm pretty sure it is an internal DP port
> mapped to the HDMI port.
>
> <a href="http://www.megachips.com/products/displayport/MCDP28x0">http://www.megachips.com/products/displayport/MCDP28x0</a></span >
MCDP2800 is a DP to HDMI converter LSPCON device, which is on-board with many
APL devices in a motherboard down mode.
<span class="quote">>
> <a href="https://www.heise.de/imgs/18/2/2/5/8/6/6/2/MegaChips-MCDP2800">https://www.heise.de/imgs/18/2/2/5/8/6/6/2/MegaChips-MCDP2800</a>-
> 903a5c8eddf6bffc-b4c059ea0025935c.jpeg
>
> <a href="https://www.heise.de/newsticker/meldung/Intel-Celeron-Gemini-Lake-mit-HDMI-2">https://www.heise.de/newsticker/meldung/Intel-Celeron-Gemini-Lake-mit-HDMI-2</a>-
> 0-und-SGX-3801532.html
> </span >
Geminilake is different from Apollolake, even though they belong to same GEN
family, GLK has a native HDMI 2.0 controller, whereas APL takes help from
LSPCON for HDMI 2.0 conversion.
<span class="quote">> I have a second TV of the same model and it's connected to my main HTPC with
> an i3-6100 & GA-B150N Phoenix-WIFI board. This combination works quite fine,
> also the logging of those messages started with kernel 4.15 so I guess it's
> related to recent patches.
>
> So all in all I'm pretty sure it's using the same lspcon & I didn't use the
> wrong system to gather information.</span ></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>