From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] add a mc13783 codec driver
Date: Mon, 12 Mar 2012 10:58:53 +0000 [thread overview]
Message-ID: <20120312105852.GE3110@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1496586.ebXd01ibP4@laptop>
On Mon, Mar 12, 2012 at 09:11:08AM +0100, Philippe R?tornaz wrote:
> Thank you for this detailed review. I will redo the patch based on your
> comments. I had a quick look at DAPM (dapm.txt in asoc documentation), but is
> there any good "reference" implementation which is in the kernel where I could
> have a look ?
Pretty much all ASoC drivers use DAPM and there's really not much
variation in quality in terms of how they do so, it's mostly an either
it works or doesn't thing. Just look for something maintained that you
can follow and/or which is fairly close to your hardware.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120312/d1ce2b81/attachment-0001.sig>
prev parent reply other threads:[~2012-03-12 10:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 14:55 [PATCH 0/4] mc13783 sound support Philippe Rétornaz
2012-03-09 14:55 ` [PATCH 1/4] add a mc13783 codec driver Philippe Rétornaz
2012-03-09 14:55 ` [PATCH 2/4] Add imx3sound sound support Philippe Rétornaz
2012-03-09 14:55 ` [PATCH 3/4] mx31moboard: Add ssi configuration Philippe Rétornaz
2012-03-09 14:55 ` [PATCH 4/4] imx31pdk: Add sound support Philippe Rétornaz
2012-03-11 11:41 ` [PATCH 3/4] mx31moboard: Add ssi configuration Mark Brown
2012-03-11 14:13 ` Fabio Estevam
2012-03-11 11:40 ` [PATCH 2/4] Add imx3sound sound support Mark Brown
2012-03-11 14:59 ` Fabio Estevam
2012-03-12 8:11 ` Philippe Rétornaz
2012-03-11 11:38 ` [PATCH 1/4] add a mc13783 codec driver Mark Brown
2012-03-12 8:11 ` Philippe Rétornaz
2012-03-12 10:58 ` Mark Brown [this message]
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=20120312105852.GE3110@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).