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,
Neil Armstrong <neil.armstrong@linaro.org>,
Jessica Zhang <jesszhan0024@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
dri-devel@lists.freedesktop.org, jazhan@google.com
Subject: Re: [PATCH v1 1/2] drm/panel-edp: Add override bpc quirk for generic edp
Date: Thu, 30 Oct 2025 11:48:06 +0200 [thread overview]
Message-ID: <3ad3ee47f29f7b6479ec19b8fb61eee443a17264@intel.com> (raw)
In-Reply-To: <CAD=FV=X9hUxsrJ6o5yP0-bprfKgyQzZJnQRwQVYRo6G0yKWhCg@mail.gmail.com>
On Wed, 29 Oct 2025, Doug Anderson <dianders@chromium.org> wrote:
> At first I was thinking that the quirks in "drm_edid.c" were probably
> just for "DP" display, but then I just realized that they probably
> also are for "eDP" panels. Specifically I think Intel hardware doesn't
> use panel-edp.c so I think the only place quirks could get applied (if
> an eDP panel was also used on Intel hardware) was from "drm_edid.c".
>
> Any chance you could confirm if EDID_QUIRK_FORCE_6BPC works for you?
>
> Does anyone else CCed have an opinion of which they like better?
No strong opinions, but obviously having it in drm_edid.c would be more
generic. Until you encounter panels where you need to force something
other than 6 bpc, when it stops being generic and becomes an
obstacle. ;)
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-10-30 9:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 8:10 [PATCH v1 0/2] Add EDP_PANEL_ENTRY3 to override bpc Ajye Huang
2025-10-29 8:10 ` [PATCH v1 1/2] drm/panel-edp: Add override bpc quirk for generic edp Ajye Huang
2025-10-29 23:20 ` Doug Anderson
2025-10-30 8:19 ` Ajye Huang
2025-10-30 9:48 ` Jani Nikula [this message]
2025-10-30 9:44 ` Jani Nikula
2025-10-30 15:10 ` Doug Anderson
2025-10-29 8:10 ` [PATCH v1 2/2] drm/panel-edp: Modify LQ116M1JW10 panel's bpc to 6 Ajye Huang
2025-10-29 23:25 ` Doug Anderson
2025-10-30 9:57 ` Ajye Huang
2025-10-30 15:22 ` Doug Anderson
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=3ad3ee47f29f7b6479ec19b8fb61eee443a17264@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=jazhan@google.com \
--cc=jesszhan0024@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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