From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: "Feng, Kenneth" <Kenneth.Feng@amd.com>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
"Koenig, Christian" <Christian.Koenig@amd.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: questions about smu_mode2_reset_is_support and smu_v13_0_init_display_count
Date: Wed, 7 May 2025 17:22:22 +0000 [thread overview]
Message-ID: <aBuWzlWN5uJqsV90@gallifrey> (raw)
In-Reply-To: <DM4PR12MB5165D85BD85BC8FC8BF7A3B48E88A@DM4PR12MB5165.namprd12.prod.outlook.com>
* Feng, Kenneth (Kenneth.Feng@amd.com) wrote:
> [AMD Official Use Only - AMD Internal Distribution Only]
>
> Hello Dave,
Hi Kenneth,
Thanks for the reply.
> smu_v13_0_init_display_count() is obsolete on smu13 series. It will be removed.
> Secondly, with cod evolving, all of below can be removed as well.
> sienna_cichlid_is_mode2_reset_supported,
> aldebaran_is_mode2_reset_supported,
> smu_v13_0_6_is_mode2_reset_supported
Great, I've sent a series to delete all those, see 20250507170145.102508-1-linux@treblig.org
Dave
> Thanks.
>
>
>
> -----Original Message-----
> From: Dr. David Alan Gilbert <linux@treblig.org>
> Sent: Wednesday, May 7, 2025 8:32 AM
> To: Deucher, Alexander <Alexander.Deucher@amd.com>; Feng, Kenneth <Kenneth.Feng@amd.com>; Koenig, Christian <Christian.Koenig@amd.com>
> Cc: amd-gfx@lists.freedesktop.org; linux-kernel@vger.kernel.org
> Subject: questions about smu_mode2_reset_is_support and smu_v13_0_init_display_count
>
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>
>
> Hi,
> I noticed two functions that are unused but I wasn't sure what to do with them:
>
> smu_v13_0_init_display_count() isn't called/wired up, where as the
> v11 version is wired up:
>
> drivers/gpu/drm/amd/pm/swsmu/smu11/navi10_ppt.c
> 3574: .init_display_count = smu_v11_0_init_display_count,
>
> so is v13 really unused or should it be wired up in a similar way?
>
> secondly, smu_mode2_reset_is_support() is uncalled, but it's the only caller through the mode2_reset_is_support() function pointer; so if smu_mode2_reset_is_support() was deleted, does it then make sense to clean up all of
> sienna_cichlid_is_mode2_reset_supported,
> aldebaran_is_mode2_reset_supported,
> smu_v13_0_6_is_mode2_reset_supported
>
> which that function pointer is sett to.
>
> Thanks in advance,
>
> Dave
>
> --
> -----Open up your eyes, open up your mind, open up your code -------
> / Dr. David Alan Gilbert | Running GNU/Linux | Happy \
> \ dave @ treblig.org | | In Hex /
> \ _________________________|_____ http://www.treblig.org |_______/
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
prev parent reply other threads:[~2025-05-07 17:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 0:32 questions about smu_mode2_reset_is_support and smu_v13_0_init_display_count Dr. David Alan Gilbert
2025-05-07 2:21 ` Feng, Kenneth
2025-05-07 17:22 ` Dr. David Alan Gilbert [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=aBuWzlWN5uJqsV90@gallifrey \
--to=linux@treblig.org \
--cc=Alexander.Deucher@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=Kenneth.Feng@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
/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