public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mario Kleiner <mario.kleiner.de@gmail.com>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>, airlied@linux.ie
Cc: daniel.vetter@intel.com, gustavo@padovan.org,
	seanpaul@chromium.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/edid: Add 6 bpc quirk for CPT panel in Asus UX303LA
Date: Sun, 18 Feb 2018 13:17:25 +0100	[thread overview]
Message-ID: <d6a3afcb-91e5-dc91-7374-50f4864d7f2f@gmail.com> (raw)
In-Reply-To: <20180218085359.7817-1-kai.heng.feng@canonical.com>

On 02/18/2018 09:53 AM, Kai-Heng Feng wrote:
> Similar to commit e10aec652f31 ("drm/edid: Add 6 bpc quirk for display
> AEO model 0."), the EDID reports "DFP 1.x compliant TMDS" but it support
> 6bpc instead of 8 bpc.
> 
> Hence, use 6 bpc quirk for this panel.
> 
> Fixes: 196f954e2509 ("drm/i915/dp: Revert "drm/i915/dp: fall back to 18 bpp when sink capability is unknown"")
> BugLink: https://bugs.launchpad.net/bugs/1749420
> Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
> ---
>   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 ddd537914575..d9c8d718e261 100644
> --- a/drivers/gpu/drm/drm_edid.c
> +++ b/drivers/gpu/drm/drm_edid.c
> @@ -113,6 +113,9 @@ static const struct edid_quirk {
>   	/* AEO model 0 reports 8 bpc, but is a 6 bpc panel */
>   	{ "AEO", 0, EDID_QUIRK_FORCE_6BPC },
>   
> +	/* CPT panel of Asus UX303LA reports 8 bpc, but is a 6 bpc panel */
> +	{ "CPT", 0x17df, EDID_QUIRK_FORCE_6BPC },
> +
>   	/* Belinea 10 15 55 */
>   	{ "MAX", 1516, EDID_QUIRK_PREFER_LARGE_60 },
>   	{ "MAX", 0x77e, EDID_QUIRK_PREFER_LARGE_60 },
> 

Reviewed-by: Mario Kleiner <mario.kleiner.de@gmail.com>

  reply	other threads:[~2018-02-18 12:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-18  8:53 [PATCH] drm/edid: Add 6 bpc quirk for CPT panel in Asus UX303LA Kai-Heng Feng
2018-02-18 12:17 ` Mario Kleiner [this message]
2018-02-19 10:42 ` Jani Nikula

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=d6a3afcb-91e5-dc91-7374-50f4864d7f2f@gmail.com \
    --to=mario.kleiner.de@gmail.com \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gustavo@padovan.org \
    --cc=kai.heng.feng@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seanpaul@chromium.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