Stefan Wahren writes:
>> Eric Anholt hat am 4. März 2019 um 19:28 geschrieben:
>>
>>
>> Stefan Wahren 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. H
> Eric Anholt hat am 4. März 2019 um 19:28 geschrieben:
>
>
> Stefan Wahren 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 i
Stefan Wahren 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
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 le
Hi,
On Mon, 2019-03-04 at 15:52 +0100, Maxime Ripard wrote:
> 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 func
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
