From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>,
Liam Girdwood <lgirdwood@gmail.com>,
zhuzhenhua@allwinnertech.com, kevin.z.m.zh@gmail.com,
sunny@allwinnertech.com, shuge@allwinnertech.com
Subject: Re: integration into ASoC
Date: Mon, 10 Mar 2014 11:11:53 +0100 [thread overview]
Message-ID: <20140310101153.GD2815@lukather> (raw)
In-Reply-To: <20140309074853.GI28112@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1092 bytes --]
On Sun, Mar 09, 2014 at 07:48:53AM +0000, Mark Brown wrote:
> On Fri, Mar 07, 2014 at 06:12:33PM +0100, Lars-Peter Clausen wrote:
> > On 03/07/2014 05:53 PM, Maxime Ripard wrote:
>
> > >I have a sound IP that is part of an SoC that I'm willing to write a
> > >driver for.
>
> > Which SoC is this?
>
> I'm going to guess it's the Allwinner stuff.
Yep.
> > >Should such a hardware block be handled into ASoC, and if yes, how?
> > >If not, which other framework should be used?
>
> > It makes sense to use ASoC if there are components where the driver
> > can be shared e.g. the DMA in your case. Otherwise you can also use
> > plain old ALSA.
>
> Right, though one thing to consider here is if the device is typically
> used with external components - some of these systems provide a line
> output which is then connected to external speaker and headphone
> amplifiers which can be things that have ASoC drivers.
Ah, yes. Good to know.
Thanks!
--
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 prev parent reply other threads:[~2014-03-10 10:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 16:53 integration into ASoC Maxime Ripard
2014-03-07 17:12 ` Lars-Peter Clausen
2014-03-09 7:48 ` Mark Brown
2014-03-10 10:11 ` Maxime Ripard [this message]
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=20140310101153.GD2815@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=lars@metafoo.de \
--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