From: <contact@mikaelpelle.com>
To: <timur.kristof@gmail.com>
Cc: <amd-gfx@lists.freedesktop.org>
Subject: [PATCH 1/2] drm/amd/pm/si: Check AMD_IS_MOBILITY flag for PPSMC_SYSTEMFLAG_GPIO_DC
Date: Sun, 27 Sep 2026 02:48:04 +0200 [thread overview]
Message-ID: <003801dd4e19$db9cacd0$92d60670$@mikaelpelle.com> (raw)
I tested this patch on a Late 2013 Mac Pro (MacPro6,1) with dual Apple FirePro D700 (Tahiti XT, 6 GB), and can confirm that it fixes the DPM issue on the D700 as well.
Test environment:
Arch Linux
Kernel: 6.18.54-1-lts + this patch
Mesa/RADV: 26.2.3
GPU: 2x FirePro D700 (Tahiti XT, 6 GB)
Params: radeon.si_support=0 amdgpu.si_support=1
Without the patch, both D700s remained at 300 MHz SCLK / 150 MHz MCLK under Vulkan compute load.
I checked the D700 VBIOS as well: ATOM_PP_PLATFORM_CAP_HARDWAREDC is set, and it contains a battery state at 300/150 MHz.
With the patch applied to the same kernel, each D700 correctly transitions from 300/150 MHz at idle to 850/1370 MHz under load. I tested both GPUs individually and simultaneously.
As a real-world test, Ollama/Qwen3-8B fully offloaded across both GPUs sustained approximately 18.3-18.7 tokens/s, compared with ~2.34 tokens/s before the patch. One API run generated 1517 tokens in 81.24 seconds.
I observed no amdgpu VM faults, GPU timeouts or resets during the tests.
Tested-by: Mikael Pelle contact@mikaelpelle.com
next reply other threads:[~2026-09-27 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 0:48 contact [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-10-16 22:10 [PATCH 1/2] drm/amd/pm/si: Check AMD_IS_MOBILITY flag for PPSMC_SYSTEMFLAG_GPIO_DC contact
2026-10-17 17:38 ` Timur Kristóf
2026-09-23 12:03 Timur Kristóf
2026-09-23 19:59 ` Mario Limonciello
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='003801dd4e19$db9cacd0$92d60670$@mikaelpelle.com' \
--to=contact@mikaelpelle.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=timur.kristof@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.