From: Jani Nikula <jani.nikula@intel.com>
To: Doug Anderson <dianders@chromium.org>,
Ajye Huang <ajye_huang@compal.corp-partner.google.com>
Cc: linux-kernel@vger.kernel.org,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v1] drm/edid: add 6 bpc quirk to the Sharp LQ116M1JW10
Date: Fri, 31 Oct 2025 12:40:07 +0200 [thread overview]
Message-ID: <789d88744fbd3a05758971dc8d893fb4599475f3@intel.com> (raw)
In-Reply-To: <7071a2b8198c09011c84d39b45dc6d1da4b69d12@intel.com>
On Fri, 31 Oct 2025, Jani Nikula <jani.nikula@intel.com> wrote:
> On Thu, 30 Oct 2025, Doug Anderson <dianders@chromium.org> wrote:
>> Hi,
>>
>> On Thu, Oct 30, 2025 at 2:44 AM Ajye Huang
>> <ajye_huang@compal.corp-partner.google.com> wrote:
>>>
>>> The Sharp LQ116M1JW105 reports that it supports 8 bpc modes,
>>> but it will happen display noise in some videos.
>>> So, limit it to 6 bpc modes.
>>>
>>> Signed-off-by: Ajye Huang <ajye_huang@compal.corp-partner.google.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 e2e85345aa9a..a73d37fe7ea1 100644
>>> --- a/drivers/gpu/drm/drm_edid.c
>>> +++ b/drivers/gpu/drm/drm_edid.c
>>> @@ -250,6 +250,9 @@ static const struct edid_quirk {
>>> EDID_QUIRK('S', 'V', 'R', 0x1019, BIT(EDID_QUIRK_NON_DESKTOP)),
>>> EDID_QUIRK('A', 'U', 'O', 0x1111, BIT(EDID_QUIRK_NON_DESKTOP)),
>>>
>>> + /* LQ116M1JW10 displays noise when 8 bpc, but display fine as 6 bpc */
>>> + EDID_QUIRK('S', 'H', 'P', 0x154c, EDID_QUIRK_FORCE_6BPC),
>>
>> Reviewed-by: Douglas Anderson <dianders@chromium.org>
>
> FWIW,
>
> Acked-by: Jani Nikula <jani.nikula@intel.com>
And as soon as I hit send, I notice the quirk is missing BIT(). It's a
bit mask, and the enum signifies the bit number.
BR,
Jani.
>
>>
>> I'll plan to apply this patch next week unless there are any comments.
>> Given that it's just adding a quirk, I'm also happy to apply it
>> soonner (or for someone else to apply it) if people think that's OK.
>> :-)
>>
>> NOTE: in general if someone is involved in the discussion of a
>> previous versoin, it's good to CC them on newer versions. I've added
>> Jani back to the CC list here.
>>
>> -Doug
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-10-31 10:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 9:44 Ajye Huang
2025-10-30 15:08 ` Doug Anderson
2025-10-30 16:31 ` Ajye Huang
2025-10-31 10:37 ` Jani Nikula
2025-10-31 10:40 ` Jani Nikula [this message]
2025-10-31 14:24 ` Doug Anderson
2025-10-31 15:35 ` Ajye Huang
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=789d88744fbd3a05758971dc8d893fb4599475f3@intel.com \
--to=jani.nikula@intel.com \
--cc=airlied@gmail.com \
--cc=ajye_huang@compal.corp-partner.google.com \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
/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®