From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: alsa-devel@alsa-project.org, Stephen Warren <swarren@nvidia.com>,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH V2 1/3] ASoC: tegra: add tegra30-ahub driver
Date: Fri, 13 Apr 2012 11:17:48 +0100 [thread overview]
Message-ID: <20120413101748.GO3168@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1334097121-18897-1-git-send-email-swarren@wwwdotorg.org>
[-- Attachment #1.1: Type: text/plain, Size: 670 bytes --]
On Tue, Apr 10, 2012 at 04:31:59PM -0600, Stephen Warren wrote:
> From: Stephen Warren <swarren@nvidia.com>
>
> The AHUB (Audio Hub) is a mux/crossbar which links all audio-related
> devices except the HDA controller on Tegra30. The devices include the
> DMA FIFOs, DAM (Digital Audio Mixers), I2S controllers, and SPDIF
> controller. Audio data may be routed between these devices in various
> combinations as required by board design/application.
Applied all, thanks. I'd have been slightly happier if we'd had the
machine driver to show how this is used but there's enough plans to
continue updating the code anyway so it doesn't seem like a big deal.
[-- 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:[~2012-04-13 10:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 22:31 [PATCH V2 1/3] ASoC: tegra: add tegra30-ahub driver Stephen Warren
2012-04-10 22:32 ` [PATCH V2 2/3] ASoC: tegra: add tegra30-i2s driver Stephen Warren
2012-04-10 22:32 ` [PATCH V2 3/3] ASoC: tegra: add Kconfig and Makefile support for Tegra30 Stephen Warren
2012-04-13 10:17 ` Mark Brown [this message]
2012-04-13 15:54 ` [PATCH V2 1/3] ASoC: tegra: add tegra30-ahub driver Stephen Warren
2012-04-13 16:09 ` Mark Brown
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=20120413101748.GO3168@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.org \
/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).