All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@ti.com>
To: Ashish Chavan <ashish.chavan@kpitcummins.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	alsa-devel <alsa-devel@alsa-project.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	arun.raghavan@collabora.co.ukMark Brown
	<broonie@opensource.wolfsonmicro.com>
Subject: Re: [alsa-devel] Query about alsa ucm (use case manager) config files
Date: Wed, 31 Oct 2012 14:26:49 +0000	[thread overview]
Message-ID: <50913529.2030906@ti.com> (raw)
In-Reply-To: <1351688372.28030.18.camel@matrix>

On 31/10/12 12:59, Ashish Chavan wrote:
> Hi,
>    I am just curious to know if there is any centralized repository for
> alsa use case manager configuration files. I tried searching and could
> only find alsa-ucm-conf.git repo at alsa project git server, which is
> actually an empty repo!
> 

This is the correct place, but I've been busy with other stuff to push our configs upstream to date (will do so today now). The eventual contents of this repo are intended to be copied into :-

/usr/share/alsa/ucm (or where ever alsa is installed on your distro)

However, I've not had a chance to push the UCM Nexus and Pandaboard files from Arun to this repo yet due to some other ongoing work.

FYI, Arun's current UCM configs are here :-

http://cgit.collabora.com/git/android/platform/external/collabora/pulseaudio-android.git/log/data/alsa/ucm/Tuna/VoiceCall

> How people share/reuse ucm configuration files for a specific codec?
> In near future, I will be developing few ucm configuration files for
> some codecs and wish to share them with rest of the world. I think even
> though ucm configs are board/machine specific, it makes sense to share
> them. Is there any other, more visible place to put these config files
> than board specific distributions?
> 

Interesting idea to create separate shareable codec UCM configuration. We currently have no way to "include" a shareable codec specific configuration into a machine specific configuration but it would probably not be too hard to add to the parser.

Regards

Liam

WARNING: multiple messages have this Message-ID (diff)
From: Liam Girdwood <lrg@ti.com>
To: Ashish Chavan <ashish.chavan@kpitcummins.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	alsa-devel <alsa-devel@alsa-project.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	<arun.raghavan@collabora.co.uk>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [alsa-devel] Query about alsa ucm (use case manager) config files
Date: Wed, 31 Oct 2012 14:26:49 +0000	[thread overview]
Message-ID: <50913529.2030906@ti.com> (raw)
In-Reply-To: <1351688372.28030.18.camel@matrix>

On 31/10/12 12:59, Ashish Chavan wrote:
> Hi,
>    I am just curious to know if there is any centralized repository for
> alsa use case manager configuration files. I tried searching and could
> only find alsa-ucm-conf.git repo at alsa project git server, which is
> actually an empty repo!
> 

This is the correct place, but I've been busy with other stuff to push our configs upstream to date (will do so today now). The eventual contents of this repo are intended to be copied into :-

/usr/share/alsa/ucm (or where ever alsa is installed on your distro)

However, I've not had a chance to push the UCM Nexus and Pandaboard files from Arun to this repo yet due to some other ongoing work.

FYI, Arun's current UCM configs are here :-

http://cgit.collabora.com/git/android/platform/external/collabora/pulseaudio-android.git/log/data/alsa/ucm/Tuna/VoiceCall

> How people share/reuse ucm configuration files for a specific codec?
> In near future, I will be developing few ucm configuration files for
> some codecs and wish to share them with rest of the world. I think even
> though ucm configs are board/machine specific, it makes sense to share
> them. Is there any other, more visible place to put these config files
> than board specific distributions?
> 

Interesting idea to create separate shareable codec UCM configuration. We currently have no way to "include" a shareable codec specific configuration into a machine specific configuration but it would probably not be too hard to add to the parser.

Regards

Liam




  reply	other threads:[~2012-10-31 14:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-31 12:59 Query about alsa ucm (use case manager) config files Ashish Chavan
2012-10-31 12:59 ` [alsa-devel] " Ashish Chavan
2012-10-31 14:26 ` Liam Girdwood [this message]
2012-10-31 14:26   ` 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=50913529.2030906@ti.com \
    --to=lrg@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=arun.raghavan@collabora.co.ukMark \
    --cc=ashish.chavan@kpitcummins.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.