From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ajye Huang <ajye_huang@compal.corp-partner.google.com>,
linux-kernel@vger.kernel.org
Cc: Douglas Anderson <dianders@chromium.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,
Ajye Huang <ajye_huang@compal.corp-partner.google.com>,
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:44:11 +0200 [thread overview]
Message-ID: <d6fe55b210888b9279c776b2bbfeaf38bfc44dcb@intel.com> (raw)
In-Reply-To: <20251029081048.162374-2-ajye_huang@compal.corp-partner.google.com>
On Wed, 29 Oct 2025, Ajye Huang <ajye_huang@compal.corp-partner.google.com> wrote:
> Adding override bpc to EDP_PANEL_ENTRY3 quirk.
>
> Signed-off-by: Ajye Huang <ajye_huang@compal.corp-partner.google.com>
> ---
> drivers/gpu/drm/panel/panel-edp.c | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/drivers/gpu/drm/panel/panel-edp.c b/drivers/gpu/drm/panel/panel-edp.c
> index 944c7c70de55..da3e8f223ec3 100644
> --- a/drivers/gpu/drm/panel/panel-edp.c
> +++ b/drivers/gpu/drm/panel/panel-edp.c
> @@ -218,6 +218,9 @@ struct edp_panel_entry {
>
> /** @override_edid_mode: Override the mode obtained by edid. */
> const struct drm_display_mode *override_edid_mode;
> +
> + /** @override_bpc: Override the Bits per color obtained by edid. */
> + unsigned int override_bpc;
> };
>
> struct panel_edp {
> @@ -586,6 +589,9 @@ static int panel_edp_get_modes(struct drm_panel *panel,
> bool has_override_edid_mode = p->detected_panel &&
> p->detected_panel != ERR_PTR(-EINVAL) &&
> p->detected_panel->override_edid_mode;
Unrelated to the patch at hand, since the pattern is there already, but
something like this should be more reliable:
bool has_override_edid_mode = !IS_ERR_OR_NULL(p->detected_panel) &&
p->detected_panel->override_edid_mode;
It does not look like p->detected_panel could have other error pointer
values than -EINVAL, but it looks awkward to check for NULL and one
error pointer value, and then go on to dereference it.
I guess even better would be to always use either NULL *or* error
pointers, not a mix, but I digress.
BR,
Jani.
> + bool has_override_bpc = p->detected_panel &&
> + p->detected_panel != ERR_PTR(-EINVAL) &&
> + p->detected_panel->override_bpc;
>
> /* probe EDID if a DDC bus is available */
> if (p->ddc) {
> @@ -611,6 +617,9 @@ static int panel_edp_get_modes(struct drm_panel *panel,
> } else {
> num += drm_edid_connector_add_modes(connector);
> }
> +
> + if (has_override_bpc)
> + connector->display_info.bpc = p->detected_panel->override_bpc;
> }
>
> pm_runtime_mark_last_busy(panel->dev);
> @@ -1871,6 +1880,17 @@ static const struct panel_delay delay_80_500_e50_d50 = {
> .override_edid_mode = _mode \
> }
>
> +#define EDP_PANEL_ENTRY3(vend_chr_0, vend_chr_1, vend_chr_2, product_id, _delay, _name, _bpc) \
> +{ \
> + .ident = { \
> + .name = _name, \
> + .panel_id = drm_edid_encode_panel_id(vend_chr_0, vend_chr_1, vend_chr_2, \
> + product_id), \
> + }, \
> + .delay = _delay, \
> + .override_bpc = _bpc \
> +}
> +
> /*
> * This table is used to figure out power sequencing delays for panels that
> * are detected by EDID. Entries here may point to entries in the
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-10-30 9:44 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
2025-10-30 9:44 ` Jani Nikula [this message]
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=d6fe55b210888b9279c776b2bbfeaf38bfc44dcb@intel.com \
--to=jani.nikula@linux.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