Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: Vinod Koul <vinod.koul@intel.com>,
	liam.r.girdwood@linux.intel.com, alsa-devel@alsa-project.org,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	patches.audio@intel.com
Subject: Re: [PATCH 1/3] ALSA: hda: add hdac_adsp_enable module flag
Date: Thu, 30 Apr 2015 22:44:21 +0200	[thread overview]
Message-ID: <s5hmw1pjqhm.wl-tiwai@suse.de> (raw)
In-Reply-To: <20150430192726.GD22845@sirena.org.uk>

At Thu, 30 Apr 2015 20:27:26 +0100,
Mark Brown wrote:
> 
> On Thu, Apr 30, 2015 at 11:02:19AM -0500, Pierre-Louis Bossart wrote:
> > On 4/30/15 9:52 AM, Vinod Koul wrote:
> 
> > >Some Intel HDA controllers sport a DSP. These systems can also be enabled
> > >with ASoC HDA driver as well. So add a flag in hda-core to enable/disable
> > >aDSP This flag for now is false, and should be true once the ASoC based
> > >systems mature.  The integrators/OS vendors can configure this flag based on
> > >system preference.
> 
> > This choice is contingent on the BIOS options, you can't enable the DSP if
> > the BIOS said no DSP...
> 
> Presumably this flag should be coming from the BIOS by default and this
> providing a disable only setting for test/development?

It's hard to know exactly how many models will be with DSP and how
many without...  The problem we're dealing with is that we'll have two
individual drivers supporting the very same PCI ID.  And, there is no
good mechanism to prioritize the driver load on Linux, so far.

So, this is the consequence after lengthy discussions: it's fairly
simple but effective enough.  Distros may build both drivers, but
which driver to use can be decided by this option.  The default value
of this switch should be set via a Kconfig, but it can be overridden
dynamically via either a static module option or boot option.


Takashi

  reply	other threads:[~2015-04-30 20:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30 14:52 [PATCH 1/3] ALSA: hda: add hdac_adsp_enable module flag Vinod Koul
2015-04-30 14:52 ` [PATCH 2/3] ALSA: hda: remove module_pci_driver Vinod Koul
2015-04-30 14:52 ` [PATCH 3/3] ALSA: hda: register selectively for SPT-LP Vinod Koul
2015-04-30 20:33   ` Mark Brown
2015-04-30 20:59     ` Takashi Iwai
2015-04-30 21:23       ` Mark Brown
2015-05-01  4:31         ` Vinod Koul
2015-04-30 16:02 ` [PATCH 1/3] ALSA: hda: add hdac_adsp_enable module flag Pierre-Louis Bossart
2015-04-30 19:27   ` Mark Brown
2015-04-30 20:44     ` Takashi Iwai [this message]
2015-05-01  4:39       ` Vinod Koul
2015-05-01 14:15         ` Pierre-Louis Bossart
2015-05-01 14:41           ` Mark Brown
2015-05-01 11:13       ` Mark Brown
2015-04-30 20:47 ` Takashi Iwai

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=s5hmw1pjqhm.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=patches.audio@intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --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