From: Daniel Vetter <daniel@ffwll.ch>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: gustavo@padovan.org, maarten.lankhorst@linux.intel.com,
sean@poorly.run, airlied@linux.ie, stable@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/edid: Add 6 bpc quirk for SDC panel in Lenovo B50-80
Date: Thu, 23 Aug 2018 10:26:19 +0200 [thread overview]
Message-ID: <20180823082618.GZ21634@phenom.ffwll.local> (raw)
In-Reply-To: <20180823055332.7723-1-kai.heng.feng@canonical.com>
On Thu, Aug 23, 2018 at 05:53:32AM +0000, Kai-Heng Feng wrote:
> Another panel that reports "DFP 1.x compliant TMDS" but it supports 6bpc
> instead of 8 bpc.
>
> Apply 6 bpc quirk for the panel to fix it.
>
> BugLink: https://bugs.launchpad.net/bugs/1788308
> Cc: <stable@vger.kernel.org> # v4.8+
> Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
Applied, thanks.
-Daniel
> ---
> drivers/gpu/drm/drm_edid.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
> index 5dc742b27ca0..3c9fc99648b7 100644
> --- a/drivers/gpu/drm/drm_edid.c
> +++ b/drivers/gpu/drm/drm_edid.c
> @@ -116,6 +116,9 @@ static const struct edid_quirk {
> /* CPT panel of Asus UX303LA reports 8 bpc, but is a 6 bpc panel */
> { "CPT", 0x17df, EDID_QUIRK_FORCE_6BPC },
>
> + /* SDC panel of Lenovo B50-80 reports 8 bpc, but is a 6 bpc panel */
> + { "SDC", 0x3652, EDID_QUIRK_FORCE_6BPC },
> +
> /* Belinea 10 15 55 */
> { "MAX", 1516, EDID_QUIRK_PREFER_LARGE_60 },
> { "MAX", 0x77e, EDID_QUIRK_PREFER_LARGE_60 },
> --
> 2.17.1
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2018-08-23 8:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 5:53 Kai-Heng Feng
2018-08-23 8:26 ` Daniel Vetter [this message]
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=20180823082618.GZ21634@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=sean@poorly.run \
--cc=stable@vger.kernel.org \
/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
all inboxes | Powered by JetHome®