From: Jyri Sarha <jsarha@ti.com>
To: alsa-devel@alsa-project.org, dri-devel@lists.freedesktop.org,
"David Airlie" <airlied@linux.ie>,
tomi.valkeinen@ti.com, lgirdwood@gmail.com, broonie@kernel.org,
peter.ujfalusi@ti.com,
"Russell King - ARM Linux " <linux@arm.linux.org.uk>,
lars@metafoo.de, "Jean-Francois Moine" <moinejf@free.fr>,
"Arnaud Pouliquen" <arnaud.pouliquen@st.com>
Subject: HDMI codec, way forward?
Date: Fri, 16 Oct 2015 14:50:26 +0300 [thread overview]
Message-ID: <5620E482.6050507@ti.com> (raw)
After reading the ELCE Audio mini conf minutes [1] I gather that HDMI
audio was not discussed after all.
My conclusion from the Lars-Peter's latest mail [2] related to the
subject is that the wind is currently blowing slightly in favour of my
version of the hdmi codec [3], or at least not in favour of Arnaud's
version [4].
So how should we proceed? Are we still waiting for some feedback from
DRM/video side?
There was not too many clear suggestions to my latest patch series
[3], so I do not see too much point in sending yet another version of
that series.
Arnaud, if I'd try to make a patch series that would implement sti
HDMI audio with my HDMI codec, would you be willing try that out?
Best regards,
Jyri
[1]
http://mailman.alsa-project.org/pipermail/alsa-devel/2015-October/098847.html
[2]
http://mailman.alsa-project.org/pipermail/alsa-devel/2015-October/098564.html
[3]
http://mailman.alsa-project.org/pipermail/alsa-devel/2015-September/097667.html
[4]
http://mailman.alsa-project.org/pipermail/alsa-devel/2015-October/098275.html
next reply other threads:[~2015-10-16 11:50 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 11:50 Jyri Sarha [this message]
2015-10-16 12:31 ` HDMI codec, way forward? Lars-Peter Clausen
2015-10-16 12:43 ` [alsa-devel] " Takashi Iwai
2015-10-16 13:37 ` Russell King - ARM Linux
2015-10-16 14:12 ` Mark Brown
2015-10-18 15:08 ` Vinod Koul
2015-10-18 15:20 ` Russell King - ARM Linux
2015-10-18 16:13 ` Vinod Koul
2015-10-18 16:22 ` Russell King - ARM Linux
2015-10-18 17:16 ` Russell King - ARM Linux
2015-10-19 13:20 ` [alsa-devel] " Takashi Iwai
2015-10-20 3:38 ` Vinod Koul
2015-10-20 8:08 ` [alsa-devel] " Russell King - ARM Linux
2015-10-20 14:01 ` Vinod Koul
2015-10-21 9:11 ` [alsa-devel] " Jani Nikula
2015-10-21 15:52 ` Vinod Koul
2015-10-21 9:27 ` [alsa-devel] " Russell King - ARM Linux
2015-10-21 13:41 ` Takashi Iwai
2015-10-21 14:03 ` Russell King - ARM Linux
2015-10-21 14:10 ` Takashi Iwai
2015-10-21 14:37 ` Takashi Iwai
2015-10-21 15:36 ` Daniel Vetter
2015-10-21 16:46 ` Takashi Iwai
2015-10-21 16:48 ` Takashi Iwai
2015-10-21 16:50 ` Takashi Iwai
2015-10-21 14:37 ` Russell King - ARM Linux
2015-10-21 16:19 ` Vinod Koul
2015-10-21 17:34 ` Russell King - ARM Linux
2015-10-21 17:59 ` [alsa-devel] " Takashi Iwai
2015-10-21 18:19 ` Russell King - ARM Linux
2015-10-21 20:37 ` Takashi Iwai
2015-10-21 21:04 ` Russell King - ARM Linux
2015-10-22 7:18 ` Daniel Vetter
2015-10-16 14:06 ` Mark Brown
2015-10-18 15:02 ` Vinod Koul
2015-10-19 20:14 ` Jyri Sarha
2015-10-16 13:51 ` Arnaud Pouliquen
2015-10-16 14:15 ` Mark Brown
2015-10-18 15:07 ` Vinod Koul
2015-10-19 13:10 ` Jyri Sarha
2015-10-19 13:31 ` Russell King - ARM Linux
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=5620E482.6050507@ti.com \
--to=jsarha@ti.com \
--cc=airlied@linux.ie \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.pouliquen@st.com \
--cc=broonie@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux@arm.linux.org.uk \
--cc=moinejf@free.fr \
--cc=peter.ujfalusi@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 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.