From: Hamza Mahfooz <hamza.mahfooz@amd.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Maxime Ripard <mripard@kernel.org>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, amd-gfx@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>,
Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [PATCH] drm/edid: add 8 bpc quirk to the BenQ GW2765
Date: Fri, 13 Oct 2023 07:37:06 -0400 [thread overview]
Message-ID: <9d371f71-b7f9-4c4e-b42b-20cabaa42567@amd.com> (raw)
In-Reply-To: <ZSkcX1nJ4Ipf2ICd@intel.com>
On 10/13/23 06:30, Ville Syrjälä wrote:
> On Thu, Oct 12, 2023 at 02:49:27PM -0400, Hamza Mahfooz wrote:
>> The BenQ GW2765 reports that it supports higher (> 8) bpc modes, but
>> when trying to set them we end up with a black screen. So, limit it to 8
>> bpc modes.
>
> Bad cable/etc was ruled out as the cause?
Yup, the issue was also reproduced by two different people with same
aforementioned monitor.
>
>>
>> Cc: stable@vger.kernel.org # 6.5+
>> Link: https://gitlab.freedesktop.org/drm/amd/-/issues/2610
>> Signed-off-by: Hamza Mahfooz <hamza.mahfooz@amd.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 0454da505687..bca2af4fe1fc 100644
>> --- a/drivers/gpu/drm/drm_edid.c
>> +++ b/drivers/gpu/drm/drm_edid.c
>> @@ -123,6 +123,9 @@ static const struct edid_quirk {
>> /* AEO model 0 reports 8 bpc, but is a 6 bpc panel */
>> EDID_QUIRK('A', 'E', 'O', 0, EDID_QUIRK_FORCE_6BPC),
>>
>> + /* BenQ GW2765 */
>> + EDID_QUIRK('B', 'N', 'Q', 0x78d6, EDID_QUIRK_FORCE_8BPC),
>> +
>> /* BOE model on HP Pavilion 15-n233sl reports 8 bpc, but is a 6 bpc panel */
>> EDID_QUIRK('B', 'O', 'E', 0x78b, EDID_QUIRK_FORCE_6BPC),
>>
>> --
>> 2.42.0
>
--
Hamza
prev parent reply other threads:[~2023-10-13 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 18:49 Hamza Mahfooz
2023-10-12 20:55 ` Harry Wentland
2023-10-13 10:30 ` Ville Syrjälä
2023-10-13 11:37 ` Hamza Mahfooz [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=9d371f71-b7f9-4c4e-b42b-20cabaa42567@amd.com \
--to=hamza.mahfooz@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tzimmermann@suse.de \
--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
all inboxes | Powered by JetHome®