From: Stefan Wahren <stefan.wahren@i2se.com>
To: Eric Anholt <eric@anholt.net>,
Maxime Ripard <maxime.ripard@bootlin.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Sean Paul <seanpaul@chromium.org>,
Daniel Vetter <daniel.vetter@intel.com>,
David Airlie <airlied@linux.ie>
Cc: Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
linux-arm-kernel@lists.infradead.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
dri-devel@lists.freedesktop.org, eben@raspberrypi.org
Subject: Re: [PATCH 1/7] drm/vc4: hdmi: Check that the monitor supports HDMI audio
Date: Mon, 4 Mar 2019 21:06:31 +0100 (CET) [thread overview]
Message-ID: <1185446515.301320.1551729991062@email.ionos.de> (raw)
In-Reply-To: <87sgw21ok9.fsf@anholt.net>
> Eric Anholt <eric@anholt.net> hat am 4. März 2019 um 19:28 geschrieben:
>
>
> Stefan Wahren <stefan.wahren@i2se.com> writes:
>
> > Hi Maxime,
> >
> > Am 04.03.2019 um 15:52 schrieb Maxime Ripard:
> >> The current code assumes as soon as the device is an HDMI one that it
> >> supports an audio sink. However, strictly speaking, this is exposed as a
> >> separate part of EDID.
> >>
> >> This can be checked through the drm_detect_monitor_audio function, so let's
> >> use it and make sure that we can use the HDMI monitor as an output before
> >> sending sound.
> >
> > does the audio output work in the following setup after applying this patch?
> >
> > VC4 --- HDMI Audio extractor --- Non audio capable monitor
>
> A 1-minute google of audio extractors says they manage the EDID. Do you
> have some reason to think this wouldn't work?
My only concern is the existence of some audio extractors which doesn't care about EDID. I that case we need to provide some kind of force switch.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-03-04 20:06 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 14:52 [PATCH 0/7] drm/vc4: Allow for more boot-time configuration Maxime Ripard
2019-03-04 14:52 ` [PATCH 1/7] drm/vc4: hdmi: Check that the monitor supports HDMI audio Maxime Ripard
2019-03-04 15:10 ` Paul Kocialkowski
2019-03-04 15:54 ` Stefan Wahren
2019-03-04 18:28 ` Eric Anholt
2019-03-04 20:06 ` Stefan Wahren [this message]
2019-03-04 21:09 ` Eric Anholt
2019-03-04 14:52 ` [PATCH 2/7] drm/edid: Allow to ignore the audio EDID data Maxime Ripard
2019-03-04 15:47 ` Jani Nikula
2019-03-04 15:51 ` Adam Jackson
2019-03-05 8:08 ` Maxime Ripard
2019-03-05 10:33 ` Jani Nikula
2019-03-05 15:08 ` Adam Jackson
2019-03-04 15:59 ` Ville Syrjälä
2019-03-04 19:53 ` Eric Anholt
2019-03-04 20:05 ` Alex Deucher
2019-03-05 9:12 ` Maxime Ripard
2019-03-05 15:24 ` Ville Syrjälä
2019-03-05 19:15 ` Ville Syrjälä
2019-03-05 19:21 ` Alex Deucher
2019-03-05 19:36 ` Ville Syrjälä
2019-03-13 10:44 ` Takashi Iwai
2019-03-13 14:03 ` Maxime Ripard
2019-03-05 18:11 ` Eric Anholt
2019-03-11 13:07 ` Daniel Vetter
2019-03-05 21:47 ` Eric Anholt
2019-03-06 8:52 ` Maxime Ripard
2019-03-06 13:22 ` Maxime Ripard
2019-03-06 17:51 ` Eric Anholt
2019-03-04 14:52 ` [PATCH 3/7] drm/edid: Allow to ignore the HDMI monitor mode Maxime Ripard
2019-03-04 15:14 ` Paul Kocialkowski
2019-03-04 15:48 ` Jani Nikula
2019-03-04 20:02 ` Eric Anholt
2019-03-05 9:24 ` Maxime Ripard
2019-03-04 14:52 ` [PATCH 4/7] drm/modes: Rewrite the command line parser Maxime Ripard
2019-03-04 14:52 ` [PATCH 5/7] drm/modes: Support modes names on the command line Maxime Ripard
2019-03-04 14:52 ` [PATCH 6/7] drm/modes: Allow to specify rotation and reflection on the commandline Maxime Ripard
2019-03-04 14:52 ` [PATCH 7/7] drm/modes: Parse overscan properties Maxime Ripard
2019-03-04 15:21 ` [PATCH 0/7] drm/vc4: Allow for more boot-time configuration Peter Stuge
2019-03-04 15:56 ` Maxime Ripard
2019-03-04 15:44 ` Stefan Wahren
2019-03-04 20:06 ` Eric Anholt
2019-03-05 9:14 ` Maxime Ripard
2019-03-11 13:00 ` Daniel Vetter
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=1185446515.301320.1551729991062@email.ionos.de \
--to=stefan.wahren@i2se.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eben@raspberrypi.org \
--cc=eric@anholt.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maxime.ripard@bootlin.com \
--cc=paul.kocialkowski@bootlin.com \
--cc=seanpaul@chromium.org \
--cc=thomas.petazzoni@bootlin.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).