From: Harry Wentland <harry.wentland@amd.com>
To: Rodrigo Siqueira Jordao <Rodrigo.Siqueira@amd.com>,
nicholas.kazlauskas@amd.com, hongao <hongao@uniontech.com>
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
sunpeng.li@amd.com, linux-kernel@vger.kernel.org,
alexander.deucher@amd.com, christian.koenig@amd.com,
Xinhui.Pan@amd.com, airlied@gmail.com, daniel@ffwll.ch,
aurabindo.pillai@amd.com, roman.li@amd.com, Jerry.Zuo@amd.com
Subject: Re: [PATCH] drm/amd/display: Fix set scaling doesn's work
Date: Wed, 11 Jan 2023 10:19:06 -0500 [thread overview]
Message-ID: <aea4b937-351a-f036-61e5-790af633f5f2@amd.com> (raw)
In-Reply-To: <789c2c61-4959-c3c1-0916-d1cc7f659247@amd.com>
On 1/10/23 10:58, Rodrigo Siqueira Jordao wrote:
>
>
> On 11/22/22 06:20, hongao wrote:
>> [Why]
>> Setting scaling does not correctly update CRTC state. As a result
>> dc stream state's src (composition area) && dest (addressable area)
>> was not calculated as expected. This causes set scaling doesn's work.
>>
>> [How]
>> Correctly update CRTC state when setting scaling property.
>>
>> Signed-off-by: hongao <hongao@uniontech.com>
>>
>> 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 3e1ecca72430..a88a6f758748 100644
>> --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
>> +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
>> @@ -9386,8 +9386,8 @@ static int amdgpu_dm_atomic_check(struct drm_device *dev,
>> goto fail;
>> }
>> - if (dm_old_con_state->abm_level !=
>> - dm_new_con_state->abm_level)
>> + if (dm_old_con_state->abm_level != dm_new_con_state->abm_level ||
>> + dm_old_con_state->scaling != dm_new_con_state->scaling)
>> new_crtc_state->connectors_changed = true;
>> }
>>
>
> Hi,
>
> This change lgtm, and I also run it in our CI, and from IGT perspective, we are good.
>
> Harry, do you have any comment about this change?
>
LGTM
Reviewed-by: Harry Wentland <harry.wentland@amd.com>
Harry
> Thanks
> Siqueira
next prev parent reply other threads:[~2023-01-11 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 11:20 hongao
2023-01-10 15:58 ` Rodrigo Siqueira Jordao
2023-01-11 15:19 ` Harry Wentland [this message]
2023-01-12 16:08 ` Rodrigo Siqueira Jordao
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=aea4b937-351a-f036-61e5-790af633f5f2@amd.com \
--to=harry.wentland@amd.com \
--cc=Jerry.Zuo@amd.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=aurabindo.pillai@amd.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hongao@uniontech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicholas.kazlauskas@amd.com \
--cc=roman.li@amd.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®