AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <superm1@kernel.org>
To: "Vivek Das Mohapatra" <vivek@collabora.com>,
	"Harry Wentland" <harry.wentland@amd.com>,
	"Leo Li" <sunpeng.li@amd.com>,
	"Rodrigo Siqueira" <siqueira@igalia.com>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Christian König" <christian.koenig@amd.com>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>
Cc: kernel@collabora.com, amd-gfx@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] drm/amd/display: Initialise backlight level values from hw
Date: Mon, 12 Jan 2026 08:10:31 -0600	[thread overview]
Message-ID: <7ec7b4ae-6186-4961-a857-f97afcfc3ded@kernel.org> (raw)
In-Reply-To: <20260112122140.2609679-1-vivek@collabora.com>

On 1/12/26 6:20 AM, Vivek Das Mohapatra wrote:
> Internal backlight levels are initialised from ACPI but the values
> are sometimes out of sync with the levels in effect until there has
> been a read from hardware (eg triggered by reading from sysfs).
> 
> This means that the first drm_commit can cause the levels to be set
> to a different value than the actual starting one, which results in
> a sudden change in brightness.
> 
> This path shows the problem (when the values are out of sync):
> 
>     amdgpu_dm_atomic_commit_tail()
>     -> amdgpu_dm_commit_streams()
>     -> amdgpu_dm_backlight_set_level(..., dm->brightness[n])
> 
> This patch calls the backlight ops get_brightness explicitly
> at the end of backlight registration to make sure dm->brightness[n]
> is in sync with the actual hardware levels.
> 
> Signed-off-by: Vivek Das Mohapatra <vivek@collabora.com>

Thanks for the patch.  One comment below.

> ---
>   .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c    | 16 ++++++++++++++++
>   1 file changed, 16 insertions(+)
> 
> diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> index 354e359c4507..50f0547ed63c 100644
> --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> @@ -5258,6 +5258,8 @@ amdgpu_dm_register_backlight_device(struct amdgpu_dm_connector *aconnector)
>   	struct amdgpu_dm_backlight_caps *caps;
>   	char bl_name[16];
>   	int min, max;
> +	int real_brightness;
> +	int init_brightness;
>   
>   	if (aconnector->bl_idx == -1)
>   		return;
> @@ -5282,6 +5284,8 @@ amdgpu_dm_register_backlight_device(struct amdgpu_dm_connector *aconnector)
>   	} else
>   		props.brightness = props.max_brightness = MAX_BACKLIGHT_LEVEL;
>   
> +	init_brightness = props.brightness;
> +
>   	if (caps->data_points && !(amdgpu_dc_debug_mask & DC_DISABLE_CUSTOM_BRIGHTNESS_CURVE)) {
>   		drm_info(drm, "Using custom brightness curve\n");
>   		props.scale = BACKLIGHT_SCALE_NON_LINEAR;
> @@ -5297,6 +5301,18 @@ amdgpu_dm_register_backlight_device(struct amdgpu_dm_connector *aconnector)
>   					  &amdgpu_dm_backlight_ops, &props);
>   	dm->brightness[aconnector->bl_idx] = props.brightness;
>   
> +	/*
> +	 * dm->brightness[x] can be inconsistent just after startup until
> +	 * ops.get_brightness is called.
> +	 */
> +	real_brightness =
> +		amdgpu_dm_backlight_ops.get_brightness(dm->backlight_dev[aconnector->bl_idx]);
> +
> +	if (real_brightness != init_brightness) {
> +		dm->actual_brightness[aconnector->bl_idx] = real_brightness;
> +		dm->brightness[aconnector->bl_idx] = real_brightness;
> +	}
> +

I think this call should be after the IS_ERR() check right below it in 
only the case that IS_ERR() failed.

>   	if (IS_ERR(dm->backlight_dev[aconnector->bl_idx])) {
>   		drm_err(drm, "DM: Backlight registration failed!\n");
>   		dm->backlight_dev[aconnector->bl_idx] = NULL;


  reply	other threads:[~2026-01-12 14:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12 12:20 [PATCH v1] drm/amd/display: Initialise backlight level values from hw Vivek Das Mohapatra
2026-01-12 14:10 ` Mario Limonciello [this message]
2026-01-12 15:28   ` [PATCH v2] " Vivek Das Mohapatra
2026-01-12 15:52     ` Mario Limonciello

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=7ec7b4ae-6186-4961-a857-f97afcfc3ded@kernel.org \
    --to=superm1@kernel.org \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=harry.wentland@amd.com \
    --cc=kernel@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=simona@ffwll.ch \
    --cc=siqueira@igalia.com \
    --cc=sunpeng.li@amd.com \
    --cc=vivek@collabora.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