From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Arun Raghavan <arun.raghavan@collabora.co.uk>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
Takashi Iwai <tiwai@suse.de>, Ricardo Neri <ricardo.neri@ti.com>,
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>
Subject: Re: [RFC] ASoC: snd_soc_jack for HDMI audio: does it make sense?
Date: Mon, 27 Aug 2012 11:55:42 -0700 [thread overview]
Message-ID: <20120827185541.GB4339@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1345792237.11808.85.camel@localhost>
On Fri, Aug 24, 2012 at 12:40:37PM +0530, Arun Raghavan wrote:
> It's been in shambles for an absurdly long time. Would be good to
> actually try to tackle it again at Plumbers or sth.
I think all this really needs is someone with the time to do the work -
it's more a coding problem with unifying the in kernel API than an issue
with working out what to do.
next prev parent reply other threads:[~2012-08-27 18:55 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 [this message]
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=20120827185541.GB4339@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=arun.raghavan@collabora.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.