From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Clark, Rob" <rob@ti.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
Ricardo Neri <ricardo.neri@ti.com>,
DRI development list <dri-devel@lists.freedesktop.org>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
"Guiriec, Sebastien" <s-guiriec@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Liam Girdwood <lrg@ti.com>
Subject: Re: [RFC] ASoC: snd_soc_jack for HDMI audio: does it make sense?
Date: Tue, 21 Aug 2012 14:18:19 +0100 [thread overview]
Message-ID: <20120821131818.GE7995@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAO8GWq=B8wa1tWOiT5ja80T2VrxHiSKSp4U6fHydV9iyOg=+Zg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 498 bytes --]
On Tue, Aug 21, 2012 at 07:39:55AM -0500, Clark, Rob wrote:
> Does ASoC support 'hotplug' of audio devices? If so, maybe it makes
> some sense to have some support in drm core. At least all the edid
> parsing stuff to determine if the display supports audio should be
> generic and not driver specific.
Not really (except on a card level), and it'd probably confuse most
userspaces. What I'd expect to happen currently is that the current
state of the connector would get reported via extcon.
[-- 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-08-21 13:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 1:47 [RFC] ASoC: snd_soc_jack for HDMI audio: does it make sense? Ricardo Neri
2012-08-21 5:28 ` [alsa-devel] " Takashi Iwai
2012-08-21 12:05 ` Mark Brown
2012-08-21 12:30 ` [alsa-devel] " David Henningsson
2012-08-21 13:16 ` Mark Brown
2012-08-22 1:24 ` Ricardo Neri
2012-08-22 16:40 ` Mark Brown
2012-08-24 7:10 ` [alsa-devel] " Arun Raghavan
2012-08-27 18:55 ` Mark Brown
2012-08-21 6:01 ` Tomi Valkeinen
2012-08-21 12:39 ` Clark, Rob
2012-08-21 13:18 ` Mark Brown [this message]
2012-08-22 0:58 ` Ricardo Neri
2012-08-22 7:55 ` [alsa-devel] " Takashi Iwai
2012-08-24 1:44 ` Ricardo Neri
2012-08-24 2:57 ` Stephen Warren
2012-08-24 5:21 ` [alsa-devel] " Takashi Iwai
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=20120821131818.GE7995@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=ricardo.neri@ti.com \
--cc=rob@ti.com \
--cc=s-guiriec@ti.com \
--cc=tomi.valkeinen@ti.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).