dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Mario Limonciello <superm1@kernel.org>
To: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
	Antheas Kapenekakis <lkml@antheas.dev>,
	"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Cc: "dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"philm@manjaro.org" <philm@manjaro.org>,
	"Koenig, Christian" <Christian.Koenig@amd.com>,
	Robert Beckett <bob.beckett@collabora.com>
Subject: Re: [PATCH v3 6/6] drm: panel-backlight-quirks: Log applied panel brightness quirks
Date: Wed, 3 Sep 2025 10:29:28 -0500	[thread overview]
Message-ID: <f5581961-2e47-4cd4-86e9-47ec37f71c06@kernel.org> (raw)
In-Reply-To: <BL1PR12MB5144E131D87B8B6584CF297DF701A@BL1PR12MB5144.namprd12.prod.outlook.com>

On 9/3/25 10:03 AM, Deucher, Alexander wrote:
> [Public]
> 
>> -----Original Message-----
>> From: Mario Limonciello <superm1@kernel.org>
>> Sent: Wednesday, September 3, 2025 12:53 AM
>> To: Antheas Kapenekakis <lkml@antheas.dev>; amd-gfx@lists.freedesktop.org
>> Cc: dri-devel@lists.freedesktop.org; linux-kernel@vger.kernel.org;
>> philm@manjaro.org; Deucher, Alexander <Alexander.Deucher@amd.com>; Koenig,
>> Christian <Christian.Koenig@amd.com>; Robert Beckett
>> <bob.beckett@collabora.com>
>> Subject: Re: [PATCH v3 6/6] drm: panel-backlight-quirks: Log applied panel
>> brightness quirks
>>
>> On 8/29/2025 10:01 AM, Antheas Kapenekakis wrote:
>>> On Fri, 29 Aug 2025 at 16:57, Antheas Kapenekakis <lkml@antheas.dev> wrote:
>>>>
>>>> Currently, when a panel brightness quirk is applied, there is no log
>>>> indicating that a quirk was applied. Unwrap the drm device on its own
>>>> and use drm_info() to log when a quirk is applied.
>>>>
>>>> Suggested-by: Mario Limonciello <mario.limonciello@amd.com>
>>>> Signed-off-by: Antheas Kapenekakis <lkml@antheas.dev>

Besides the one thing you identified this looks fine to me.

Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>

>>>> ---
>>>>    .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c    | 16 +++++++++++++---
>>>>    1 file changed, 13 insertions(+), 3 deletions(-)
>>>>
>>>> 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 263f15f6fdea..2a3e17d83d6e 100644
>>>> --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
>>>> +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
>>>> @@ -3617,13 +3617,15 @@ static void update_connector_ext_caps(struct
>> amdgpu_dm_connector *aconnector)
>>>>           struct drm_connector *conn_base;
>>>>           struct amdgpu_device *adev;
>>>>           struct drm_luminance_range_info *luminance_range;
>>>> +       struct drm_device *drm;
>>>>
>>>>           if (aconnector->bl_idx == -1 ||
>>>>               aconnector->dc_link->connector_signal != SIGNAL_TYPE_EDP)
>>>>                   return;
>>>>
>>>>           conn_base = &aconnector->base;
>>>> -       adev = drm_to_adev(conn_base->dev);
>>>> +       drm = conn_base->dev;
>>>> +       adev = drm_to_adev(drm);
>>>>
>>>>           caps = &adev->dm.backlight_caps[aconnector->bl_idx];
>>>>           caps->ext_caps = &aconnector->dc_link->dpcd_sink_ext_caps;
>>>> @@ -3659,12 +3661,20 @@ static void update_connector_ext_caps(struct
>> amdgpu_dm_connector *aconnector)
>>>>           panel_backlight_quirk =
>>>>                   drm_get_panel_backlight_quirk(aconnector->drm_edid);
>>>>           if (!IS_ERR_OR_NULL(panel_backlight_quirk)) {
>>>> -               if (panel_backlight_quirk->min_brightness)
>>>> +               if (panel_backlight_quirk->min_brightness) {
>>>> +                       drm_info(drm,
>>>> +                                "Applying panel backlight quirk, min_brightness: %d\n",
>>>> +
>>>> + panel_backlight_quirk->min_brightness);
>>>
>>> mmm, needs a -1 here
>>>
>>
>> You may as well re-order it too so that you set caps->min_input_signal and access
>> it in this message.
>>
> 
> With that fixed up, the series is:
> Acked-by: Alex Deucher <alexander.deucher@amd.com>
> 
> 

I've added a manual fixup for that change in the last patch and pushed 
the series to drm-misc-next.

a3ae3384be770 (HEAD -> drm-misc-next, drm-misc/for-linux-next, 
drm-misc/drm-misc-next) drm: panel-backlight-quirks: Log applied panel 
brightness quirks
bf0365b005d9a drm: panel-backlight-quirks: Add Steam Deck brightness quirk
aef10b1138e99 drm: panel-backlight-quirks: Add brightness mask quirk
f7033fab81d82 drm: panel-backlight-quirks: Add secondary DMI match
6eee1ef9e5985 drm: panel-backlight-quirks: Convert brightness quirk to 
generic structure
9931e4be11f21 drm: panel-backlight-quirks: Make EDID match optional

      reply	other threads:[~2025-09-03 15:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-29 14:55 [PATCH v3 0/6] drm: panel-backlight-quirks: Do partial refactor and apply OLED fix Antheas Kapenekakis
2025-08-29 14:55 ` [PATCH v3 1/6] drm: panel-backlight-quirks: Make EDID match optional Antheas Kapenekakis
2025-08-29 14:55 ` [PATCH v3 2/6] drm: panel-backlight-quirks: Convert brightness quirk to generic structure Antheas Kapenekakis
2025-08-29 14:55 ` [PATCH v3 3/6] drm: panel-backlight-quirks: Add secondary DMI match Antheas Kapenekakis
2025-08-29 14:55 ` [PATCH v3 4/6] drm: panel-backlight-quirks: Add brightness mask quirk Antheas Kapenekakis
2025-08-29 14:55 ` [PATCH v3 5/6] drm: panel-backlight-quirks: Add Steam Deck brightness quirk Antheas Kapenekakis
2025-08-29 14:55 ` [PATCH v3 6/6] drm: panel-backlight-quirks: Log applied panel brightness quirks Antheas Kapenekakis
2025-08-29 15:01   ` Antheas Kapenekakis
2025-09-03  4:52     ` Mario Limonciello
2025-09-03 15:03       ` Deucher, Alexander
2025-09-03 15:29         ` Mario Limonciello [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=f5581961-2e47-4cd4-86e9-47ec37f71c06@kernel.org \
    --to=superm1@kernel.org \
    --cc=Alexander.Deucher@amd.com \
    --cc=Christian.Koenig@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=bob.beckett@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@antheas.dev \
    --cc=philm@manjaro.org \
    /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;
as well as URLs for NNTP newsgroup(s).