From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <liam.r.girdwood@linux.intel.com>
Cc: Takashi Iwai <tiwai@suse.de>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Linux Upstreaming Team <linux@endlessm.com>,
General PulseAudio Discussion
<pulseaudio-discuss@lists.freedesktop.org>,
"han.lu" <han.lu@linux.intel.com>
Subject: Re: ASoC and pulseaudio
Date: Tue, 15 Mar 2016 10:00:33 +0000 [thread overview]
Message-ID: <20160315100033.GL2566@sirena.org.uk> (raw)
In-Reply-To: <1458035331.8522.52.camel@loki>
[-- Attachment #1.1: Type: text/plain, Size: 1411 bytes --]
On Tue, Mar 15, 2016 at 09:48:51AM +0000, Liam Girdwood wrote:
> On Tue, 2016-03-15 at 09:55 +0100, Takashi Iwai wrote:
> > > Shouldn't we use whatever we use to figure out which firmware to load
> > > rather than the firmware name? Someone might do something like try to
> > > replace one firmware with another and get everything confused.
> This is not to load FW for our use case, the FW name is hard coded in
It's not for loading, it's because the firmware name we requested may
not be the firmware that actually got loaded.
> driver tables. We do have several FWs for the BYT driver that all have
> different capabilities. Userspace could set the correct config for each
> FW if it knew the FW that was being used.
Is the firmware configuration sufficiently reusable between boards or
could that just be figured out in userspace?
> > The short name is something between them. The alsa-lib USB-audio
> > config file refers to the short name because the driver doesn't
> > provide a unique id for driver_name for various workarounds. But it
> > should be considered as an exception. Ideally, driver_name should be
> > unique enough for each different configuration.
> So IIUC this would mean ?
> 1) short name is optional, but could be board name.
I'd not make it optional, the long names tend to be on the verbose side
so applications do seem to use the short name for user rendering
purposes.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 187 bytes --]
_______________________________________________
pulseaudio-discuss mailing list
pulseaudio-discuss@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
next prev parent reply other threads:[~2016-03-15 10:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAL9uMOHRjcCJomr6zzR0ySh384AVj1FRvASZSp3KsPqfeS8Lzw@mail.gmail.com>
[not found] ` <56C8AEFD.4060808@linux.intel.com>
[not found] ` <1456225994.6424.35.camel@loki>
[not found] ` <B51200AC81AB024499A3C2C9A1BB90A83D3AABF9@SHSMSX101.ccr.corp.intel.com>
2016-03-14 8:19 ` ASoC and pulseaudio Liam Girdwood
2016-03-14 15:23 ` [alsa-devel] " Pierre-Louis Bossart
2016-03-14 16:06 ` Mark Brown
2016-03-15 6:01 ` Liam Girdwood
2016-03-15 8:45 ` Mark Brown
2016-03-15 8:55 ` Takashi Iwai
2016-03-15 9:48 ` Liam Girdwood
2016-03-15 9:56 ` Takashi Iwai
2016-03-15 10:58 ` Liam Girdwood
2016-03-16 14:57 ` [pulseaudio-discuss] " Vinod Koul
2016-03-16 15:09 ` [alsa-devel] " Mark Brown
2016-03-16 15:17 ` Takashi Iwai
2016-03-16 15:53 ` [pulseaudio-discuss] " Vinod Koul
2016-03-16 17:59 ` [alsa-devel] " Liam Girdwood
2016-03-17 11:23 ` [pulseaudio-discuss] " Lu, Han
2016-03-17 11:28 ` [alsa-devel] " Lu, Han
2016-03-17 16:29 ` Vinod Koul
2016-03-16 17:58 ` Liam Girdwood
2016-03-16 17:57 ` Liam Girdwood
2016-03-15 10:00 ` Mark Brown [this message]
2016-03-15 10:48 ` Liam Girdwood
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=20160315100033.GL2566@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=han.lu@linux.intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux@endlessm.com \
--cc=pulseaudio-discuss@lists.freedesktop.org \
--cc=tiwai@suse.de \
/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).