[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200907281836.03049.jkrzyszt@tis.icnet.pl>
Date: Tue, 28 Jul 2009 18:36:01 +0200
From: Janusz Krzysztofik <jkrzyszt@....icnet.pl>
To: Mark Brown <broonie@...nsource.wolfsonmicro.com>
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
Tuesday 28 July 2009 18:11:32 Mark Brown wrote:
> On Tue, Jul 28, 2009 at 06:07:29PM +0200, Janusz Krzysztofik wrote:
> > now. Activation of the line discipline would deregister the codec device
> > from the platform bus and reregister it again, now as the line discipline
> > provided device. Is this possible with current ASoC framework?
>
> No, not currently. But why would you do that, anyway?
>
> 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?
Janusz
--
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/
Powered by blists - more mailing lists