Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stuart Longland <redhatter@gentoo.org>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
	Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: Binding multiple registers to an enum
Date: Mon, 13 Sep 2010 09:43:07 +0100	[thread overview]
Message-ID: <20100913084307.GC16606@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <20100912233151.GU14056@atomos.longlandclan.yi.org>

On Mon, Sep 13, 2010 at 09:31:51AM +1000, Stuart Longland wrote:

> I've tried lying to DAPM and telling it these bits control PGAs on the
> inputs themselves... but it gets the wrong idea about which ones need to
> be turned on.  Perhaps I should investigate that ... but the idea of
> using PGA controls doesn't seem quite right.

It would be helpful if you could be a bit more specific about what the
registers look like and what the problems you are encountering are.
Since what you're saying is so generic and non-specific it's hard to
really say anything concrete.  Possibly what you want to do is have an
event on the widgets for the mixers which does the appropriate setup?

> I've looked at SOC_ENUM_EXT, which would do what I want (I already use
> this to keep ADC OSR and DAC OSR settings in sync) however, these
> controls have implications for signal routing, and therefore DAPM needs
> to know about them, so really it'd be a SOC_DAPM_ENUM_EXT control I'd be
> after.  I can't see such a thing however... how does one go about doing
> this?

The easiest thing is to look at the git logs and see how similar things
were added then do the equivalent thing.  That'll show all the areas
that need updating.

      reply	other threads:[~2010-09-13  8:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-12 23:31 Binding multiple registers to an enum Stuart Longland
2010-09-13  8:43 ` Mark Brown [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=20100913084307.GC16606@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=redhatter@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox