From: "Arnd Bergmann" <arnd@arndb.de>
To: "Julian Braha" <julianbraha@gmail.com>,
"Cezary Rojewski" <cezary.rojewski@intel.com>,
"Peter Ujfalusi" <peter.ujfalusi@linux.intel.com>,
"Ranjani Sridharan" <ranjani.sridharan@linux.intel.com>,
"Mark Brown" <broonie@kernel.org>
Cc: linux-sound@vger.kernel.org, liam.r.girdwood@linux.intel.com,
"Bard Liao" <yung-chuan.liao@linux.intel.com>,
"Kai Vehmanen" <kai.vehmanen@linux.intel.com>,
"Pierre-Louis Bossart" <pierre-louis.bossart@linux.dev>,
"Jaroslav Kysela" <perex@perex.cz>,
david.lin@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: Intel: boards: fix unmet dependency on PINCTRL
Date: Sun, 22 Mar 2026 22:06:50 +0100 [thread overview]
Message-ID: <b8aecc71-1fed-4f52-9f6c-263fbe56d493@app.fastmail.com> (raw)
In-Reply-To: <20260322194847.1126372-1-julianbraha@gmail.com>
On Sun, Mar 22, 2026, at 20:48, Julian Braha wrote:
> Currently, SND_SOC_INTEL_SOUNDWIRE_SOF_MACH selects PINCTRL_CS42L43
> without also selecting or depending on PINCTRL, despite PINCTRL_CS42L43
> depending on PINCTRL.
>
> See the following Kbuild warning:
>
> WARNING: unmet direct dependencies detected for PINCTRL_CS42L43
> Depends on [n]: PINCTRL [=n] && MFD_CS42L43 [=m]
> Selected by [m]:
> - SND_SOC_INTEL_SOUNDWIRE_SOF_MACH [=m] && SOUND [=y] && SND [=m] &&
> SND_SOC [=m] && SND_SOC_INTEL_MACH [=y] && (SND_SOC_SOF_INTEL_COMMON
> [=m] || !SND_SOC_SOF_INTEL_COMMON [=m]) && SND_SOC_SOF_INTEL_SOUNDWIRE
> [=m] && I2C [=y] && SPI_MASTER [=y] && ACPI [=y] && (MFD_INTEL_LPSS
> [=n] || COMPILE_TEST [=y]) && (SND_SOC_INTEL_USER_FRIENDLY_LONG_NAMES
> [=n] || COMPILE_TEST [=y]) && SOUNDWIRE [=m]
>
> This unmet dependency was detected by kconfirm, a static analysis
> tool for Kconfig.
>
> Fixes: c073f0757663 ("ASoC: Intel: sof_sdw: select PINCTRL_CS42L43 and
> SPI_CS42L43")
> Signed-off-by: Julian Braha <julianbraha@gmail.com>
I don't see any compile-time dependency between sof_sdw and
the PINCTRL_CS42L43 driver and I wonder if it would be better
to instead revert that patch.
It is generally a bad idea for an individual device driver
to force-enable another subsystem or a driver from another
subsystem, as that increases the risk for dependency loops
and makes it harder to turn subsystems off entirely.
Arnd
prev parent reply other threads:[~2026-03-22 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-22 19:48 Julian Braha
2026-03-22 21:06 ` Arnd Bergmann [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=b8aecc71-1fed-4f52-9f6c-263fbe56d493@app.fastmail.com \
--to=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=david.lin@intel.com \
--cc=julianbraha@gmail.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=ranjani.sridharan@linux.intel.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 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®