From: "Mukunda,Vijendar" <vijendar.mukunda@amd.com>
To: Julian Braha <julianbraha@gmail.com>,
broonie@kernel.org, perex@perex.cz, tiwai@suse.com,
pierre-louis.bossart@linux.intel.com
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
fazilyildiran@gmail.com
Subject: Re: [PATCH RESEND] ASoC: fix unmet dependencies on GPIOLIB for SND_SOC_DMIC
Date: Thu, 28 Oct 2021 18:09:40 +0530 [thread overview]
Message-ID: <6ff76018-309d-349e-691a-f504ca29420e@amd.com> (raw)
In-Reply-To: <20211027184835.112916-1-julianbraha@gmail.com>
On 10/28/21 12:18 AM, Julian Braha wrote:
> When SND_SOC_AMD_RENOIR_MACH or SND_SOC_AMD_RV_RT5682_MACH
> are selected, and GPIOLIB is not selected, Kbuild gives
> the following warnings, respectively:
>
> WARNING: unmet direct dependencies detected for SND_SOC_DMIC
> Depends on [n]: SOUND [=y] && !UML && SND [=y] && SND_SOC [=y] && GPIOLIB [=n]
> Selected by [y]:
> - SND_SOC_AMD_RENOIR_MACH [=y] && SOUND [=y] && !UML && SND [=y] && SND_SOC [=y] && SND_SOC_AMD_RENOIR [=y]
>
> and
>
> WARNING: unmet direct dependencies detected for SND_SOC_MAX98357A
> Depends on [n]: SOUND [=y] && !UML && SND [=y] && SND_SOC [=y] && GPIOLIB [=n]
> Selected by [y]:
> - SND_SOC_AMD_RV_RT5682_MACH [=y] && SOUND [=y] && !UML && SND [=y] && SND_SOC [=y] && SND_SOC_AMD_ACP3x [=y] && I2C [=y] && CROS_EC [=y]
>
> This is because SND_SOC_DMIC and SND_SOC_MAX98357A are
> selected by SND_SOC_AMD_RV_RT5682_MACH and SND_SOC_AMD_RENOIR_MACH,
> respectively. However, neither of the selectors depend on or select GPIOLIB,
> despite their selectees depending on GPIOLIB.
>
> These unmet dependency bugs were detected by Kismet,
> a static analysis tool for Kconfig. Please advise if this
> is not the appropriate solution.
>
> Signed-off-by: Julian Braha <julianbraha@gmail.com>
> ---
> sound/soc/amd/Kconfig | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/sound/soc/amd/Kconfig b/sound/soc/amd/Kconfig
> index 56e7c079deac..2c6af3f8f296 100644
> --- a/sound/soc/amd/Kconfig
> +++ b/sound/soc/amd/Kconfig
> @@ -38,7 +38,7 @@ config SND_SOC_AMD_RV_RT5682_MACH
> select I2C_CROS_EC_TUNNEL
> select SND_SOC_RT1015
> select SND_SOC_RT1015P
> - depends on SND_SOC_AMD_ACP3x && I2C && CROS_EC
> + depends on SND_SOC_AMD_ACP3x && I2C && CROS_EC && GPIOLIB
> help
> This option enables machine driver for RT5682 and MAX9835.
>
> @@ -51,7 +51,7 @@ config SND_SOC_AMD_RENOIR
> config SND_SOC_AMD_RENOIR_MACH
> tristate "AMD Renoir support for DMIC"
> select SND_SOC_DMIC
> - depends on SND_SOC_AMD_RENOIR
> + depends on SND_SOC_AMD_RENOIR && GPIOLIB
For Renoir platform, DMIC driver selected for registering codec dai with
ASOC. No additional functionality handled related to GPIO.
Do you still see necessity adding GPIOLIB dependency?
> help
> This option enables machine driver for DMIC
>
> --
> 2.30.2
>
next prev parent reply other threads:[~2021-10-28 12:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 18:48 Julian Braha
2021-10-28 12:28 ` Mark Brown
2021-10-28 15:23 ` Julian Braha
2021-10-28 12:39 ` Mukunda,Vijendar [this message]
2021-10-28 15:31 ` Julian Braha
2021-10-28 12:59 ` 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=6ff76018-309d-349e-691a-f504ca29420e@amd.com \
--to=vijendar.mukunda@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=fazilyildiran@gmail.com \
--cc=julianbraha@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.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 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®