From: Patrick Lai <plai@codeaurora.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Question about your DSP topic branch
Date: Tue, 25 Jan 2011 22:22:41 -0800 [thread overview]
Message-ID: <4D3FBDB1.90804@codeaurora.org> (raw)
In-Reply-To: <20110125115113.GB13051@sirena.org.uk>
On 1/25/2011 3:51 AM, Mark Brown wrote:
> On Mon, Jan 24, 2011 at 11:01:10PM -0800, Patrick Lai wrote:
>
>> 8. I see there is dmic codec(dmic.c) under sound/soc/codec which is
>> pretty much just a dummy codec driver. I supposed the configuration of
>> DMIC is done in other driver. Would it be better if we could have
>
> It's for direct DMIC interfaces in CPUs like OMAP4 has.
>
>> something like fixed voltage regulator? So, there is no need to
>> duplicate the effort.
>
> Yes, that'd be kind of nice but given how tiny these noop drivers are
> and the fact that they do all need to specify their capabilites it's not
> clear that there's much advantage from combining them into a single
> driver - the boiler plate is so small and simple.
Do we consider the case that codec driver is not required such as
virtual sink or sink is configured outside of ALSA driver? If we create
dummy codec driver for each use case, wouldn't sound/soc/codecs end up
littered with bunch of noop drivers? Furthermore, couldn't capabilities
being passed through platform device?
Thanks
Patrick
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2011-01-26 6:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D2652C8.7030701@codeaurora.org>
2011-01-25 7:01 ` Question about your DSP topic branch Patrick Lai
2011-01-25 11:51 ` Mark Brown
2011-01-26 6:22 ` Patrick Lai [this message]
2011-01-26 11:20 ` Mark Brown
2011-01-27 21:51 ` Patrick Lai
2011-01-31 13:30 ` Mark Brown
2011-03-17 7:29 ` Patrick Lai
2011-03-17 11:57 ` Mark Brown
2011-01-25 16:46 ` Liam Girdwood
2011-01-27 23:41 ` Patrick Lai
2011-03-15 7:08 ` [alsa-devel] " Patrick Lai
2011-03-15 11:25 ` Mark Brown
2011-03-17 7:21 ` Patrick Lai
2011-03-17 23:58 ` Mark Brown
2011-03-30 20:39 ` Question about your DSP topic Patrick Lai
2011-03-31 6:40 ` Question about your DSP topic branch Patrick Lai
2011-03-31 21:35 ` Liam Girdwood
2011-03-31 21:42 ` Mark Brown
2011-03-31 22:07 ` Patrick Lai
2011-03-31 18:26 ` Question about your DSP topic Liam Girdwood
2011-03-31 20:59 ` Patrick Lai
2011-03-31 21:37 ` Liam Girdwood
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=4D3FBDB1.90804@codeaurora.org \
--to=plai@codeaurora.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.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;
as well as URLs for NNTP newsgroup(s).