From: Hamza Mahfooz <hamza.mahfooz@amd.com>
To: Mario Limonciello <mario.limonciello@amd.com>,
amd-gfx@lists.freedesktop.org, Simon Ser <contact@emersion.fr>
Cc: Harry Wentland <Harry.Wentland@amd.com>,
Xaver Hugl <xaver.hugl@gmail.com>,
dri-devel@lists.freedesktop.org, Leo Li <sunpeng.li@amd.com>,
Sean Paul <seanpaul@google.com>
Subject: Re: [PATCH v4 0/2] Add support for 'power saving policy' property
Date: Wed, 10 Jul 2024 17:01:22 -0400 [thread overview]
Message-ID: <3a590f4d-18a5-46ba-a536-a4ea76bda59b@amd.com> (raw)
In-Reply-To: <20240703051722.328-1-mario.limonciello@amd.com>
On 7/3/24 01:17, Mario Limonciello wrote:
> During the Display Next hackfest 2024 one of the topics discussed
> was the need for compositor to be able to relay intention to drivers
> that color fidelity is preferred over power savings.
>
> To accomplish this a new optional DRM property is being introduced called
> "power saving policy". This property is a bit mask that can be configured
> with requests of "Require color accuracy" or "Require low latency"
> that can be configured by the compositor.
>
> When a driver advertises support for this property and the compositor
> sets it to "Require color accuracy" then the driver will disable any power
> saving features that can compromise color fidelity.
>
> In practice the main feature this currently applies to is the
> "Adaptive Backlight Modulation" feature within AMD DCN on eDP panels.
>
> When the compositor has marked the property "Require color accuracy" then
> this feature will be disabled and any userspace that tries to turn it on
> will get an -EBUSY return code.
>
> Compositors can also request that low latency is critical which in
> practice should cause PSR and PSR2 to be disabled.
>
> When the compositor has restored the value back to no requirements then
> the previous value that would have been programmed will be restored.
Applied, thanks!
>
> v3->v4:
> * Fixup for Xaver's reported issue
> v2->v3:
> * Updates from Leo's comments (see individual patches)
>
> Mario Limonciello (2):
> drm: Introduce 'power saving policy' drm property
> drm/amd: Add power_saving_policy drm property to eDP connectors
>
> drivers/gpu/drm/amd/amdgpu/amdgpu_display.c | 4 ++
> .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 50 +++++++++++++++++--
> .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h | 2 +
> drivers/gpu/drm/drm_connector.c | 48 ++++++++++++++++++
> include/drm/drm_connector.h | 2 +
> include/drm/drm_mode_config.h | 5 ++
> include/uapi/drm/drm_mode.h | 7 +++
> 7 files changed, 113 insertions(+), 5 deletions(-)
>
--
Hamza
prev parent reply other threads:[~2024-07-10 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 5:17 [PATCH v4 0/2] Add support for 'power saving policy' property Mario Limonciello
2024-07-03 5:17 ` [PATCH v4 1/2] drm: Introduce 'power saving policy' drm property Mario Limonciello
2024-07-03 5:17 ` [PATCH v4 2/2] drm/amd: Add power_saving_policy drm property to eDP connectors Mario Limonciello
2024-07-10 20:48 ` Leo Li
2024-07-10 21:01 ` Hamza Mahfooz [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=3a590f4d-18a5-46ba-a536-a4ea76bda59b@amd.com \
--to=hamza.mahfooz@amd.com \
--cc=Harry.Wentland@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=contact@emersion.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=mario.limonciello@amd.com \
--cc=seanpaul@google.com \
--cc=sunpeng.li@amd.com \
--cc=xaver.hugl@gmail.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