From: Mario Kleiner <mario.kleiner.de@gmail.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
stable <stable@vger.kernel.org>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Mario Kleiner" <mario.kleiner.de@gmail.com>
Subject: Re: [PATCH 1/2] drm/i915/dp: Revert "drm/i915/dp: fall back to 18 bpp when sink capability is unknown"
Date: Tue, 14 Jun 2016 16:12:03 +0200 [thread overview]
Message-ID: <576010B3.4020904@gmail.com> (raw)
In-Reply-To: <CAKMK7uGMQ=Vd6UZnLG4HKMuJR=AoBXbcgfQXf5KkHQR2Aa1S4w@mail.gmail.com>
On 06/14/2016 01:05 PM, Daniel Vetter wrote:
> On Thu, May 26, 2016 at 4:39 PM, Mario Kleiner
> <mario.kleiner.de@gmail.com> wrote:
>> This reverts commit 013dd9e03872
>> ("drm/i915/dp: fall back to 18 bpp when sink capability is unknown")
>>
>> This commit introduced a regression into stable kernels,
>> as it reduces output color depth to 6 bpc for any video
>> sink connected to a Displayport connector if that sink
>> doesn't report a specific color depth via EDID, or if
>> our EDID parser doesn't actually recognize the proper
>> bpc from EDID.
>>
>> Affected are active DisplayPort->VGA converters and
>> active DisplayPort->DVI converters. Both should be
>> able to handle 8 bpc, but are degraded to 6 bpc with
>> this patch.
>>
>> The reverted commit was meant to fix
>> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=105331
>>
>> A followup patch implements a fix for that specific bug,
>> which is caused by a faulty EDID of the affected DP panel
>> by adding a new EDID quirk for that panel.
>>
>> DP 18 bpp fallback handling and other improvements to
>> DP sink bpc detection will be handled for future
>> kernels in a separate series of patches.
>>
>> Please backport to stable.
>>
>> Signed-off-by: Mario Kleiner <mario.kleiner.de@gmail.com>
>> Acked-by: Jani Nikula <jani.nikula@intel.com>
>> Cc: stable@vger.kernel.org
>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
>
> I wonder whether we shouldn't just move this into the DP code, and
> instead of looking at the edid (which is just pass-through for dp->vga
> dongles) we should only look at dpcd values? Or maybe only look at the
> edid value if the sink is native DP, and not when it's a dongle.
>
> That would probably also avoid the quirk, and that quirk seems a bit fishy.
> -Daniel
>
This patch is just a simple fix for the color depth regression which
affects stable kernels. It can be back-ported easily to affected stable
kernels, as Jani advised me.
I wanted to clean up and resubmit that DP helper function which looks at
dpcd values and might be a bit too much for stable, once this fix is in.
-mario
next prev parent reply other threads:[~2016-06-14 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 14:39 EDID/DP color precision fixes on Intel hw for stable (v2) Mario Kleiner
2016-05-26 14:39 ` [PATCH 1/2] drm/i915/dp: Revert "drm/i915/dp: fall back to 18 bpp when sink capability is unknown" Mario Kleiner
2016-06-14 11:05 ` Daniel Vetter
2016-06-14 14:12 ` Mario Kleiner [this message]
2016-06-21 15:48 ` Mario Kleiner
2016-05-26 14:39 ` [PATCH 2/2] drm/edid: Add 6 bpc quirk for display AEO model 0 Mario Kleiner
2016-06-14 10:44 ` Ville Syrjälä
2016-06-14 14:05 ` Mario Kleiner
[not found] ` <575AE8D9.2090001@gmail.com>
2016-06-10 16:40 ` EDID/DP color precision fixes on Intel hw for stable (v2) Daniel Vetter
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=576010B3.4020904@gmail.com \
--to=mario.kleiner.de@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=stable@vger.kernel.org \
--cc=ville.syrjala@linux.intel.com \
/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