From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ricardo Neri <ricardo.neri@ti.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
Takashi Iwai <tiwai@suse.de>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
"Valkeinen, Tomi" <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>,
David Henningsson <david.henningsson@canonical.com>
Subject: Re: [RFC] ASoC: snd_soc_jack for HDMI audio: does it make sense?
Date: Wed, 22 Aug 2012 17:40:57 +0100 [thread overview]
Message-ID: <20120822164056.GS7995@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <503434DD.8030003@ti.com>
[-- Attachment #1.1: Type: text/plain, Size: 675 bytes --]
On Tue, Aug 21, 2012 at 08:24:45PM -0500, Ricardo Neri wrote:
> So, it seems that the way to go is extcon. I guess that ALSA will
> use extcon just like today snd_jack uses the input driver. is this
> correct? Is there any chance that ctrljack will propagate the events
> through extcon? Is there any early implementation that I could look
> at? I am asking to know how feasible is to use ctljack today and be
> compatible with extcon in the future.
The ctljack API doesn't really map onto the other jack APIs at the
minute since the in kernel representation is that it exposes the
booleans directly to the callers rather than grouping them together into
the overall jack.
[-- 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-22 16:40 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 [this message]
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
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=20120822164056.GS7995@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=ricardo.neri@ti.com \
--cc=s-guiriec@ti.com \
--cc=tiwai@suse.de \
--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).