<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [BYT][VLV] No picture on DSI display after DRM loads on Teclast X80H tablet"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96996#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [BYT][VLV] No picture on DSI display after DRM loads on Teclast X80H tablet"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96996">bug 96996</a>
from <span class="vcard"><a class="email" href="mailto:laszlo.fiat@gmail.com" title="Laszlo Fiat <laszlo.fiat@gmail.com>"> <span class="fn">Laszlo Fiat</span></a>
</span></b>
<pre>Created <span class=""><a href="attachment.cgi?id=128654" name="attach_128654" title="Dmesg of drm-tip 2016-12-22, no WARNING, but still blank screen">attachment 128654</a> <a href="attachment.cgi?id=128654&action=edit" title="Dmesg of drm-tip 2016-12-22, no WARNING, but still blank screen">[details]</a></span>
Dmesg of drm-tip 2016-12-22, no WARNING, but still blank screen
The patches make the WARNING go away, but the screen still stays blank after
modeset.
Just a wild guess: this may be a gpio issue like what Hans fixed with his patch
[1] for CHT, but this is VLV.
This tablet has a DollarCove pmic (AXP288), so this is not CrystalCove. The
Android kernel code handled this pmic in intel_soc_pmic, while mainline has is
in axp20x (in a really bad shape). Hans created some patches for it, but they
are not in linux-next yet. This may, or may not be relevant for panel handling.
[1]:
<a href="https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/gpu/drm/i915?id=22ca0d4991169b76e753d767a45f1105c356bbb8">https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/gpu/drm/i915?id=22ca0d4991169b76e753d767a45f1105c356bbb8</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>