On Mon, Nov 05, 2018 at 10:19:02PM +0100, Arnd Bergmann wrote:
> On 11/5/18, Andy Shevchenko wrote:
> > On Mon, Nov 5, 2018 at 7:19 PM Pierre-Louis Bossart
> > wrote:
> >> >> config SND_SOC_HDAC_HDA_FORCE
> >> >> tristate
> >
> >> >> depends on SND_SOC_ALL_CODECS != n
> >
> >
On 11/5/18, Andy Shevchenko wrote:
> On Mon, Nov 5, 2018 at 7:19 PM Pierre-Louis Bossart
> wrote:
>>
>>
>> >>> We have this ("strange") lines over the drivers:
>> >>>
>> >>> config BAR
>> >>> depends on FOO || FOO=n
>> >>>
>> >>> which guarantees that FOO will be not module when BAR is built-in.
On Mon, Nov 5, 2018 at 7:19 PM Pierre-Louis Bossart
wrote:
>
>
> >>> We have this ("strange") lines over the drivers:
> >>>
> >>> config BAR
> >>> depends on FOO || FOO=n
> >>>
> >>> which guarantees that FOO will be not module when BAR is built-in.
> >> That's what I normally use, but I could not
We have this ("strange") lines over the drivers:
config BAR
depends on FOO || FOO=n
which guarantees that FOO will be not module when BAR is built-in.
That's what I normally use, but I could not figure this one out.
One problem is that SND_SOC_ALL_CODECS selects
SND_SOC_HDAC_HDA, and SND_SOC
On Mon, 05 Nov 2018 16:07:50 +0100,
Arnd Bergmann wrote:
>
> On 11/5/18, Andy Shevchenko wrote:
> > On Sun, Nov 04, 2018 at 10:45:17AM -0600, Pierre-Louis Bossart wrote:
> >
> >> So yes indeed we have to add a select HDAC_HDA statement under the
> >> SKYLAKE
> >> config - i just don't know of any
On 11/5/18, Andy Shevchenko wrote:
> On Sun, Nov 04, 2018 at 10:45:17AM -0600, Pierre-Louis Bossart wrote:
>
>> So yes indeed we have to add a select HDAC_HDA statement under the
>> SKYLAKE
>> config - i just don't know of any other means to say "don't build
>> HDAC_HDA
>> as a module when SKYLAKE
On Sun, Nov 04, 2018 at 10:45:17AM -0600, Pierre-Louis Bossart wrote:
> So yes indeed we have to add a select HDAC_HDA statement under the SKYLAKE
> config - i just don't know of any other means to say "don't build HDAC_HDA
> as a module when SKYLAKE is buit-in"
We have this ("strange") lines ove
On 11/2/18 5:03 PM, Arnd Bergmann wrote:
On 11/2/18, Pierre-Louis Bossart wrote:
On 11/2/18 6:24 AM, Arnd Bergmann wrote:
The skylake sound support is written to work both with or without
CONFIG_SND_SOC_HDAC_HDA, and uses an #ifdef to decide whether it should
link against that. However, this
On 11/2/18, Pierre-Louis Bossart wrote:
>
> On 11/2/18 6:24 AM, Arnd Bergmann wrote:
>> The skylake sound support is written to work both with or without
>> CONFIG_SND_SOC_HDAC_HDA, and uses an #ifdef to decide whether it should
>> link against that. However, this fails with SND_SOC_ALL_CODECS=m o
On 11/2/18 6:24 AM, Arnd Bergmann wrote:
The skylake sound support is written to work both with or without
CONFIG_SND_SOC_HDAC_HDA, and uses an #ifdef to decide whether it should
link against that. However, this fails with SND_SOC_ALL_CODECS=m or
SND_SOC_INTEL_SKL_HDA_DSP_GENERIC_MACH=m when th
The skylake sound support is written to work both with or without
CONFIG_SND_SOC_HDAC_HDA, and uses an #ifdef to decide whether it should
link against that. However, this fails with SND_SOC_ALL_CODECS=m or
SND_SOC_INTEL_SKL_HDA_DSP_GENERIC_MACH=m when the Skylake support itself
is built-in, with th
11 matches
Mail list logo
