All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mario Kleiner <mario.kleiner.de@gmail.com>
To: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Cc: Jani Nikula <jani.nikula@intel.com>,
	Dave Airlie <airlied@redhat.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Fwd: EDID/DP fixes for proper bpc detection of displays.
Date: Sat, 30 Jul 2016 17:08:03 +0200	[thread overview]
Message-ID: <dfe9dbbf-155f-b933-0eca-0b9bc1d5ff98@gmail.com> (raw)
In-Reply-To: <1467799548-13229-1-git-send-email-mario.kleiner.de@gmail.com>

Three weeks have passed, so resending. Could i maybe excite somebody to 
review/merge at least some of the really trivial but important patches 
to fix regressions back-ported to all stable kernels, mostly in Intel 
kms + DP legacy in this series before the 4.8 merge window closes?

Especially patch 2, "[PATCH 2/5] drm/i915/dp: Revert "drm/i915/dp: fall 
back to 18 bpp when sink capability is unknown" a revert acked by Jani 
for a patch of him, and patch 5 "[PATCH 5/5] drm/edid: Set 8 bpc color 
depth for displays with "DFP 1.x compliant TMDS"?

Patch 5/5 would make our EDID parsing for DVI more complete and if also 
back-ported to stable would at least prevent the worst fallout for 
current users if patch 2/5 doesn't get applied.

thanks,
-mario

-------- Forwarded Message --------
Subject: EDID/DP fixes for proper bpc detection of displays.
Date: Wed,  6 Jul 2016 12:05:43 +0200
From: Mario Kleiner <mario.kleiner.de@gmail.com>
To: dri-devel@lists.freedesktop.org
CC: mario.kleiner.de@gmail.com

Updated series to fix the regressions introduced into stable
kernels for active Displayport to dual-link DVI converters and
for active Displayport to VGA converters. Also to fix this stuff
better for Linux 4.8.

Patch 1 + 2 are needed to fix the regressions in the stable
kernels. These are meant for easy backporting to all affected
kernels.

Patch 3: A DP helper for parsing sink bpc from DP aux data to
assist drivers if they can't get bpc from EDID.

Patch 4: Make intel kms use patch 3.

Patch 5: Make the EDID parser recognize the "DFP1.x compatible TMDS"
bit by which DVI sinks can declare they support at least 8 bpc according
to DFP spec. This one if applied would let me sleep so much better, as
the common special display equipment for neuroscience research, which is
all DVI based atm., sets that bit in its EDID 1.3.

Thanks,
-mario

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2016-07-30 15:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-06 10:05 EDID/DP fixes for proper bpc detection of displays Mario Kleiner
2016-07-06 10:05 ` [PATCH 1/5] drm/edid: Add 6 bpc quirk for display AEO model 0 Mario Kleiner
2016-07-06 10:05   ` Mario Kleiner
2016-07-06 10:05 ` [PATCH 2/5] drm/i915/dp: Revert "drm/i915/dp: fall back to 18 bpp when sink capability is unknown" Mario Kleiner
2016-07-06 10:05   ` Mario Kleiner
2016-07-06 10:05 ` [PATCH 3/5] drm/dp: Add helper to find bpc of a connected DP sink Mario Kleiner
2016-07-06 10:05 ` [PATCH 4/5] drm/intel/dp: Try harder to get bpc of a DP sink if EDID doesn't tell Mario Kleiner
2016-08-03  3:07   ` Dave Airlie
2016-08-03  6:09     ` Daniel Vetter
2016-08-03 12:03       ` Mario Kleiner
2016-08-07 16:10         ` Mario Kleiner
2016-07-06 10:05 ` [PATCH 5/5] drm/edid: Set 8 bpc color depth for displays with "DFP 1.x compliant TMDS" Mario Kleiner
2016-07-30 15:08 ` Mario Kleiner [this message]
2016-08-02 13:16   ` Fwd: EDID/DP fixes for proper bpc detection of displays 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=dfe9dbbf-155f-b933-0eca-0b9bc1d5ff98@gmail.com \
    --to=mario.kleiner.de@gmail.com \
    --cc=airlied@redhat.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jani.nikula@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.