From: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
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: [RFC] [PATCH 1/3] ASoC: Add support for Conexant CX20442-11 voice modem codec
Date: Wed, 22 Jul 2009 16:01:43 +0200 [thread overview]
Message-ID: <4A671BC7.20300@tis.icnet.pl> (raw)
In-Reply-To: <20090722101027.GA7622@sirena.org.uk>
Hi Mark,
Mark Brown wrote:
> On Wed, Jul 22, 2009 at 05:22:28AM +0200, Janusz Krzysztofik wrote:
>> This patch adds support for Conexant CX20442-11 voice modem codec, suitable
>> for use by the ASoC board driver for Amstrad E3 (Delta) videophone. Related
>> sound card driver will follow.
>> ...
> This patch is basically fine from an ASoC point of view so I've applied
> it.
Thanks!
> You'll want to run checkpatch over it and send a followup fixing the
Sorry for not doing this before submitting. Will send the followup soon.
> issues it identifies. Looking at this I suspect that it may be possible
> to refactor things so that more of the line discipline interaction is
> pushed down into the CODEC driver but that can also be done as a
> followup.
I have put the line discipline code into the machine driver for two reasons:
1. For me, the actual code is much more machine than codec specific.
2. It was much easier to update the codec structure instance with
machine's provided hw_write() rather than fiddle with adding a new
member to the structure definition for passing a machine callback to the
line discipline functions.
If you think we can find any use cases for drivers supporting
codec/modem combination other than CX20442 on Amstrad Delta, I can agree
with you on moving the line discipline code out of the machine driver,
but instead of pushing it down to the codec I would rather se it as a
separate module. Anyway, I think that some kind of support on the ASoC
top level for this case could be helpfull.
> would also be nice to add some documentation somewhere explaining how
> the hw_write() function is expected to be set up since it's a little
> surprising (if the line discipline stuff were pushed down into the code
> that'd become a lot more obvious).
I'll add a few words to the followup.
Thanks,
Janusz
next prev parent reply other threads:[~2009-07-22 14:01 UTC|newest]
Thread overview: 9+ 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 10:10 ` Mark Brown
2009-07-22 14:01 ` Janusz Krzysztofik [this message]
2009-07-28 14:59 ` [alsa-devel] " Janusz Krzysztofik
2009-07-28 15:07 ` Mark Brown
2009-07-28 16:07 ` Janusz Krzysztofik
2009-07-28 16:11 ` [alsa-devel] " Mark Brown
2009-07-28 16:36 ` Janusz Krzysztofik
2009-07-28 16:39 ` 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=4A671BC7.20300@tis.icnet.pl \
--to=jkrzyszt@tis.icnet.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=arunks@mistralsolutions.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=e3-hacking@earth.li \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox