From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
alsa-devel@kernel.org
Cc: tiwai@suse.de, broonie@kernel.org, torvalds@linux-foundation.org,
vinod.koul@intel.com, liam.r.girdwood@linux.intel.com,
arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/9] ASoC: Intel: Kconfig: Simplify-clarify ACPI/PCI dependencies
Date: Fri, 15 Dec 2017 12:58:43 +0200 [thread overview]
Message-ID: <1513335523.7000.95.camel@linux.intel.com> (raw)
In-Reply-To: <20171215004451.30800-3-pierre-louis.bossart@linux.intel.com>
On Thu, 2017-12-14 at 18:44 -0600, Pierre-Louis Bossart wrote:
> PCI/ACPI selections should not happen in Kconfig for machine drivers,
> move to SOC selections.
>
> Add distinction between PCI and ACPI HiFi2 platforms and help text.
>
> There should be no functionality change.
>
> The PCI-based platforms may be removed at some point since Medfield
> is not really supported by anyone, and with Edison now defunct support
> for
> Merrifield/Edison is to be determined.
>
> - depends on SND_DMA_SGBUF
> + depends on SND_DMA_SGBUF && ACPI
> depends on DMADEVICES
Perhaps
depends on DMADEVICES && ACPI
to be in align with below?
> config SND_SOC_INTEL_BAYTRAIL
> tristate "Intel ASoC SST driver for Baytrail (legacy)"
> - depends on DMADEVICES
> + depends on DMADEVICES && ACPI
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-12-15 11:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 0:44 [PATCH 0/9] ASoC: Intel: Kconfig fixes Pierre-Louis Bossart
2017-12-15 0:44 ` [PATCH 1/9] ASoC: Intel: Fix Kconfig with top-level selector Pierre-Louis Bossart
2017-12-15 11:07 ` Takashi Iwai
2017-12-15 12:30 ` Pierre-Louis Bossart
2017-12-19 10:17 ` Takashi Iwai
2017-12-15 11:10 ` Andy Shevchenko
2017-12-15 0:44 ` [PATCH 2/9] ASoC: Intel: Kconfig: Simplify-clarify ACPI/PCI dependencies Pierre-Louis Bossart
2017-12-15 10:58 ` Andy Shevchenko [this message]
2017-12-15 12:34 ` Pierre-Louis Bossart
2017-12-19 10:49 ` Andy Shevchenko
2017-12-19 12:43 ` Pierre-Louis Bossart
2017-12-15 0:44 ` [PATCH 3/9] ASoC: Intel: document what Kconfig options do Pierre-Louis Bossart
2017-12-15 10:56 ` Andy Shevchenko
2017-12-15 0:44 ` [PATCH 4/9] ASoC: Intel: Fix nested/unnecessary Kconfig dependencies Pierre-Louis Bossart
2017-12-15 0:44 ` [PATCH 5/9] ASoC: Intel: boards: align Kconfig dependencies for Haswell/Broadwell Pierre-Louis Bossart
2017-12-15 0:44 ` [PATCH 6/9] ASoC: Intel: boards: align Kconfig configurations for HiFi2 Pierre-Louis Bossart
2017-12-15 10:53 ` Andy Shevchenko
2017-12-15 0:44 ` [PATCH 7/9] ASoC: Intel: boards: align/fix SKL/BXT/KBL Kconfigs Pierre-Louis Bossart
2017-12-15 0:44 ` [PATCH 8/9] ASoC: Intel: kconfig: add some comments for if symbols Pierre-Louis Bossart
2017-12-15 0:44 ` [PATCH 9/9] ASoC: Intel: kconfig: drop boiler plate text from config items Pierre-Louis Bossart
2017-12-15 10:51 ` Andy Shevchenko
2017-12-15 5:34 ` [PATCH 0/9] ASoC: Intel: Kconfig fixes Vinod Koul
2017-12-15 11:06 ` 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=1513335523.7000.95.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alsa-devel@kernel.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.