From: Mario Limonciello <superm1@kernel.org>
To: mario.limonciello@amd.com, lgirdwood@gmail.com,
peter.ujfalusi@linux.intel.com, yung-chuan.liao@linux.intel.com,
ranjani.sridharan@linux.intel.com, daniel.baluta@nxp.com,
broonie@kernel.org, perex@perex.cz, tiwai@suse.com
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
sound-open-firmware@alsa-project.org,
linux-sound@vger.kernel.org
Subject: [PATCH] ASoC: SOF: amd: Add depends on CPU_SUP_AMD
Date: Thu, 20 Feb 2025 10:51:26 -0600 [thread overview]
Message-ID: <20250220165127.492927-1-superm1@kernel.org> (raw)
From: Mario Limonciello <mario.limonciello@amd.com>
When SMN support was switched to the kernel wide AMD_NODE instead of
local implementation this broke compilation on the allyesconfig for
some architectures. AMD_NODE is only supported on AMD platforms, so
modify all the AMD drivers that use it to also require CPU_SUP_AMD.
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Closes: https://lore.kernel.org/linux-next/20250220160950.2cd64bdb@canb.auug.org.au/
Fixes: f120cf33d232 ("ASoC: SOF: amd: Use AMD_NODE")
---
sound/soc/sof/amd/Kconfig | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/sound/soc/sof/amd/Kconfig b/sound/soc/sof/amd/Kconfig
index 28216c8c1cf97..6eb5b2d148430 100644
--- a/sound/soc/sof/amd/Kconfig
+++ b/sound/soc/sof/amd/Kconfig
@@ -33,6 +33,7 @@ config SND_SOC_SOF_AMD_COMMON
config SND_SOC_SOF_AMD_RENOIR
tristate "SOF support for RENOIR"
depends on SND_SOC_SOF_PCI
+ depends on CPU_SUP_AMD
select SND_SOC_SOF_AMD_COMMON
help
Select this option for SOF support on AMD Renoir platform
@@ -40,6 +41,7 @@ config SND_SOC_SOF_AMD_RENOIR
config SND_SOC_SOF_AMD_VANGOGH
tristate "SOF support for VANGOGH"
depends on SND_SOC_SOF_PCI
+ depends on CPU_SUP_AMD
select SND_SOC_SOF_AMD_COMMON
help
Select this option for SOF support
@@ -50,6 +52,7 @@ config SND_SOC_SOF_AMD_VANGOGH
config SND_SOC_SOF_AMD_REMBRANDT
tristate "SOF support for REMBRANDT"
depends on SND_SOC_SOF_PCI
+ depends on CPU_SUP_AMD
select SND_SOC_SOF_AMD_COMMON
help
Select this option for SOF support on AMD Rembrandt platform
@@ -82,6 +85,7 @@ config SND_SOC_SOF_AMD_SOUNDWIRE
config SND_SOC_SOF_AMD_ACP63
tristate "SOF support for ACP6.3 platform"
depends on SND_SOC_SOF_PCI
+ depends on CPU_SUP_AMD
select SND_SOC_SOF_AMD_COMMON
select SND_SOC_SOF_AMD_SOUNDWIRE_LINK_BASELINE
help
@@ -93,6 +97,7 @@ config SND_SOC_SOF_AMD_ACP63
config SND_SOC_SOF_AMD_ACP70
tristate "SOF support for ACP7.0 platform"
depends on SND_SOC_SOF_PCI
+ depends on CPU_SUP_AMD
select SND_SOC_SOF_AMD_COMMON
help
Select this option for SOF support on
--
2.43.0
next reply other threads:[~2025-02-20 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 16:51 Mario Limonciello [this message]
2025-02-20 18:43 ` [PATCH] ASoC: SOF: amd: Add depends on CPU_SUP_AMD Mark Brown
2025-02-20 18:46 ` Mario Limonciello
-- strict thread matches above, loose matches on Subject: below --
2025-02-20 18:48 Mario Limonciello
2025-02-20 22:21 ` Mark Brown
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=20250220165127.492927-1-superm1@kernel.org \
--to=superm1@kernel.org \
--cc=broonie@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sfr@canb.auug.org.au \
--cc=sound-open-firmware@alsa-project.org \
--cc=tiwai@suse.com \
--cc=yung-chuan.liao@linux.intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.