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 16:25:12 +0100 [thread overview]
Message-ID: <20261103162512.2ec834ac@kait2en-mbp15-1> (raw)
In-Reply-To: <CADnq5_NCB6ur05ZvP0fe9hsgLHM0=y_Wx31G4vkpKH+F7yZ74g@mail.gmail.com>
On Tue, 3 Nov 2026 09:30:34 -0500
Alex Deucher <alexdeucher@gmail.com> wrote:
> It is the same issue. I don't want two fixes for the same issue.
Understandable, but it is not. Two devs told you the same
independently.
On another note I reviewed your patch. It only rejects empty or zero
levels. On the 16,1 the pptable levels (736/750 MHz) are non-zero.
Besides other issues in the code, the commit message says the exact
patch wasn't tested, yet v5 extends it to every Apple Navi 1x.
I am sorry but your patch is implausible to me.
Andre
next prev parent reply other threads:[~2026-11-03 15:25 UTC|newest]
Thread overview: 13+ 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-03 15:25 ` André Eikmeyer [this message]
2026-11-03 15:53 ` Alex Deucher
2026-11-03 16:05 ` Atharva Tiwari
2026-11-03 16:15 ` André Eikmeyer
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=20261103162512.2ec834ac@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®