All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Timur Kristóf" <timur.kristof@gmail.com>
To: amd-gfx@lists.freedesktop.org, Petr Belyaev <upcfrost@gmail.com>
Cc: alexander.deucher@amd.com, Petr Belyaev <upcfrost@gmail.com>
Subject: Re: [PATCH] drm/amd/pm/smu7: Don't send VddC_Request on CI
Date: Mon, 24 Aug 2026 17:07:41 +0200	[thread overview]
Message-ID: <GoS-FsT8QACGf_8gWuUlnQ@gmail.com> (raw)
In-Reply-To: <20260824144714.182835-1-upcfrost@gmail.com>

On Monday, August 24, 2026 4:47:14 PM Central European Summer Time Petr 
Belyaev wrote:
> smu7_upload_dpm_level_enable_mask() calls
> smu7_apply_minimum_dce_voltage_request() unconditionally, which sends
> PPSMC_MSG_VddC_Request to the SMC. CI SMC firmware does not implement
> that message: it is only defined in smu7_ppsmc.h, tonga_ppsmc.h and
> fiji_ppsmc.h, and there is no CI equivalent. The SMC therefore never
> writes SMC_RESP, PHM_WAIT_FIELD_UNEQUAL() spins until it gives up, and
> every call burns the full ~1.9s response timeout.

Hi,

I'm sorry but this is wrong.
I added the VDDC request specifically to solve an issue with a Bonaire GPU.
That system will boot into a black screen without requesting a high enough 
voltage for the display engine. This patch would regress that.

> 
> Nothing downstream notices, because ci_send_msg_to_smc() returns 0
> regardless of the outcome. The only effects are the delay and
> 
>   amdgpu: failed to send message 15f ret is 0
> 
> in dmesg. On a Radeon R7 260X (BONAIRE, 1002:6658) this is 40 messages
> per boot: 32 during the boot-time modeset, which becomes ~59s of blank
> screen, and 8 more on every DPMS wake, adding ~15s before the display
> comes back.

How do you reproduce this issue, and on which kernel version?
I've tested this patch on two different Bonaire chips and a Hawaii chip, and 
haven't seen this error message. In fact I am running an R9 390X right now and 
I don't see this error message in my logs.

> 
> Commit 0138610c1413 ("drm/amd/pm/smu7: Fix SMU7 voltage dependency on
> display clock") extended this feature to CI, which the previous
> implementation had deliberately excluded -- the old call site was
> guarded by pp_table_version == PP_TABLE_V1 with an adjacent comment
> reading "TO DO for v0 iceland and Ci". That commit was verified on a
> Radeon R9 M380, which is VI, so the CI path went untested.

The CI path definitely did not go untested.
R9 M380 is Bonaire (it's in an old iMac).
You can see all the details here:
https://gitlab.freedesktop.org/drm/amd/-/work_items/3425#note_3338643

Best regards,
Timur



  reply	other threads:[~2026-08-24 15:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24 14:47 [PATCH] drm/amd/pm/smu7: Don't send VddC_Request on CI Petr Belyaev
2026-08-24 15:07 ` Timur Kristóf [this message]
2026-08-24 16:11   ` Petr Belyaev
2026-08-24 19:54     ` Timur Kristóf

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=GoS-FsT8QACGf_8gWuUlnQ@gmail.com \
    --to=timur.kristof@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=upcfrost@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 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.