alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Austin, Brian" <Brian.Austin@cirrus.com>
Cc: "<alsa-devel@alsa-project.org>" <alsa-devel@alsa-project.org>,
	"<vinod.koul@linux.intel.com>" <vinod.koul@linux.intel.com>,
	"<joe@nucleusys.com>" <joe@nucleusys.com>,
	"<ramesh.babu@intel.com>" <ramesh.babu@intel.com>,
	"<lrg@ti.com>" <lrg@ti.com>
Subject: Re: [PATCH v3] ASoC: Add support for cs42l73 codec
Date: Fri, 7 Oct 2011 11:34:00 +0100	[thread overview]
Message-ID: <20111007103359.GG19080@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <10520301-F8F9-4096-91F8-141F22CEA68C@cirrus.com>

On Thu, Oct 06, 2011 at 07:15:22PM +0000, Austin, Brian wrote:
> On Oct 6, 2011, at 1:57 PM, Mark Brown wrote:
> > On Thu, Oct 06, 2011 at 11:19:05AM -0500, Brian Austin wrote:

> >> +	{"DAC1 Mixer", "Headphone Switch", "XSPIN"},

> >> +	{"DAC1 Mixer", "Headphone Switch", "ASPIN"},

> >> +	{"DAC1 Mixer", "Headphone Switch", "VSPIN"},

> > This all looks totally wrong and I'm surprised the driver loads without
> > errors.  There's two issues:

> > - All the controls here are for the input to the DAC mixers but their
> >   names are for physical outputs.  I'd expect the switches to name
> >   inputs (for example, "DAC1 Mixer VSPIN Switch").  What's actually
> >   going on here?

> > - You've got three copies of each of the controls for each mixer - I'm
> >   surprsied this loads without the core complaining that it can't
> >   create controls with duplicate names.

> This works fine on my setup with a beagleboard. 

I'm frankly astonished.  What are these controls called?

> There are 3 routes for the HP/LO/SPK/SPKLO/EAR. What I am trying to accomplish is the following.
> Allow a stream from any serial port to go to any output.

That's perfectly reasonable but what you've written doesn't seem to do
that.  The DAPM routes are in the form:

    { destination, control, source }

so what the above example says is that audio is routed from XSPIN to
DAC1 if the DAC1 Headphone switch is turned on.

  reply	other threads:[~2011-10-07 10:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-06 16:19 [PATCH v3] ASoC: Add support for cs42l73 codec Brian Austin
2011-10-06 18:57 ` Mark Brown
2011-10-06 19:15   ` Austin, Brian
2011-10-07 10:34     ` Mark Brown [this message]
2011-10-07 11:07       ` Vinod Koul
2011-10-07 11:42         ` Mark Brown
2011-10-07 14:05           ` Austin, Brian
2011-10-07 14:27             ` Mark Brown
2011-10-07 14:29             ` Vinod Koul
2011-10-12 15:58               ` Austin, Brian
2011-10-12 21:37               ` Austin, Brian
2011-10-12 21:50                 ` Austin, Brian
2011-10-12 21:55                   ` Austin, Brian
2011-10-17 19:11               ` Austin, Brian
2011-10-17 20:15                 ` Mark Brown
2011-10-07  3:59   ` Vinod Koul
2011-10-07  2:13 ` Tabi Timur-B04825
2011-10-07 10:27   ` 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=20111007103359.GG19080@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=Brian.Austin@cirrus.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=joe@nucleusys.com \
    --cc=lrg@ti.com \
    --cc=ramesh.babu@intel.com \
    --cc=vinod.koul@linux.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;
as well as URLs for NNTP newsgroup(s).