From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>,
<intel-xe@lists.freedesktop.org>,
<intel-gfx@lists.freedesktop.org>
Cc: <arun.r.murthy@intel.com>
Subject: Re: [PATCH 1/2] drm/i915/backlight: Make try_vesa_interface as true
Date: Fri, 20 Feb 2026 10:45:55 +0530 [thread overview]
Message-ID: <bc41cb6c-044e-4ff6-a066-a6c29ea3b144@intel.com> (raw)
In-Reply-To: <20260219022454.2417063-1-suraj.kandpal@intel.com>
On 2/19/2026 7:54 AM, Suraj Kandpal wrote:
> Make try_vesa_interface as true by default. This is so that there
> is a fallback mechanism for Panels which needs VESA DPCD AUX backlight
> mechanism to work but has a broken VBT indicating otherwise.
>
> Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15679
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> index eb05ef4bd9f6..f14abc48a2a7 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> @@ -644,7 +644,7 @@ int intel_dp_aux_init_backlight_funcs(struct intel_connector *connector)
> struct intel_dp *intel_dp = intel_attached_dp(connector);
> struct drm_device *dev = connector->base.dev;
> struct intel_panel *panel = &connector->panel;
> - bool try_intel_interface = false, try_vesa_interface = false;
> + bool try_intel_interface = false, try_vesa_interface = true;
hmm If we want to fallback to VESA interface and we already check for
Intel interface first, then I think we can drop the try_vesa_interface
variable altogether.
In the note below, where the rationale of checking for Intel interface
is mentioned, there we need to add that some VBTs might be broken (in
the sense that they advertise Intel interface support, but are missing
the necessary support in the panel).
In such a case try VESA interface as a fallback.
Regards,
Ankit
>
> /* Check the VBT and user's module parameters to figure out which
> * interfaces to probe
prev parent reply other threads:[~2026-02-20 5:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 2:24 [PATCH 1/2] drm/i915/backlight: Make try_vesa_interface as true Suraj Kandpal
2026-02-19 2:24 ` [PATCH 2/2] drm/i915/backlight: Cleanup try_vesa_interface assignments Suraj Kandpal
2026-02-19 3:10 ` ✓ i915.CI.BAT: success for series starting with [1/2] drm/i915/backlight: Make try_vesa_interface as true Patchwork
2026-02-19 4:55 ` ✗ i915.CI.Full: failure " Patchwork
2026-02-20 5:15 ` Nautiyal, Ankit K [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=bc41cb6c-044e-4ff6-a066-a6c29ea3b144@intel.com \
--to=ankit.k.nautiyal@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=suraj.kandpal@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