linux-kernel - Re: [alsa-devel] [PATCH 1/4] ASoC: DAPM: Allow multiple mixer sources to be routed via the same switch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4E43A808.4050105@metafoo.de>
Date:	Thu, 11 Aug 2011 11:59:36 +0200
From:	Lars-Peter Clausen <lars@...afoo.de>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC:	Mike Frysinger <vapier.adi@...il.com>, alsa-devel@...a-project.org,
	Liam Girdwood <lrg@...com>,
	device-drivers-devel@...ckfin.uclinux.org,
	linux-kernel@...r.kernel.org
Subject: Re: [alsa-devel] [PATCH 1/4] ASoC: DAPM: Allow multiple mixer sources
 to be routed via the same switch

On 08/11/2011 11:31 AM, Mark Brown wrote:
> On Wed, Aug 10, 2011 at 05:52:41AM +0200, Lars-Peter Clausen wrote:
>> Currently it is only possible to route one source per switch into a mixer.
>> This patch modifies the code, so that it is possible to route multiple sources
>> into a mixer via the same switch. One use-case for this is routing a stereo
>> channel pair into a mono-mixer via the same switch.
>
> I'd have thought the dapm_is_shared_control() stuff should handle this?


The dapm_is_shared_control() stuff is about sharing kcontrols between multiple
muxes. This is about sharing the same kcontrol between multiple paths of the
same mixer.

i.e

{ "Mono Mixer", "DAC", "Left DAC" },
{ "Mono Mixer", "DAC", "Right DAC" },

doesn't work without this patch.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/