mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ray Wu <ray.wu@amd.com>
To: Hugo Sales <hugo@hsal.es>,
	harry.wentland@amd.com, siqueira@igalia.com,
	amd-gfx@lists.freedesktop.org, sunpeng.li@amd.com,
	alexander.deucher@amd.com
Cc: mario.limonciello@amd.com, christian.koenig@amd.com,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	simona@ffwll.ch, alex.hung@amd.com, airlied@gmail.com
Subject: Re: [PATCH RFC 3/3] drm/amd/display: Warn about an invalid ATIF backlight signal range
Date: Wed, 11 Nov 2026 17:35:23 +0800	[thread overview]
Message-ID: <30437e95-2104-4bce-9565-d672d3e97d8a@amd.com> (raw)
In-Reply-To: <20261104-backlight-curve-validate-v1-3-10c688880e85@hsal.es>

Reviewed-by: Ray Wu <ray.wu@amd.com>

On 11/4/2026 6:31 PM, Hugo Sales wrote:
> When the ATIF signal range is out of bounds or narrower than
> AMDGPU_DM_MIN_SPREAD, amdgpu_dm_validate_backlight_caps() drops the
> firmware caps and the driver falls back to a range of 12-255. It only
> says so with drm_dbg_kms(), so a user whose brightness range changed
> finds nothing in dmesg to report
>
> Make it a drm_warn() with FW_BUG, like the custom curve warnings
>
> Signed-off-by: Hugo Sales <hugo@hsal.es>
> ---
>   drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_backlight.c | 6 ++++--
>   1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_backlight.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_backlight.c
> index 3a27fb956627a..68b34654fca02 100644
> --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_backlight.c
> +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_backlight.c
> @@ -104,8 +104,10 @@ void amdgpu_dm_validate_backlight_caps(struct amdgpu_display_manager *dm, int bl
>   	    caps->min_input_signal < 0 ||
>   	    spread > AMDGPU_DM_DEFAULT_MAX_BACKLIGHT ||
>   	    spread < AMDGPU_DM_MIN_SPREAD) {
> -		drm_dbg_kms(adev_to_drm(dm->adev), "DM: Invalid backlight caps: min=%d, max=%d\n",
> -			    caps->min_input_signal, caps->max_input_signal);
> +		drm_warn(adev_to_drm(dm->adev), FW_BUG
> +			 "ATIF: backlight signal range %d to %d is invalid, using %d to %d\n",
> +			 caps->min_input_signal, caps->max_input_signal,
> +			 AMDGPU_DM_DEFAULT_MIN_BACKLIGHT, AMDGPU_DM_DEFAULT_MAX_BACKLIGHT);
>   		caps->caps_valid = false;
>   	}
>   
>

      reply	other threads:[~2026-11-11  9:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 10:31 [PATCH RFC 0/3] drm/amd/display: Check the ATIF backlight curve Hugo Sales
2026-11-04 10:31 ` [PATCH RFC 1/3] drm/amd/display: Repair or drop a bad " Hugo Sales
2026-11-04 10:31 ` [PATCH RFC 2/3] drm/amd/display: Add KUnit tests for the ATIF backlight curve check Hugo Sales
2026-11-11  9:39   ` Ray Wu
2026-11-04 10:31 ` [PATCH RFC 3/3] drm/amd/display: Warn about an invalid ATIF backlight signal range Hugo Sales
2026-11-11  9:35   ` Ray Wu [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=30437e95-2104-4bce-9565-d672d3e97d8a@amd.com \
    --to=ray.wu@amd.com \
    --cc=airlied@gmail.com \
    --cc=alex.hung@amd.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=hugo@hsal.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=simona@ffwll.ch \
    --cc=siqueira@igalia.com \
    --cc=sunpeng.li@amd.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

all inboxes | Powered by JetHome®