[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yeb0n9AVXeVzBHrT@sirena.org.uk>
Date: Tue, 18 Jan 2022 17:10:55 +0000
From: Mark Brown <broonie@...nel.org>
To: Julian Braha <julianbraha@...il.com>
Cc: lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com,
Vijendar.Mukunda@....com, AjitKumar.Pandey@....com,
pierre-louis.bossart@...ux.intel.com, kai.vehmanen@...ux.intel.com,
tanureal@...nsource.cirrus.com, linux-kernel@...r.kernel.org,
alsa-devel@...a-project.org, fazilyildiran@...il.com
Subject: Re: [PATCH] ASoC: amd: fix unmet dependency on GPIOLIB for
SND_SOC_DMIC
On Sun, Jan 16, 2022 at 11:15:28PM -0500, Julian Braha wrote:
> When SND_SOC_AMD_YC_MACH is selected,
> and GPIOLIB is not selected,
> Kbuild gives the following warning:
>
> 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_YC_MACH [=y] && SOUND [=y] && !UML && SND [=y] && SND_SOC [=y] && SND_SOC_AMD_ACP6x [=y]
Why is this a good fix and not removing the dependency on gpiolib from
DMIC? While a DMIC *can* use a GPIO it's not something that's an
intrinsic requirement and it's entirely optional in the code.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists