From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
Cc: alsa-devel@alsa-project.org, Jonathan McDowell <noodles@earth.li>,
Tony Lindgren <tony@atomide.com>,
Peter Ujfalusi <peter.ujfalusi@nokia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
e3-hacking@earth.li, Arun KS <arunks@mistralsolutions.com>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [alsa-devel] [RFC] [PATCH 1/3] ASoC: Add support for Conexant CX20442-11 voice modem codec
Date: Tue, 28 Jul 2009 17:11:32 +0100 [thread overview]
Message-ID: <20090728161131.GA22349@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <200907281807.31070.jkrzyszt@tis.icnet.pl>
On Tue, Jul 28, 2009 at 06:07:29PM +0200, Janusz Krzysztofik wrote:
> What I would like to retain from the current codec driver are those two modes
> of operation: without and with the line discipline activated. Initially, the
> codec would be registered as a platform device, as it is 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.
next prev parent reply other threads:[~2009-07-28 16:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 3:22 [RFC] [PATCH 1/3] ASoC: Add support for Conexant CX20442-11 voice modem codec Janusz Krzysztofik
2009-07-22 3:22 ` Janusz Krzysztofik
2009-07-22 10:10 ` Mark Brown
2009-07-22 10:10 ` [alsa-devel] " Mark Brown
2009-07-22 14:01 ` Janusz Krzysztofik
2009-07-22 14:01 ` [alsa-devel] " Janusz Krzysztofik
2009-07-28 14:59 ` Janusz Krzysztofik
2009-07-28 15:07 ` Mark Brown
2009-07-28 15:07 ` [alsa-devel] " Mark Brown
2009-07-28 16:07 ` Janusz Krzysztofik
2009-07-28 16:07 ` [alsa-devel] " Janusz Krzysztofik
2009-07-28 16:11 ` Mark Brown [this message]
2009-07-28 16:36 ` Janusz Krzysztofik
2009-07-28 16:36 ` [alsa-devel] " Janusz Krzysztofik
2009-07-28 16:39 ` Mark Brown
2009-07-28 16:39 ` [alsa-devel] " 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=20090728161131.GA22349@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=arunks@mistralsolutions.com \
--cc=e3-hacking@earth.li \
--cc=jkrzyszt@tis.icnet.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=noodles@earth.li \
--cc=peter.ujfalusi@nokia.com \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.