linux-kernel - Re: [alsa-devel] [RFC] [PATCH 1/3] ASoC: Add support for Conexant CX20442-11 voice modem codec

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] [day] [month] [year] [list]

Message-ID: <20090728163902.GA26657@rakim.wolfsonmicro.main>
Date:	Tue, 28 Jul 2009 17:39:02 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Janusz Krzysztofik <jkrzyszt@....icnet.pl>
Cc:	alsa-devel@...a-project.org, Jonathan McDowell <noodles@...th.li>,
	Tony Lindgren <tony@...mide.com>,
	Peter Ujfalusi <peter.ujfalusi@...ia.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	e3-hacking@...th.li, Arun KS <arunks@...tralsolutions.com>,
	"linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>,
	"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [alsa-devel] [RFC] [PATCH 1/3] ASoC: Add support for Conexant
 CX20442-11 voice modem codec

On Tue, Jul 28, 2009 at 06:36:01PM +0200, Janusz Krzysztofik wrote:
> Tuesday 28 July 2009 18:11:32 Mark Brown wrote:

> > Like I say, I'd suggest always keeping the controls registered and just
> > masking and unmasking from user space - the control indexes get used so
> > removing them will just confuse things.

> However, in order for the machine driver to unmask/mask a machine specific 
> control, the codec driver must drop the machine driver a message about the 
> line discipline being activeted/deactivated, right? The only such existing 
> feedback I can see the codec is able to use is via snd_soc_init_card() that 
> calls snd_soc_dai_link.init() in turn. Am I missing something?

Well, the machine driver can look up controls by name (this is going to
be required in order to find the controls anyway...).  Besides, given
that the machine driver is already entirely CODEC-specific there'd no
problem with it calling into CODEC-specific APIs to do things.
--
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/