From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
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: Fri, 1 May 2015 12:13:42 +0100 [thread overview]
Message-ID: <20150501111342.GW22845@sirena.org.uk> (raw)
In-Reply-To: <s5hmw1pjqhm.wl-tiwai@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 1522 bytes --]
On Thu, Apr 30, 2015 at 10:44:21PM +0200, Takashi Iwai wrote:
> Mark Brown wrote:
> > On Thu, Apr 30, 2015 at 11:02:19AM -0500, Pierre-Louis Bossart wrote:
j
> > > 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.
Well, I'm a bit confused why we're loading separate drivers at all here.
Shouldn't we be loading one driver and then figuring out what to do with
the hardware based on something like DMI matching (you'd hope that there
would be some config readback from the firmware but recent performance
suggests not)?
> 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.
I don't understand how it's going to work well for users, especially
distros where you're building something to be installed on a wide range
of hardware, and it doesn't seem idiomatic.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-05-01 11:13 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
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 [this message]
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=20150501111342.GW22845@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=patches.audio@intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.de \
--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