From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: alsa-devel@alsa-project.org
Cc: tiwai@suse.de, broonie@kernel.org, torvalds@linux-foundation.org,
vinod.koul@intel.com, liam.r.girdwood@linux.intel.com,
andriy.shevchenko@linux.intel.com, arnd@arndb.de,
linux-kernel@vger.kernel.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: [PATCH v2 5/9] ASoC: Intel: Fix nested/unnecessary Kconfig dependencies
Date: Wed, 3 Jan 2018 10:50:18 -0600 [thread overview]
Message-ID: <20180103165022.4984-6-pierre-louis.bossart@linux.intel.com> (raw)
In-Reply-To: <20180103165022.4984-1-pierre-louis.bossart@linux.intel.com>
This patch fixes a number of issues:
1. IOSF_MBI is only needed for byt-cr detection, which is only supported
on Baytrail/Cherrytrail, move to HiFi2 config
2. SND_SOC_INTEL_SST should not select SND_SOC_INTEL_SST_ACPI, the latter
config is only valid for Haswell/Baytrail legacy but not needed by Skylake
3. SND_SST_IPC_ACPI, used only by the atom/sst driver, should not select
SND_SOC_INTEL_SST, none of the code under common/sst*.c is used
This nesting of configs really makes no sense, it's easier to maintain
if for each platform one can control what is strictly required.
Compiled-tested with each of Haswell, Baytrail legacy, HiFi2, SKL cases
selected independently. 0-day and explicit randconfig tests did not report
additional issues and no functionality loss was observed in Intel tests on
HIFI2 and SKYLAKE platforms
Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
---
sound/soc/intel/Kconfig | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/sound/soc/intel/Kconfig b/sound/soc/intel/Kconfig
index 01b75df6b118..b75fa5f59b96 100644
--- a/sound/soc/intel/Kconfig
+++ b/sound/soc/intel/Kconfig
@@ -27,8 +27,6 @@ config SND_SST_IPC_PCI
config SND_SST_IPC_ACPI
tristate
select SND_SST_IPC
- select SND_SOC_INTEL_SST
- select IOSF_MBI
# This option controls the ACPI-based IPC for HiFi2 platforms
# (Baytrail, Cherrytrail)
@@ -40,7 +38,6 @@ config SND_SOC_INTEL_SST_ACPI
config SND_SOC_INTEL_SST
tristate
- select SND_SOC_INTEL_SST_ACPI if ACPI
config SND_SOC_INTEL_SST_FIRMWARE
tristate
@@ -54,6 +51,7 @@ config SND_SOC_INTEL_HASWELL
depends on SND_DMA_SGBUF
depends on DMADEVICES && ACPI
select SND_SOC_INTEL_SST
+ select SND_SOC_INTEL_SST_ACPI
select SND_SOC_INTEL_SST_FIRMWARE
select SND_SOC_ACPI_INTEL_MATCH
help
@@ -65,6 +63,7 @@ config SND_SOC_INTEL_BAYTRAIL
tristate "Intel ASoC SST driver for Baytrail (legacy)"
depends on DMADEVICES && ACPI
select SND_SOC_INTEL_SST
+ select SND_SOC_INTEL_SST_ACPI
select SND_SOC_INTEL_SST_FIRMWARE
select SND_SOC_ACPI_INTEL_MATCH
help
@@ -91,6 +90,7 @@ config SND_SST_ATOM_HIFI2_PLATFORM
tristate "Intel ASoC SST driver for ACPI HiFi2 platforms (Baytrail, Cherrytrail)"
depends on X86 && ACPI
select SND_SST_IPC_ACPI
+ select IOSF_MBI
select SND_SOC_COMPRESS
select SND_SOC_ACPI_INTEL_MATCH
help
--
2.14.1
next prev parent reply other threads:[~2018-01-03 16:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 16:50 [PATCH v2 0/9] ASoC: Intel: Kconfig+acpi fixes Pierre-Louis Bossart
2018-01-03 16:50 ` [PATCH v2 1/9] ASoC: acpi: add missing includes for non-ACPI platforms Pierre-Louis Bossart
2018-01-08 16:23 ` Applied "ASoC: acpi: add missing includes for non-ACPI platforms" to the asoc tree Mark Brown
2018-01-03 16:50 ` [PATCH v2 2/9] ASoC: Intel: Fix Kconfig with top-level selector Pierre-Louis Bossart
2018-01-08 16:22 ` Applied "ASoC: Intel: Fix Kconfig with top-level selector" to the asoc tree Mark Brown
2018-01-03 16:50 ` [PATCH v2 3/9] ASoC: Intel: Kconfig: Simplify-clarify ACPI/PCI dependencies Pierre-Louis Bossart
2018-01-08 16:22 ` Applied "ASoC: Intel: Kconfig: Simplify-clarify ACPI/PCI dependencies" to the asoc tree Mark Brown
2018-01-03 16:50 ` [PATCH v2 4/9] ASoC: Intel: document what Kconfig options do Pierre-Louis Bossart
2018-01-08 16:22 ` Applied "ASoC: Intel: document what Kconfig options do" to the asoc tree Mark Brown
2018-01-03 16:50 ` Pierre-Louis Bossart [this message]
2018-01-03 16:56 ` [PATCH v2 5/9] ASoC: Intel: Fix nested/unnecessary Kconfig dependencies Andy Shevchenko
2018-01-03 18:09 ` Andy Shevchenko
2018-01-03 16:50 ` [PATCH v2 6/9] ASoC: Intel: boards: align Kconfig dependencies for Haswell/Broadwell Pierre-Louis Bossart
2018-01-03 16:50 ` [PATCH v2 7/9] ASoC: Intel: boards: align Kconfig configurations for HiFi2 Pierre-Louis Bossart
2018-01-08 16:21 ` Applied "ASoC: Intel: boards: align Kconfig configurations for HiFi2" to the asoc tree Mark Brown
2018-01-03 16:50 ` [PATCH v2 8/9] ASoC: Intel: boards: align/fix SKL/BXT/KBL Kconfigs Pierre-Louis Bossart
2018-01-03 17:00 ` Andy Shevchenko
2018-01-03 16:50 ` [PATCH v2 9/9] ASoC: Intel: kconfig: add some comments for if symbols Pierre-Louis Bossart
2018-01-03 17:07 ` Andy Shevchenko
2018-01-03 19:25 ` Randy Dunlap
2018-01-03 19:51 ` Pierre-Louis Bossart
2018-01-03 17:09 ` [PATCH v2 0/9] ASoC: Intel: Kconfig+acpi fixes Andy Shevchenko
2018-01-03 18:52 ` Pierre-Louis Bossart
2018-01-03 19:10 ` Andy Shevchenko
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=20180103165022.4984-6-pierre-louis.bossart@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.org \
--cc=vinod.koul@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®