From: Liam Girdwood <lrg@slimlogic.co.uk>
To: abraham duenas <aduejazz@gmail.com>
Cc: alsa-devel@alsa-project.org, broonie@opensource.wolfsonmicro.com
Subject: Re: ALSA UCM
Date: Thu, 04 Nov 2010 10:09:09 +0000 [thread overview]
Message-ID: <1288865349.3277.14.camel@odin> (raw)
In-Reply-To: <AANLkTimFdKg=_KDv8fbSJry6XTEsZqyQz7GhzaPxXDYP@mail.gmail.com>
On Wed, 2010-11-03 at 14:38 -0600, abraham duenas wrote:
> Hello,
>
> I recently cloned:
> git clone git://git.alsa-project.org/alsa-lib.git alsa-lib
> git clone git://git.alsa-project.org/alsa-utils.git alsa-utils
> and switched to the "ucm" branch to give it try. I have a panda board
> (pandaboard.org it is just a TI OMAP4 platform).
>
Ok, this is the correct repository.
> I created some configuration files for my card. My conf file is
> 'SDP4430.conf' and my verb is on 'hifi'.
> I came with a simple program to set my verb and configure it for a
> simple device. I'm calling this sequence:
> 1. open it.... snd_use_case_mgr_open(&uc_mgr,"SDP4430")
> 2. reset it ....snd_use_case_mgr_reset(uc_mgr)
> 3. query for my verb.... snd_use_case_get_list(uc_mgr,"_verbs",&mylist)
> 4. set my verb ... snd_use_case_set(uc_mgr,"_verb",*mylist)
> 5. set my created device... snd_use_case_set(uc_mgr,"_enadev","Headset.0")
> 6. close it... snd_use_case_mgr_close(uc_mgr)
>
> Seems to work ok (without any errors) but I can't see any of my amixer
> controls set/changed accordingly to my verb/device.
> Is this a right sequence to follow? may be my files are not well written?
>
This sequence looks correct. Can you share with us the relevant parts of
your configuration files.
Jaroslav did make some changes to the config file format so maybe we
have a formatting problem here.
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-11-04 10:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 20:38 ALSA UCM abraham duenas
2010-11-04 10:09 ` Liam Girdwood [this message]
2010-11-04 12:57 ` abraham duenas
2010-11-04 17:09 ` Liam Girdwood
2010-11-04 18:31 ` Jaroslav Kysela
2010-11-04 18:34 ` Jaroslav Kysela
2010-11-04 18:47 ` Liam Girdwood
2010-11-04 18:52 ` Jaroslav Kysela
2010-11-04 19:07 ` Liam Girdwood
2010-11-05 21:23 ` abraham duenas
2010-11-06 12:26 ` Liam Girdwood
2010-11-09 16:54 ` abraham duenas
2010-11-10 15:11 ` Jaroslav Kysela
2010-11-12 15:41 ` Liam Girdwood
2010-11-12 16:25 ` Jaroslav Kysela
2010-11-12 16:42 ` Liam Girdwood
2010-11-12 16:55 ` Jaroslav Kysela
2010-11-12 17:28 ` Mark Brown
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=1288865349.3277.14.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=aduejazz@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.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;
as well as URLs for NNTP newsgroup(s).