From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
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 06:01:28 +0000 [thread overview]
Message-ID: <1458021688.8522.16.camel@loki> (raw)
In-Reply-To: <20160314160654.GA2566@sirena.org.uk>
On Mon, 2016-03-14 at 16:06 +0000, Mark Brown wrote:
> On Mon, Mar 14, 2016 at 08:19:27AM +0000, Liam Girdwood wrote:
>
> > On Mon, 2016-03-14 at 08:17 +0000, Lu, Han wrote:
>
> > > a) shortname is current machine driver name i.e. "byt-rt5640"
> > > b) longname is DMI boardname + 1 i.e. "Minnowboard Max: byt-rt5640"
> > > c) driver name is platform driver name i.e. "baytrail-pcm-audio"
>
> I don't understand why we wouldn't use the machine driver name as the
> driver name.
I'm fine with that too. What about :-
1) Shortname is board/machine name. This can come from DMI or device
tree. e.g. "Asus T100"
2) Long name is 1 + driver name + optional firmware name. (I've just
added the FW name here too as we can have potentially > 1 FW per driver
- BYT is an example) e.g. "Asus T00: byt-rt5640: IntSST1.bin".
3) Driver name is driver_name. e.g. "byt-rt5640"
(The string name combinations above are not from a real machine but just
for example.)
Liam
_______________________________________________
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 6:01 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 [this message]
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
2016-03-15 10:48 ` [alsa-devel] " 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=1458021688.8522.16.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=han.lu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.