From: David Brownell <david-b@pacbell.net>
To: Mark Brown <broonie@sirena.org.uk>
Cc: Jarkko Nikula <jarkko.nikula@nokia.com>,
"Stanley.Miao" <stanley.miao@windriver.com>,
alsa-devel@alsa-project.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAP general SOC driver.
Date: Wed, 26 Nov 2008 12:33:12 -0800 [thread overview]
Message-ID: <200811261233.13259.david-b@pacbell.net> (raw)
In-Reply-To: <20081126200750.GK6234@sirena.org.uk>
On Wednesday 26 November 2008, Mark Brown wrote:
> Can someone post an overview of what the hardware configurations of
> these boards are, please? It's starting to sound like they're not very
> similar at all.
I only have schematics for Beagle ... which makes VERY minimal
use of the twl4030 audio capabilities:
- stereo "headset" output, without its mic
- stereo aux-in
Other twl4030 family boards *could* have:
- microphone input for that headset
- stereo "hands-off" speakers
- mono earpiece output
- two other microphone input channels
And maybe more; that's just me summarizing unconnected pins,
not the datasheet. There are also cost-reduced parts with
less audio capability.
I make no claim about audio expertise -- the nearest I come
to it is observing a few years back that there was a huge
framework hole, which ASoC seems to fill -- but I wonder if
it shouldn't suffice just to provide a mask of capabilities
that are wired up on a given board.
- Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-11-26 20:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 10:47 [PATCH] OMAP general SOC driver Stanley.Miao
2008-11-26 11:08 ` Mark Brown
2008-11-26 11:40 ` Jarkko Nikula
2008-11-26 18:34 ` David Brownell
2008-11-26 20:07 ` Mark Brown
2008-11-26 20:20 ` Koen Kooi
2008-11-27 5:01 ` Arun KS
[not found] ` <6ed0b2680811270242i1b857f13i9494826f6089bf15@mail.gmail.com>
2008-11-27 12:36 ` Mark Brown
2008-11-26 20:33 ` David Brownell [this message]
2008-11-26 21:16 ` Mark Brown
2008-11-26 22:03 ` David Brownell
2008-11-27 12:39 ` stanley.miao
2008-11-26 20:44 ` David Brownell
2008-11-26 21:22 ` Mark Brown
2008-11-26 17:24 ` Steve Sakoman
2008-11-26 17:29 ` [alsa-devel] " Mark Brown
2008-11-26 15:53 ` Tony Lindgren
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=200811261233.13259.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@sirena.org.uk \
--cc=jarkko.nikula@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=stanley.miao@windriver.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