From: Lee Jones <lee@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Mark Brown <broonie@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Benjamin Gray <bgray@linux.ibm.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] regmap: REGMAP_SLIMBUS should select REGMAP
Date: Wed, 12 Jul 2023 12:58:04 +0100 [thread overview]
Message-ID: <20230712115804.GC10768@google.com> (raw)
In-Reply-To: <7519324a34015e1c046227269409fef688889f4f.1688643442.git.geert@linux-m68k.org>
On Thu, 06 Jul 2023, Geert Uytterhoeven wrote:
> If CONFIG_SND_SOC_WCD934X=y, CONFIG_COMPILE_TEST=y,
> CONFIG_MFD_WCD934X=n, CONFIG_REGMAP=n:
>
> sound/soc/codecs/wcd934x.c:518:38: error: array type has incomplete element type ‘struct regmap_range_cfg’
> 518 | static const struct regmap_range_cfg wcd934x_ifc_ranges[] = {
> | ^~~~~~~~~~~~~~~~~~
>
> Fix this by making REGMAP_SLIMBUS select REGMAP.
>
> Drop the selection of REGMAP by MFD_WCD934X, as this is not needed
> (now both REGMAP_SLIMBUS and REGMAP_IRQ select REGMAP).
>
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> ---
> drivers/base/regmap/Kconfig | 1 +
> drivers/mfd/Kconfig | 1 -
Acked-by: Lee Jones <lee@kernel.org>
> 2 files changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/base/regmap/Kconfig b/drivers/base/regmap/Kconfig
> index e25cc619c75de3d9..c3a260ed4e864959 100644
> --- a/drivers/base/regmap/Kconfig
> +++ b/drivers/base/regmap/Kconfig
> @@ -34,6 +34,7 @@ config REGMAP_I2C
> config REGMAP_SLIMBUS
> tristate
> depends on SLIMBUS
> + select REGMAP
>
> config REGMAP_SPI
> tristate
> diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
> index 0b6af476f554a191..5857dad2c64828fa 100644
> --- a/drivers/mfd/Kconfig
> +++ b/drivers/mfd/Kconfig
> @@ -2121,7 +2121,6 @@ config MFD_STMFX
> config MFD_WCD934X
> tristate "Support for WCD9340/WCD9341 Codec"
> depends on SLIMBUS
> - select REGMAP
> select REGMAP_SLIMBUS
> select REGMAP_IRQ
> select MFD_CORE
> --
> 2.34.1
>
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-07-12 11:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 11:42 [PATCH 0/3] regmap: Fix REGMAP selections Geert Uytterhoeven
2023-07-06 11:42 ` [PATCH 1/3] regmap: Replace "default y if" by select Geert Uytterhoeven
2023-07-06 12:33 ` Mark Brown
2023-07-06 11:42 ` [PATCH 2/3] regmap: REGMAP_SLIMBUS should select REGMAP Geert Uytterhoeven
2023-07-06 12:18 ` Mark Brown
2023-07-06 12:28 ` Geert Uytterhoeven
2023-07-12 11:58 ` Lee Jones [this message]
2023-07-06 11:42 ` [PATCH 3/3] ASoC: codecs: SND_SOC_WCD934X should select REGMAP_IRQ Geert Uytterhoeven
2023-07-06 12:09 ` Mark Brown
2023-07-06 12:15 ` Geert Uytterhoeven
2023-07-06 12:18 ` Mark Brown
2023-07-11 20:44 ` (subset) [PATCH 0/3] regmap: Fix REGMAP selections 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=20230712115804.GC10768@google.com \
--to=lee@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgray@linux.ibm.com \
--cc=broonie@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=rafael@kernel.org \
--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