On Wednesday, March 23, 2022 6:40 PM, Jani wrote :
>On Wed, 23 Mar 2022, "Lee, Shawn C" wrote:
>> On Wednesday, March 23, 2022 6:04 PM, Nikula, Jani
>> wrote :
>>>On Mon, 21 Mar 2022, Cooper Chiou wrote:
In DisplayID v2.0 CTS data block 0x81 case, there is no any audio
information
On Wed, 23 Mar 2022, "Lee, Shawn C" wrote:
> On Wednesday, March 23, 2022 6:04 PM, Nikula, Jani
> wrote :
>>On Mon, 21 Mar 2022, Cooper Chiou wrote:
>>> In DisplayID v2.0 CTS data block 0x81 case, there is no any audio
>>> information definition, but drm_detect_monitor_audio didn't filter it
On Wednesday, March 23, 2022 6:04 PM, Nikula, Jani
wrote :
>On Mon, 21 Mar 2022, Cooper Chiou wrote:
>> In DisplayID v2.0 CTS data block 0x81 case, there is no any audio
>> information definition, but drm_detect_monitor_audio didn't filter it
>> so that it caused eDP dummy audio card be
On Mon, 21 Mar 2022, Cooper Chiou wrote:
> In DisplayID v2.0 CTS data block 0x81 case, there is no any audio
> information definition, but drm_detect_monitor_audio didn't filter
> it so that it caused eDP dummy audio card be detected improperly.
>
> We observed this issue on some AUO/BOE eDP
On Mon, 21 Mar 2022, Cooper Chiou wrote:
> In DisplayID v2.0 CTS data block 0x81 case, there is no any audio
> information definition, but drm_detect_monitor_audio didn't filter
> it so that it caused eDP dummy audio card be detected improperly.
>
> We observed this issue on some AUO/BOE eDP
In DisplayID v2.0 CTS data block 0x81 case, there is no any audio
information definition, but drm_detect_monitor_audio didn't filter
it so that it caused eDP dummy audio card be detected improperly.
We observed this issue on some AUO/BOE eDP panel with DID v2.0 CTA
block, and fix issue by adding
