From: "Murthy, Arun R" <arun.r.murthy@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>,
<intel-xe@lists.freedesktop.org>,
<intel-gfx@lists.freedesktop.org>
Cc: <ankit.k.nautiyal@intel.com>
Subject: Re: [PATCH 1/8] drm/i915/backlight: Avoid 0 brightness for VESA AUX backlight
Date: Wed, 18 Feb 2026 14:05:30 +0530 [thread overview]
Message-ID: <56cae45c-3122-42a3-bf30-180c5a4f0135@intel.com> (raw)
In-Reply-To: <20260213091653.2250887-2-suraj.kandpal@intel.com>
On 13-02-2026 14:46, Suraj Kandpal wrote:
> Whenever the minimum brightness is reported as 0 there are chances
> we maybe sometimes end up with blank screen.
maybe->may
Please reframe
> This confuses the user
> into thinking the display is acting weird. This occurs in eDP 1.5 when
> we are PANEL_LUMINANCE_OVERRIDE
in PANEL_LUMINANCE_OVERRIDE
> mode to mainpulate brightness via luminance
> values. Make sure if minimum luminance range is 0 we program
> it to 10% of max luminance range.
0 nits for OLED panel is a valid value right?
Instead better to have a default brightness if no brightness is parsed
from the vbt and the default brightness can be max_brightness.
Thanks and Regards,
Arun R Murthy
--------------------
>
> Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15671
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> ---
> .../gpu/drm/i915/display/intel_dp_aux_backlight.c | 14 +++++++++++---
> 1 file changed, 11 insertions(+), 3 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 eb05ef4bd9f6..f1811beee25f 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> @@ -456,7 +456,11 @@ static u32 intel_dp_aux_vesa_get_backlight(struct intel_connector *connector, en
> }
>
> val |= buf[0] | buf[1] << 8 | buf[2] << 16;
> - return val / 1000;
> + val = val / 1000;
> + if (!val)
> + return panel->backlight.min;
> +
> + return val;
> }
>
> return connector->panel.backlight.level;
> @@ -557,10 +561,14 @@ static int intel_dp_aux_vesa_setup_backlight(struct intel_connector *connector,
> if (panel->backlight.edp.vesa.info.luminance_set) {
> if (luminance_range->max_luminance) {
> panel->backlight.max = panel->backlight.edp.vesa.info.max;
> - panel->backlight.min = luminance_range->min_luminance;
> + if (luminance_range->min_luminance)
> + panel->backlight.min = luminance_range->min_luminance;
> + else
> + panel->backlight.min = (luminance_range->max_luminance * 10) / 100;
> +
> } else {
> panel->backlight.max = 512;
> - panel->backlight.min = 0;
> + panel->backlight.min = 51;
> }
> panel->backlight.level = intel_dp_aux_vesa_get_backlight(connector, 0);
> panel->backlight.enabled = panel->backlight.level != 0;
next prev parent reply other threads:[~2026-02-18 8:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 9:16 [PATCH 0/8] Fixes and updates when using AUX backlight using Luminance Suraj Kandpal
2026-02-13 9:16 ` [PATCH 1/8] drm/i915/backlight: Avoid 0 brightness for VESA AUX backlight Suraj Kandpal
2026-02-18 8:35 ` Murthy, Arun R [this message]
2026-02-13 9:16 ` [PATCH 2/8] drm/i915/backlight: Use intel_panel variable instead of intel_connector Suraj Kandpal
2026-02-13 9:16 ` [PATCH 3/8] drm/i915/backlight: Take luminance_set into account for VESA backlight Suraj Kandpal
2026-02-13 9:16 ` [PATCH 4/8] drm/i915/backlight: Check luminance_set when disabling PWM via AUX " Suraj Kandpal
2026-02-13 9:16 ` [PATCH 5/8] drm/i915/backlight: Short circuit intel_dp_aux_supports_hdr_backlight Suraj Kandpal
2026-02-13 9:16 ` [PATCH 6/8] drm/i915/backlight: Update debug log during backlight setup Suraj Kandpal
2026-02-13 9:16 ` [PATCH 7/8] drm/i915/backlight: Provide clear description on how backlight level is controlled Suraj Kandpal
2026-02-13 9:16 ` [PATCH 8/8] drm/i915/backlight: Avoid 0 brightness for INTEL AUX HDR backlight Suraj Kandpal
2026-02-13 9:45 ` ✗ CI.checkpatch: warning for Fixes and updates when using AUX backlight using Luminance Patchwork
2026-02-13 9:46 ` ✓ CI.KUnit: success " Patchwork
2026-02-13 10:22 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-14 6:28 ` ✗ Xe.CI.FULL: failure " 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=56cae45c-3122-42a3-bf30-180c5a4f0135@intel.com \
--to=arun.r.murthy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox