From: Atharva Tiwari <atharvatiwarilinuxdev@gmail.com>
To: alexdeucher@gmail.com
Cc: 062bel313@gmail.com, Alexander.Deucher@amd.com,
Christian.Koenig@amd.com, Kenneth.Feng@amd.com,
airlied@gmail.com, amd-gfx@lists.freedesktop.org,
atharvatiwarilinuxdev@gmail.com, dri-devel@lists.freedesktop.org,
ed@aicharmers.com, linux-kernel@vger.kernel.org, simona@ffwll.ch
Subject: Re: [PATCH v2] drm/amd/pm: defer UCLK DPM enablement on Apple Navi 14
Date: Tue, 15 Sep 2026 19:20:43 -0400 [thread overview]
Message-ID: <20260915232043.1222-1-atharvatiwarilinuxdev@gmail.com> (raw)
In-Reply-To: <CADnq5_NyBdPbavmiPVdsHkP_Oi1w7ngX0kPSNce+BWN-YkuAFQ@mail.gmail.com>
> I can drop the patch if you feel strongly, although it is pretty
> similar your original patch, it just keeps all of the logic within
> navi10_ppt.c which is cleaner in my opinion rather than pulling navi1x
> specific logic into the core pm code.
>
> Alex
I dont have problem with the code, the problem is that, this is not the
solution to this problem, as i said in the previous, the solution lies
in the DC not the SMU (i tested by removing dce_v10_0_early_init and adding
that function to dce_v10_sw_init), it is also confirmed via the testing using
Opencore Lecacy patcher, which makes the display 5K, and make the display not
use compatibility mode (4K), and it also fixes the SMU problem.
(https://gitlab.freedesktop.org/drm/amd/-/work_items/4455)
You can choose to upstream this, i dont necessarily have a problem with this
patch as long as i am the patch author (eg using From: )
Thanks
prev parent reply other threads:[~2026-09-15 23:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 19:04 [PATCH] drm/amdgpu/smu: Enable UCLK after init in AMD Radeon Pro 5300 Atharva Tiwari
2026-09-09 7:05 ` Feng, Kenneth
2026-09-09 8:02 ` Ed Schofield
2026-09-09 8:39 ` Feng, Kenneth
2026-09-09 12:34 ` [PATCH v2] drm/amd/pm: defer UCLK DPM enablement on Apple Navi 14 Ed Schofield
2026-09-10 10:31 ` Feng, Kenneth
2026-09-10 13:21 ` Alex Deucher
2026-09-13 0:50 ` Atharva Tiwari
2026-09-14 14:21 ` Alex Deucher
2026-09-15 23:20 ` Atharva Tiwari [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=20260915232043.1222-1-atharvatiwarilinuxdev@gmail.com \
--to=atharvatiwarilinuxdev@gmail.com \
--cc=062bel313@gmail.com \
--cc=Alexander.Deucher@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=Kenneth.Feng@amd.com \
--cc=airlied@gmail.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ed@aicharmers.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®