From: Lizhi Hou <lizhi.hou@amd.com>
To: "Liam R. Howlett" <liam@infradead.org>,
Mario Limonciello <superm1@kernel.org>
Cc: Min Ma <mamin506@gmail.com>, Oded Gabbay <ogabbay@kernel.org>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] accel/amdxdna: Fix Kconfig invalid configuration
Date: Fri, 9 Oct 2026 08:59:55 -0700 [thread overview]
Message-ID: <694d6976-4b2b-650b-ffe1-77f5f3cdd65d@amd.com> (raw)
In-Reply-To: <20261009011010.3521631-1-liam@infradead.org>
On 10/8/26 18:10, Liam R. Howlett wrote:
> The amdxdna has a soft dependency on the amd_pmf module. It will use an
> exported function if it is available and fall back to another function
> if it is not enabled.
>
> amdxdna and amd_pmf are tridstate modules supporting both built [y] and
> modularized [m] in the .config file. Since the amdxdna decides to use
> the amd_pmf if it is either a module or built in (see
> drivers/accel/amdxdna/aie2_pci.h), then there is an issue if they are
> not compiled either both as modules or both as built-in.
>
> Adding the optional dependency to Kconfig does not allow the
> configuration from being selected.
>
> Fixes: f66d6cc6891e4 ("accel/amdxdna: Support sensors for column utilization")
> Signed-off-by: Liam R. Howlett <liam@infradead.org>
> ---
> drivers/accel/amdxdna/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/accel/amdxdna/Kconfig b/drivers/accel/amdxdna/Kconfig
> index f39d7a87296cd..eddff490b4f75 100644
> --- a/drivers/accel/amdxdna/Kconfig
> +++ b/drivers/accel/amdxdna/Kconfig
> @@ -6,6 +6,7 @@ config DRM_ACCEL_AMDXDNA
> depends on DRM_ACCEL
> depends on PCI && HAS_IOMEM
> depends on X86_64
> + depends on AMD_PMF || !AMD_PMF
Reviewed-by: Lizhi Hou <lizhi.hou@amd.com>
> select DRM_SCHED
> select DRM_GEM_SHMEM_HELPER
> select FW_LOADER
prev parent reply other threads:[~2026-10-09 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 1:10 Liam R. Howlett
2026-10-09 15:59 ` Lizhi Hou [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=694d6976-4b2b-650b-ffe1-77f5f3cdd65d@amd.com \
--to=lizhi.hou@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mamin506@gmail.com \
--cc=ogabbay@kernel.org \
--cc=superm1@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
all inboxes | Powered by JetHome®