AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Timur Kristóf" <timur.kristof@gmail.com>
To: contact@mikaelpelle.com
Cc: amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/amd/pm/si: Check AMD_IS_MOBILITY flag for PPSMC_SYSTEMFLAG_GPIO_DC
Date: Sat, 17 Oct 2026 11:38:04 -0600	[thread overview]
Message-ID: <a2FoeEsiQmiOiZVMEFL_8Q@gmail.com> (raw)
In-Reply-To: <000801dd5dbb$2a3de5b0$7eb9b110$@mikaelpelle.com>

On 2026. október 16., péntek 16:10:32 középső államokbeli zónaidő 
contact@mikaelpelle.com wrote:
> Hi Timur,
> 
> A quick follow-up from the same MacPro6,1 with dual FirePro D700s.
> I have now tested the fixes after they reached stock stable kernels:
>
> - Linux 6.18.57-1-lts: 
>   both GPUs correctly transition from 300/150 MHz idle to 850/1370 MHz under
> Vulkan compute load, then return to 300/150 MHz afterward.
> 
> - Linux 7.2.10-arch1-1:
>   same result; both D700s reach 850/1370 MHz correctly under load.
> 
> For comparison, Linux 7.2.9, before these stable backports, still kept both
> GPUs at 300/150 MHz under the same type of compute workload.
> 
> So I can confirm that the stable backports of:
>   drm/amd/pm/si: Check AMD_IS_MOBILITY flag for PPSMC_SYSTEMFLAG_GPIO_DC
>   drm/amd/pm/si: Fix updating clock limits on AC/DC
> resolve the DPM issue on the dual FirePro D700 in the MacPro6,1.
> 
> Thanks for the fixes.
> 

Hi Mikael,

Thank you for testing.
I'm happy to hear that the patches are working well for you!

Best regards,
Timur





  reply	other threads:[~2026-10-17 17:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-09-27  0:48 contact
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=a2FoeEsiQmiOiZVMEFL_8Q@gmail.com \
    --to=timur.kristof@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=contact@mikaelpelle.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