From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: mengdong.lin@linux.intel.com
Cc: alsa-devel@alsa-project.org, tiwai@suse.de,
mengdong.lin@intel.com, vinod.koul@intel.com, broonie@kernel.org
Subject: Re: [RESEND RFC PATCH 0/3] ucm: Add support for component devices
Date: Tue, 15 Nov 2016 08:55:29 +0000 [thread overview]
Message-ID: <1479200129.7823.19.camel@loki> (raw)
In-Reply-To: <cover.1479195801.git.mengdong.lin@linux.intel.com>
On Tue, 2016-11-15 at 16:01 +0800, mengdong.lin@linux.intel.com wrote:
> From: Mengdong Lin <mengdong.lin@linux.intel.com>
>
> Sound cards are defined by machines. And off-soc codecs and DSPs embedded
> in DSP can be taken as the components and resued by different machines/
> sound cards. This series allows codec and SOC vendors to install UCM
> configuration files for a specific codec or DSP, and sound card verb
> files can just include these conf files of components, and trigger enable/
> disable sequence defined by the component devices.
>
> Component devices will not be exposed to applications for backward
> compatibility. So audio servers like PulseAudio and CRAS still only see
> the machine devices.
The intention here is that the sound server will load the UCM
configuration based on the sound card name in []. I have patches to
improve this for Intel based machines which tend to all use the platform
name....sending shortly.
Liam
prev parent reply other threads:[~2016-11-15 8:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 7:57 [RFC PATCH 0/3] Add support for component devices mengdong.lin
2016-11-15 8:02 ` [RFC PATCH 1/3] ucm: Skip component directories when scanning sound card configuration files mengdong.lin
2016-11-15 8:45 ` Liam Girdwood
2016-11-16 7:07 ` Lin, Mengdong
2016-11-15 8:02 ` [RFC PATCH 2/3] ucm: Parse sequence of component devices mengdong.lin
2016-11-15 8:45 ` Liam Girdwood
2016-11-16 7:16 ` Lin, Mengdong
2016-11-15 8:02 ` [RFC PATCH 3/3] ucm: Execute " mengdong.lin
2016-11-15 8:49 ` Liam Girdwood
2016-11-16 7:36 ` Lin, Mengdong
2016-11-15 8:55 ` Liam Girdwood [this message]
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=1479200129.7823.19.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=mengdong.lin@intel.com \
--cc=mengdong.lin@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