From: "Murthy, Arun R" <arun.r.murthy@intel.com>
To: "Kandpal, Suraj" <suraj.kandpal@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
Subject: Re: [PATCH 7/8] drm/i915/backlight: Provide clear description on how backlight level is controlled
Date: Tue, 24 Feb 2026 08:52:38 +0530 [thread overview]
Message-ID: <85d1a57d-0587-4d6e-8698-263f2c326654@intel.com> (raw)
In-Reply-To: <DM3PPF208195D8D75CD839398873412EF9DE374A@DM3PPF208195D8D.namprd11.prod.outlook.com>
On 24-02-2026 08:50, Kandpal, Suraj wrote:
>> Subject: Re: [PATCH 7/8] drm/i915/backlight: Provide clear description on how
>> backlight level is controlled
>>
>> On 20-02-2026 10:32, Suraj Kandpal wrote:
>>> Currently it takes us multiple log prints to arrive at the conclusion
>>> on how we are actually controlling backlight level. Make the logging
>>> concise.
>>>
>>> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
>>> ---
>>> .../drm/i915/display/intel_dp_aux_backlight.c | 19 ++++++++++++++-----
>>> 1 file changed, 14 insertions(+), 5 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 043c9aef2ea6..aac6cdb5b69b 100644
>>> --- a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
>>> +++ b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
>>> @@ -368,6 +368,16 @@ static const char *dpcd_vs_pwm_str(bool aux)
>>> return aux ? "DPCD" : "PWM";
>>> }
>>>
>>> +static const char *backlight_unit_str(struct intel_panel *panel) {
>>> + if (panel->backlight.edp.vesa.info.luminance_set)
>>> + return "NITS";
>>> + else if (panel->backlight.edp.vesa.info.aux_set)
>>> + return "Brightness %";
>> Should this be AUX Brightness?
>> So that it calls out its AUX based DPCD backlight control.
> Actually where this is called has the line
> "AUX VESA backlight level is controlled through %s using %s values\n"
> Here we return the unit value we use to control brightness
Sorry missed that, so with having AUX backlight already, this proposed
change doesnt make much sense.
Reviewed-by: Arun R Murthy <arun.r.murthy@intel.com>
Thanks and Regards,
Arun R Murthy
-------------------
> Regards,
> Suraj Kandpal
>
>>> + else
>>> + return "PWM";
>>> +}
>>> +
>>> static void
>>> intel_dp_aux_write_panel_luminance_override(struct intel_connector
>> *connector)
>>> {
>>> @@ -542,9 +552,11 @@ static int
>> intel_dp_aux_vesa_setup_backlight(struct intel_connector *connector,
>>> dpcd_vs_pwm_str(panel-
>>> backlight.edp.vesa.info.aux_enable ||
>>> panel-
>>> backlight.edp.vesa.info.luminance_set));
>>> drm_dbg_kms(display->drm,
>>> - "[CONNECTOR:%d:%s] AUX VESA backlight level is
>> controlled through %s\n",
>>> + "[CONNECTOR:%d:%s] AUX VESA backlight level is
>> controlled
>>> +through %s using %s values\n",
>>> connector->base.base.id, connector->base.name,
>>> - dpcd_vs_pwm_str(panel-
>>> backlight.edp.vesa.info.aux_set));
>>> + dpcd_vs_pwm_str(panel->backlight.edp.vesa.info.aux_set
>> ||
>>> + panel-
>>> backlight.edp.vesa.info.luminance_set),
>>> + backlight_unit_str(panel));
>>>
>>> if (!panel->backlight.edp.vesa.info.aux_set ||
>>> !panel->backlight.edp.vesa.info.aux_enable) { @@ -569,9 +581,6
>>> @@ static int intel_dp_aux_vesa_setup_backlight(struct intel_connector
>> *connector,
>>> panel->backlight.enabled = panel->backlight.level != 0;
>>> if (!panel->backlight.level)
>>> panel->backlight.level = panel->backlight.max;
>>> - drm_dbg_kms(display->drm,
>>> - "[CONNECTOR:%d:%s] AUX VESA Nits backlight
>> level is controlled through DPCD\n",
>>> - connector->base.base.id, connector->base.name);
>>> } else if (panel->backlight.edp.vesa.info.aux_set) {
>>> panel->backlight.max = panel->backlight.edp.vesa.info.max;
>>> panel->backlight.min = 0;
next prev parent reply other threads:[~2026-02-24 3:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 5:02 [PATCH 0/8] Fixes and updates when using AUX backlight using Luminance Suraj Kandpal
2026-02-20 5:02 ` [PATCH 1/8] drm/i915/backlight: Avoid 0 brightness for VESA AUX backlight by default Suraj Kandpal
2026-02-24 2:50 ` Murthy, Arun R
2026-02-20 5:02 ` [PATCH 2/8] drm/i915/backlight: Use intel_panel variable instead of intel_connector Suraj Kandpal
2026-02-24 2:52 ` Murthy, Arun R
2026-02-20 5:02 ` [PATCH 3/8] drm/i915/backlight: Take luminance_set into account for VESA backlight Suraj Kandpal
2026-02-24 2:54 ` Murthy, Arun R
2026-02-20 5:02 ` [PATCH 4/8] drm/i915/backlight: Check luminance_set when disabling PWM via AUX " Suraj Kandpal
2026-02-24 2:55 ` Murthy, Arun R
2026-02-20 5:02 ` [PATCH 5/8] drm/i915/backlight: Short circuit intel_dp_aux_supports_hdr_backlight Suraj Kandpal
2026-02-24 2:57 ` Murthy, Arun R
2026-02-20 5:02 ` [PATCH 6/8] drm/i915/backlight: Update debug log during backlight setup Suraj Kandpal
2026-02-23 7:05 ` Garg, Nemesa
2026-02-23 8:11 ` Kandpal, Suraj
2026-02-23 9:29 ` Garg, Nemesa
2026-02-24 3:03 ` Murthy, Arun R
2026-02-20 5:02 ` [PATCH 7/8] drm/i915/backlight: Provide clear description on how backlight level is controlled Suraj Kandpal
2026-02-24 3:05 ` Murthy, Arun R
2026-02-24 3:20 ` Kandpal, Suraj
2026-02-24 3:22 ` Murthy, Arun R [this message]
2026-02-20 5:02 ` [PATCH 8/8] drm/i915/backlight: Avoid 0 brightness for INTEL AUX HDR backlight by default Suraj Kandpal
2026-02-24 3:06 ` Murthy, Arun R
2026-02-20 5:46 ` ✓ CI.KUnit: success for Fixes and updates when using AUX backlight using Luminance (rev2) Patchwork
2026-02-20 9:19 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-20 19:32 ` ✗ Xe.CI.FULL: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
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 7/8] drm/i915/backlight: Provide clear description on how backlight level is controlled Suraj Kandpal
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=85d1a57d-0587-4d6e-8698-263f2c326654@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