From: "Lazar, Lijo" <lijo.lazar@amd.com>
To: Kevin Wang <kevin.wang@amd.com>, amd-gfx@lists.freedesktop.org
Cc: alexander.deucher@amd.com, hawking.zhang@amd.com, kenneth.feng@amd.com
Subject: Re: [PATCH 0/7] drm/amd/pm: stage OD reset until commit
Date: Mon, 31 Aug 2026 16:25:41 +0530 [thread overview]
Message-ID: <6041b95a-ac8c-4410-97cb-8eca51d20d50@amd.com> (raw)
In-Reply-To: <20260831043507.523599-1-kevin.wang@amd.com>
On 31-Aug-26 10:05 AM, Kevin Wang wrote:
> [Some people who received this message don't often get email from kevin.wang@amd.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> The pp_od_clk_voltage interface exposes a staged OverDrive workflow:
> users edit clock, voltage, and power settings, then write "c" to
> commit them to the SMU.
>
> However, PP_OD_RESTORE_DEFAULT_TABLE does not follow this workflow on
> every SMU version. Some backends restore their cached settings and wait
> for "c", while others upload the reset table or send frequency-limit
> commands directly from "r". As a result, the same userspace sequence
> has different hardware effects across ASICs.
>
> For example:
>
> - SMU 14.0.0 and SMU 13.0.5 stage reset limits until "c".
> - SMU 14.0.2 and SMU 13.0.6 apply reset values immediately.
> - Navi10 stages the boot OD table, while Vega20 reads the current SMU
> table instead of restoring the saved defaults.
>
> This series makes "r" restore default values only in driver-side
> staging state. "c" remains the sole operation that uploads an OD table
> or sends frequency-limit commands to PMFW.
>
> This gives pp_od_clk_voltage one consistent transaction model:
>
> edit/reset -> staged driver state -> commit
Reset should be reset to defaults and shouldn't require extra commit.
This breaks existing userspace for SMU 13.0.6.
Thanks,
Lijo
> It also permits userspace to reset a staged configuration, adjust one
> or more settings, and submit the final configuration with one commit,
> without temporarily applying an intermediate default configuration.
>
> Link: https://gitlab.freedesktop.org/drm/amd/-/work_items/5690
>
> Kevin Wang (7):
> drm/amd/pm: stage od reset for smu 11.0.7
> drm/amd/pm: stage od reset for smu 13.0.2
> drm/amd/pm: stage od reset for smu 13.0.0/13.0.7
> drm/amd/pm: stage od reset for smu 13.0.6
> drm/amd/pm: stage od reset for smu 14.0.2
> drm/amd/pm: stage od reset for smu 15.0.8
> drm/amd/pm: stage od reset for smu vega20
>
> .../drm/amd/pm/powerplay/hwmgr/vega20_hwmgr.c | 75 ++++++++++++++--
> .../amd/pm/swsmu/smu11/sienna_cichlid_ppt.c | 2 +-
> .../drm/amd/pm/swsmu/smu13/aldebaran_ppt.c | 15 +---
> .../drm/amd/pm/swsmu/smu13/smu_v13_0_0_ppt.c | 2 +-
> .../drm/amd/pm/swsmu/smu13/smu_v13_0_6_ppt.c | 85 ++++++++++---------
> .../drm/amd/pm/swsmu/smu13/smu_v13_0_7_ppt.c | 2 +-
> .../drm/amd/pm/swsmu/smu14/smu_v14_0_2_ppt.c | 2 +-
> .../drm/amd/pm/swsmu/smu15/smu_v15_0_8_ppt.c | 50 ++++++-----
> 8 files changed, 145 insertions(+), 88 deletions(-)
>
> --
> 2.55.0
>
next prev parent reply other threads:[~2026-08-31 10:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 4:35 [PATCH 0/7] drm/amd/pm: stage OD reset until commit Kevin Wang
2026-08-31 4:35 ` [PATCH 1/7] drm/amd/pm: stage od reset for smu 11.0.7 Kevin Wang
2026-08-31 4:35 ` [PATCH 2/7] drm/amd/pm: stage od reset for smu 13.0.2 Kevin Wang
2026-08-31 4:35 ` [PATCH 3/7] drm/amd/pm: stage od reset for smu 13.0.0/13.0.7 Kevin Wang
2026-08-31 4:35 ` [PATCH 4/7] drm/amd/pm: stage od reset for smu 13.0.6 Kevin Wang
2026-08-31 10:51 ` Lazar, Lijo
2026-08-31 4:35 ` [PATCH 5/7] drm/amd/pm: stage od reset for smu 14.0.2 Kevin Wang
2026-08-31 4:35 ` [PATCH 6/7] drm/amd/pm: stage od reset for smu 15.0.8 Kevin Wang
2026-08-31 4:35 ` [PATCH 7/7] drm/amd/pm: stage od reset for smu vega20 Kevin Wang
2026-08-31 8:09 ` [PATCH 0/7] drm/amd/pm: stage OD reset until commit Feng, Kenneth
2026-08-31 8:23 ` Wang, Kevin
2026-08-31 10:55 ` Lazar, Lijo [this message]
2026-08-31 11:05 ` Lazar, Lijo
2026-08-31 12:06 ` Wang, Kevin
2026-08-31 12:21 ` Lazar, Lijo
2026-08-31 12:47 ` Wang, Kevin
2026-09-01 6:44 ` Feng, Kenneth
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=6041b95a-ac8c-4410-97cb-8eca51d20d50@amd.com \
--to=lijo.lazar@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=hawking.zhang@amd.com \
--cc=kenneth.feng@amd.com \
--cc=kevin.wang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.