From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Jie Yang <yang.jie@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
alsa-devel@alsa-project.org, Vinod Koul <vinod.koul@intel.com>
Cc: dmaengine <dmaengine@vger.kernel.org>
Subject: Re: [PATCH 1/1] sst: select DW_DMAC_CORE since it's mandatory
Date: Fri, 18 Mar 2016 11:15:36 -0500 [thread overview]
Message-ID: <56EC29A8.3030400@linux.intel.com> (raw)
In-Reply-To: <1458303883.1347.141.camel@linux.intel.com>
On 3/18/16 7:24 AM, Andy Shevchenko wrote:
> On Fri, 2015-09-18 at 14:44 +0300, Andy Shevchenko wrote:
>> While here group selectors under SND_SOC_INTEL_HASWELL and
>> SND_SOC_INTEL_BAYTRAIL.
>
> It seems patch is not applied anymore.
> I will send v2 if no one objects on the approach.
I don't think DW_DMAC_CORE is mandatory at all for BAYTRAIL. We've have
a thread with Keyon on this.
>
>>
>> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>> ---
>> sound/soc/intel/Kconfig | 15 +++++----------
>> 1 file changed, 5 insertions(+), 10 deletions(-)
>>
>> diff --git a/sound/soc/intel/Kconfig b/sound/soc/intel/Kconfig
>> index 05fde5e6e..bc5281e 100644
>> --- a/sound/soc/intel/Kconfig
>> +++ b/sound/soc/intel/Kconfig
>> @@ -35,15 +35,17 @@ config SND_SOC_INTEL_SST_ACPI
>>
>> config SND_SOC_INTEL_HASWELL
>> tristate
>> + select DW_DMAC_CORE
>> + select SND_SOC_INTEL_SST
>>
>> config SND_SOC_INTEL_BAYTRAIL
>> tristate
>> + select DW_DMAC_CORE
>> + select SND_SOC_INTEL_SST
>>
>> config SND_SOC_INTEL_HASWELL_MACH
>> tristate "ASoC Audio DSP support for Intel Haswell
>> Lynxpoint"
>> depends on X86_INTEL_LPSS && I2C && I2C_DESIGNWARE_PLATFORM
>> - depends on DW_DMAC_CORE
>> - select SND_SOC_INTEL_SST
>> select SND_SOC_INTEL_HASWELL
>> select SND_SOC_RT5640
>> help
>> @@ -55,8 +57,6 @@ config SND_SOC_INTEL_HASWELL_MACH
>> config SND_SOC_INTEL_BYT_RT5640_MACH
>> tristate "ASoC Audio driver for Intel Baytrail with RT5640
>> codec"
>> depends on X86_INTEL_LPSS && I2C
>> - depends on DW_DMAC_CORE
>> - select SND_SOC_INTEL_SST
>> select SND_SOC_INTEL_BAYTRAIL
>> select SND_SOC_RT5640
>> help
>> @@ -66,8 +66,6 @@ config SND_SOC_INTEL_BYT_RT5640_MACH
>> config SND_SOC_INTEL_BYT_MAX98090_MACH
>> tristate "ASoC Audio driver for Intel Baytrail with MAX98090
>> codec"
>> depends on X86_INTEL_LPSS && I2C
>> - depends on DW_DMAC_CORE
>> - select SND_SOC_INTEL_SST
>> select SND_SOC_INTEL_BAYTRAIL
>> select SND_SOC_MAX98090
>> help
>> @@ -76,10 +74,7 @@ config SND_SOC_INTEL_BYT_MAX98090_MACH
>>
>> config SND_SOC_INTEL_BROADWELL_MACH
>> tristate "ASoC Audio DSP support for Intel Broadwell
>> Wildcatpoint"
>> - depends on X86_INTEL_LPSS && I2C && DW_DMAC && \
>> - I2C_DESIGNWARE_PLATFORM
>> - depends on DW_DMAC_CORE
>> - select SND_SOC_INTEL_SST
>> + depends on X86_INTEL_LPSS && I2C && I2C_DESIGNWARE_PLATFORM
>> select SND_SOC_INTEL_HASWELL
>> select SND_SOC_RT286
>> help
>
prev parent reply other threads:[~2016-03-18 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 11:44 [PATCH 1/1] sst: select DW_DMAC_CORE since it's mandatory Andy Shevchenko
2016-03-18 12:24 ` Andy Shevchenko
2016-03-18 16:15 ` Pierre-Louis Bossart [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=56EC29A8.3030400@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=vinod.koul@intel.com \
--cc=yang.jie@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;
as well as URLs for NNTP newsgroup(s).