From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: alsa-devel@alsa-project.org
Cc: "ext Aggarwal, Anuj" <anuj.aggarwal@ti.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: Default enabling of mixer controls
Date: Tue, 9 Jun 2009 09:57:39 +0300 [thread overview]
Message-ID: <200906090957.39758.peter.ujfalusi@nokia.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB030591A9D1@dbde02.ent.ti.com>
On Tuesday 09 June 2009 06:45:24 ext Aggarwal, Anuj wrote:
> > Hrm, you'll be missing some internal DAPM state updates. Currently the
> > most direct way to do that would be to go through the actual control
> > interface and there's not a particularly nice way of doing that that
> > from the kernel that I'm aware of.
Should the snd_soc_dapm_sync(codec); need to be called after the register
updates?
> >
> > Is this not something you can have user space do?
>
> [Aggarwal, Anuj] Since this was by default enabled in my earlier codec
> driver, I wanted to make the change transparent to the end user. However,
> since the same can be done from user space too, it should not be a problem
> for my customer.
I think this should be done by the user space as well. I have had plans to
disable all paths by default on the twl4030 codec, and let the user space to
configure for the given board. At least that is what we are doing in our
custom board.
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
--
Péter
next prev parent reply other threads:[~2009-06-09 6:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 12:10 Default enabling of mixer controls Aggarwal, Anuj
2009-06-08 12:14 ` Mark Brown
2009-06-08 14:24 ` Aggarwal, Anuj
2009-06-08 14:39 ` Mark Brown
2009-06-09 3:45 ` Aggarwal, Anuj
2009-06-09 6:57 ` Peter Ujfalusi [this message]
2009-06-09 8:54 ` 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=200906090957.39758.peter.ujfalusi@nokia.com \
--to=peter.ujfalusi@nokia.com \
--cc=alsa-devel@alsa-project.org \
--cc=anuj.aggarwal@ti.com \
--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 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.