From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>
Cc: intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
ankit.k.nautiyal@intel.com
Subject: Re: [PATCH] drm/i915/backlight: Fix VESA backlight possible check condition
Date: Thu, 2 Apr 2026 22:18:55 +0300 [thread overview]
Message-ID: <ac7BHyT8VI1vEMQv@intel.com> (raw)
In-Reply-To: <20260401034332.1321585-1-suraj.kandpal@intel.com>
On Wed, Apr 01, 2026 at 09:13:32AM +0530, Suraj Kandpal wrote:
> VESA backlight is possible through AUX only when
> BACKLIGHT_AUX_ENABLE_CAPABLE is true or when we use BL_ENABLE bit
> to enable backlight. Since that is not implemented we need to make
> sure we do not try to manipulate backlight when
> BACKLIGHT_AUX_ENABLE_CAPABLE is not set.
> Also fix return value when condition is not fulfilled.
>
> Fixes: 40d2f5820951 ("drm/i915/backlight: Remove try_vesa_interface")
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
Appears to work.
Tested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
I filed a bug with a dump of all platform information, mainly for posterity:
Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/work_items/15907
> ---
> drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> 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 d0c76632a946..138d5b5e5482 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> @@ -615,8 +615,9 @@ check_if_vesa_backlight_possible(struct intel_dp *intel_dp)
> int ret;
> u8 bit_min, bit_max;
>
> - if (!(intel_dp->edp_dpcd[2] & DP_EDP_BACKLIGHT_BRIGHTNESS_AUX_SET_CAP))
> - return true;
> + if (!(intel_dp->edp_dpcd[2] & DP_EDP_BACKLIGHT_BRIGHTNESS_AUX_SET_CAP &&
> + intel_dp->edp_dpcd[1] & DP_EDP_BACKLIGHT_AUX_ENABLE_CAP))
> + return false;
>
> ret = drm_dp_dpcd_read_byte(&intel_dp->aux, DP_EDP_PWMGEN_BIT_COUNT_CAP_MIN, &bit_min);
> if (ret < 0)
> --
> 2.34.1
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2026-04-02 19:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 3:43 [PATCH] drm/i915/backlight: Fix VESA backlight possible check condition Suraj Kandpal
2026-04-01 3:50 ` ✓ CI.KUnit: success for " Patchwork
2026-04-01 4:36 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-01 4:37 ` ✓ i915.CI.BAT: " Patchwork
2026-04-01 10:53 ` ✓ Xe.CI.FULL: " Patchwork
2026-04-01 20:22 ` ✓ i915.CI.Full: " Patchwork
2026-04-02 19:18 ` Ville Syrjälä [this message]
2026-04-06 14:42 ` [PATCH] " Nautiyal, Ankit K
2026-04-07 3:07 ` [PATCH v2] " Suraj Kandpal
2026-04-07 11:10 ` Nautiyal, Ankit K
2026-04-07 3:57 ` ✓ i915.CI.BAT: success for drm/i915/backlight: Fix VESA backlight possible check condition (rev2) Patchwork
2026-04-07 4:30 ` ✓ CI.KUnit: " Patchwork
2026-04-07 5:07 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-07 6:00 ` ✗ i915.CI.Full: failure " Patchwork
2026-04-07 6:39 ` ✗ Xe.CI.FULL: " Patchwork
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=ac7BHyT8VI1vEMQv@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=ankit.k.nautiyal@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.