From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: "devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Rob Herring <robherring2@gmail.com>, Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH v2 2/6] ASoC: Allow the DAPM routes to be stored in device tree
Date: Tue, 13 Dec 2011 12:07:29 +0800 [thread overview]
Message-ID: <20111213040728.GA4565@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF1751860838@HQMAIL01.nvidia.com>
On Mon, Dec 12, 2011 at 11:34:13AM -0800, Stephen Warren wrote:
> Mark Brown wrote at Saturday, December 10, 2011 5:49 AM:
> > It's starting to get an idiomatic way of representing the external
> > nodes, HDA is probably a good source of inspiration :) We do need to
> > have a think about the jacks, though - simple ones are fine but
> > multifinction is more fun.
> I just wanted to confirm that you're talking about multiple audio
> functions here (e.g. mic+headphones), rather than mixing audio with
> other features (e.g. s-video + line out). I don't think the latter has
Both.
> any kind of representation in the kernel right now though? That said,
Depends; if you listen to Lennart and Kay it's totally there already and
there's nothing to worry about.
> it might be a good idea to represent jacks outside any audio complex
> DT node, so that they could host functionality of different types if
> the HW does so...
Clearly, and even audio jacks have non-audio functionality like buttons.
next prev parent reply other threads:[~2011-12-13 4:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 20:58 [PATCH v2 1/6] ASoC: Allow device tree to specify a card's name Stephen Warren
[not found] ` <1323291510-22338-1-git-send-email-swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-12-07 20:58 ` [PATCH v2 2/6] ASoC: Allow the DAPM routes to be stored in device tree Stephen Warren
[not found] ` <1323291510-22338-2-git-send-email-swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-12-08 4:31 ` Mark Brown
[not found] ` <20111208043149.GA31372-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2011-12-09 21:52 ` Stephen Warren
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF17518605B1-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2011-12-10 12:49 ` Mark Brown
[not found] ` <20111210124921.GA20568-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2011-12-12 19:08 ` Stephen Warren
[not found] ` <4EE65128.2090209-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-12-13 1:32 ` Mark Brown
2011-12-12 19:34 ` Stephen Warren
2011-12-13 4:07 ` Mark Brown [this message]
2011-12-07 20:58 ` [PATCH v2 3/6] ASoC: Refactor some conditions and loop in soc_bind_dai_link() Stephen Warren
[not found] ` <1323291510-22338-3-git-send-email-swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-12-09 4:46 ` Mark Brown
2011-12-07 20:58 ` [PATCH v2 4/6] ASoC: Allow DAI links to be specified using device tree nodes Stephen Warren
[not found] ` <1323291510-22338-4-git-send-email-swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-12-09 6:03 ` Mark Brown
2011-12-07 20:58 ` [PATCH v2 5/6] ASoC: Tegra: Move DAS configuration into DAS driver Stephen Warren
[not found] ` <1323291510-22338-5-git-send-email-swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-12-08 4:34 ` Mark Brown
2011-12-07 20:58 ` [PATCH v2 6/6] ASoC: Tegra+WM8903 machine: Add device tree binding Stephen Warren
2011-12-08 1:31 ` [PATCH v2 1/6] ASoC: Allow device tree to specify a card's name Mark Brown
2011-12-08 19:17 ` Liam Girdwood
2011-12-09 3:17 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2011-12-07 22:13 [PATCH v2 0/8] arm/tegra: Device tree support for audio Stephen Warren
[not found] ` <1323296033-28730-1-git-send-email-swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-12-07 22:13 ` [PATCH v2 2/6] ASoC: Allow the DAPM routes to be stored in device tree Stephen Warren
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=20111213040728.GA4565@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=lrg@ti.com \
--cc=robherring2@gmail.com \
--cc=swarren@nvidia.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).