From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Mark Brown <broonie@kernel.org>, Liam Girdwood <lgirdwood@gmail.com>
Cc: shuge@allwinnertech.com, alsa-devel@alsa-project.org,
zhuzhenhua@allwinnertech.com, kevin.z.m.zh@gmail.com,
sunny@allwinnertech.com
Subject: integration into ASoC
Date: Fri, 7 Mar 2014 17:53:35 +0100 [thread overview]
Message-ID: <20140307165335.GT607@lukather> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 958 bytes --]
Hi Liam, Mark,
I have a sound IP that is part of an SoC that I'm willing to write a
driver for.
This IP is made of a few registers to control the sampling rate, if
we're using mono/stereo, plus two fifos, one for playback, one for
capture, that can be seed with data. The data are then taken, go
through a DAC, and the outer interface of the IP are directly analog
signals (so the DAC/ADC are directly in the SoC, and the only
interface we have is plain registers).
From what I understood from ASoC, you have mostly three components,
the DAI, the codec and the platform that plumbers the two first
together. Here, my understanding is that it's pretty much the whole
three in a single IP.
Should such a hardware block be handled into ASoC, and if yes, how?
If not, which other framework should be used?
Thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next reply other threads:[~2014-03-07 16:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 16:53 Maxime Ripard [this message]
2014-03-07 17:12 ` integration into ASoC Lars-Peter Clausen
2014-03-09 7:48 ` Mark Brown
2014-03-10 10:11 ` Maxime Ripard
2014-03-10 9:50 ` Maxime Ripard
2014-03-10 10:15 ` Lars-Peter Clausen
2014-03-10 16:43 ` Maxime Ripard
2014-03-10 17:23 ` Lars-Peter Clausen
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=20140307165335.GT607@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kevin.z.m.zh@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=shuge@allwinnertech.com \
--cc=sunny@allwinnertech.com \
--cc=zhuzhenhua@allwinnertech.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