From: "André Eikmeyer" <dev@deq.rocks>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: "Ed Schofield" <ed@aicharmers.com>,
amd-gfx@lists.freedesktop.org,
"Kenneth Feng" <kenneth.feng@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Atharva Tiwari" <atharvatiwarilinuxdev@gmail.com>,
"Christian König" <christian.koenig@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] drm/amd/pm: defer UCLK DPM on selected Apple Navi GPUs
Date: Tue, 3 Nov 2026 17:15:28 +0100 [thread overview]
Message-ID: <20261103171528.6c6a0edf@kait2en-mbp15-1> (raw)
In-Reply-To: <CADnq5_NDJ7V=TQLOJ37msbmhwsVG+70mPKU3ns+xmAu9jxWwcg@mail.gmail.com>
On Tue, 3 Nov 2026 10:53:56 -0500
Alex Deucher <alexdeucher@gmail.com> wrote:
> I forgot to remove the pptable check. Can you try a simplified
> version of the patch? I think all you need to do is delay the UCLK
> DPM enablement until late_init. Something like the attached patch.
Alex, as I told you earlier. I don't own a 16,1. I developed the patch
I submitted. It took me months to figure out while debugging via ssh.
Currently a community of nearly 6000 people are happily using it.
I dont understand your fixation towards a patch that fixes nothing. I
dont understand why you write patches based on obvious slop without even
being able to test. And I dont see why I should help you with it. There
is simply no point in it.
prev parent reply other threads:[~2026-11-03 16:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 14:40 Ed Schofield
2026-10-29 21:57 ` Alex Deucher
2026-10-30 1:55 ` Atharva Tiwari
2026-10-30 11:30 ` André Eikmeyer
2026-11-03 14:30 ` Alex Deucher
2026-11-03 15:00 ` Atharva Tiwari
2026-11-03 15:14 ` Alex Deucher
2026-11-03 15:59 ` André Eikmeyer
2026-11-03 16:00 ` Aditya Garg
2026-11-04 12:52 ` Ed Schofield
2026-11-04 14:07 ` Alex Deucher
2026-11-04 14:20 ` Aditya Garg
2026-11-03 15:25 ` André Eikmeyer
2026-11-03 15:53 ` Alex Deucher
2026-11-03 16:05 ` Atharva Tiwari
2026-11-03 16:15 ` André Eikmeyer [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=20261103171528.6c6a0edf@kait2en-mbp15-1 \
--to=dev@deq.rocks \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=atharvatiwarilinuxdev@gmail.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ed@aicharmers.com \
--cc=kenneth.feng@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=simona@ffwll.ch \
/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
all inboxes | Powered by JetHome®