[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090722101027.GA7622@sirena.org.uk>
Date: Wed, 22 Jul 2009 11:10:28 +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 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.
> Created and tested against linux-2.6.31-rc3.
> Applies and works with linux-omap-2.6 commit
> 7c5cb7862d32cb344be7831d466535d5255e35ac as well.
> Signed-off-by: Janusz Krzysztofik <jkrzyszt@....icnet.pl>
This patch is basically fine from an ASoC point of view so I've applied
it.
You'll want to run checkpatch over it and send a followup fixing the
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.
Since this (and all the other descriptive text that follows it):
> This codec is an optional part of the Conexant SmartV three chip modem design.
> As such, documentation for its proprietary digital audio interface is not
> available. However, on Amstrad Delta board, thanks to Mark Underwood who
...is useful documentation I've pulled it into the commit message. It
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).
--
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