From: "Gabriel M. Beddingfield" <gabrbedd@gmail.com>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [RFC] ASoC: Current state of Dynamic PCM API
Date: Mon, 22 Apr 2013 07:57:35 -0700 [thread overview]
Message-ID: <51754FDF.5050401@gmail.com> (raw)
In-Reply-To: <CABJ1b_QQS7amB3jTMvKGsJAC-QuPj4DmPNg-1waAqgC-Y8Ry7A@mail.gmail.com>
On 04/18/2013 05:07 AM, Sebastian Hesselbarth wrote:
> Can any of you point me to patches, repositories, or documentation
> about DPCM where I can start with?
One that I know of is here:
http://git.omapzoom.org/?p=kernel/omap.git;a=summary
branch: p-android-omap-3.4, p-linux-omap-3.4
machine driver: sound/soc/omap/omap-abe-twl6040.c (OMAP4, OMAP5)
There's also stuff on the 3.0 and 3.1 branches... but 3.4 more closely
resembles the current API.
-gabriel
prev parent reply other threads:[~2013-04-22 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 12:07 [RFC] ASoC: Current state of Dynamic PCM API Sebastian Hesselbarth
2013-04-22 14:57 ` Gabriel M. Beddingfield [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=51754FDF.5050401@gmail.com \
--to=gabrbedd@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@slimlogic.co.uk \
--cc=peter.ujfalusi@ti.com \
--cc=sebastian.hesselbarth@gmail.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