[alsa-devel] [PATCH v5] ASoC:Add support for cs42l73 codec

Austin, Brian Brian.Austin at cirrus.com
Thu Oct 20 23:34:24 CEST 2011

On Oct 20, 2011, at 4:28 PM, "Mark Brown" <broonie at opensource.wolfsonmicro.com> wrote:

> On Thu, Oct 20, 2011 at 08:26:11PM +0000, Austin, Brian wrote:
> Fix your mailer to word wrap within paragraphs, I've reflowed for
> legibility.
>> We have only 2 power domains.  The input PCM and the output AMP.
>> The routing between these 2 points in the codec is handled by volume levels.
> Like I say this is pretty unremarkable - the volumes are your DAPM
> routing controls.
>> Given that, why would there be a need to show all routes through the
>> mixer in a DAPM context? How do you show that?  would it look
>> something like this?
> Well, the most obvious issue is that even if your device doesn't have
> any useful internal power management there may be external devices
> connected to the outputs (eg, a high power speaker amp) which do and so
> we need to know which outputs are actually active in order to control
> the outputs.

That makes sense, thanks
>> {"HPOUT",  NULL, "HP Amp"}
>> {"HP Amp", "Amp Switch",  "DAC1"}
>> {"DAC1",  "HP-XSP Volume Control",  "XSPIN"}
> This looks wrong, the control on the DAC looks like it actually controls
> just the one input path.

That is just one example, it would be
for all inputs as the mixer controls are.
>> You can represent the "HP-XSP Volume Control" control as DAPM? 
> Yes.
> ______
Let me rework the routes to show all inputs.

Sorry this has been such a hassle.

> _________________________________________
> Alsa-devel mailing list
> Alsa-devel at alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

More information about the Alsa-devel mailing list