From: Philipp Zabel <p.zabel@pengutronix.de>
To: Jyri Sarha <jsarha@ti.com>
Cc: Jean-Francois Moine <moinejf@free.fr>,
alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Arnaud Pouliquen <arnaud.pouliquen@st.com>,
Koro Chen <koro.chen@mediatek.com>,
Daniel Kurtz <djkurtz@chromium.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-mediatek@lists.infradead.org, kernel@pengutronix.de,
Matthias Brugger <matthias.bgg@gmail.com>,
Cawa Cheng <cawa.cheng@mediatek.com>
Subject: Re: [RFC v2 6/6] ASoC: hdmi-codec: Use HDMI notifications to add jack support
Date: Fri, 08 Jan 2016 09:43:49 +0100 [thread overview]
Message-ID: <1452242629.3347.12.camel@pengutronix.de> (raw)
In-Reply-To: <568E9BE1.6050209@ti.com>
Hi Jyri,
Am Donnerstag, den 07.01.2016, 19:09 +0200 schrieb Jyri Sarha:
> On 01/04/16 21:19, Philipp Zabel wrote:
> > Use HDMI connection / disconnection notifications to update an ALSA
> > jack object. Also make a copy of the ELD block after every change.
> >
>
> The jack part looks good to me AFAIU,
If this is in principle an acceptable idea, this leaves the issue that
the jack has an initial state and right now we can't query it but
instead would have to wait for the first HDMI_(DIS)CONNECTED
notification before it can be set. Would it make sense to add an
is_connected callback to the hdmi_codec_ops or does this rather belong
somewhere else?
> but I think we should just update
> the local ELD copy with data given in the ELD notification. It then
> depends on the implementation details whether the get_eld() callback is
> needed at all or if it should be called once at the probe time.
Thanks, that sounds reasonable.
> Then it is a separate issue to check if the currently played stream is
> still supported after an ELD update, and to decide what to do about it
> if it is not.
[...]
Possibly the HDMI driver itself should just mute if the format is not
supported, and userspace should be notified?
regards
Philipp
next prev parent reply other threads:[~2016-01-08 8:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 19:09 [RFC v2 0/6] ASoC: Add mediatek HDMI codec support Philipp Zabel
2016-01-04 19:09 ` [RFC v2 1/6] drm/mediatek: hdmi: Add audio interface to the hdmi-codec driver Philipp Zabel
2016-01-04 22:29 ` Russell King - ARM Linux
2016-01-05 14:56 ` Philipp Zabel
[not found] ` <1451934551-21333-1-git-send-email-p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2016-01-04 19:09 ` [RFC v2 2/6] ASoC: mediatek: address dai link array entries by enum Philipp Zabel
2016-01-04 19:15 ` [RFC v2 3/6] ASoC: mediatek: Add HDMI dai-links in the machine driver Philipp Zabel
2016-01-05 12:46 ` Mark Brown
2016-01-07 10:06 ` Philipp Zabel
2016-03-05 12:24 ` Applied "ASoC: mediatek: address dai link array entries by enum" to the asoc tree Mark Brown
2016-01-04 19:19 ` [RFC v2 6/6] ASoC: hdmi-codec: Use HDMI notifications to add jack support Philipp Zabel
2016-01-07 17:09 ` Jyri Sarha
2016-01-08 8:43 ` Philipp Zabel [this message]
2016-01-08 9:57 ` Jyri Sarha
2016-01-08 10:46 ` Russell King - ARM Linux
2016-01-08 10:52 ` Takashi Iwai
2016-01-08 12:55 ` Mark Brown
2016-01-04 19:11 ` [RFC v2 0/6] ASoC: Add mediatek HDMI codec support Russell King - ARM Linux
2016-01-04 19:18 ` [RFC v2 4/6] video: rmk's HDMI notification prototype Philipp Zabel
2016-01-04 19:18 ` [RFC v2 5/6] drm/mediatek: hdmi: issue notifications Philipp Zabel
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=1452242629.3347.12.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.pouliquen@st.com \
--cc=broonie@kernel.org \
--cc=cawa.cheng@mediatek.com \
--cc=djkurtz@chromium.org \
--cc=jsarha@ti.com \
--cc=kernel@pengutronix.de \
--cc=koro.chen@mediatek.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=matthias.bgg@gmail.com \
--cc=moinejf@free.fr \
/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).