Public bug reported:
[Impact]
Hotplugging different monitors on different ports makes HDMI audio
disappears.
[Fix]
Make sure new EDID is added.
[Test case]
Boot up with a HDMI monitor with audio output, unplug the monitor and
plug another monitor without speaker and without audio jack.
Then plug back the original monitor.
With the patch applied, there's still HDMI audio output from the
original monitor.
[Where problems could occur]
If the EDID is valid, the driver does the correct thing.
If the EDID is invalid, then the driver spends a bit more time setting
up EDID, without doing any harm.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux-oem-5.6 (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux-oem-5.6 (Ubuntu Focal)
Importance: Medium
Status: Confirmed
** Tags: oem-priority originate-from-1896207 sutton
** Package changed: linux (Ubuntu) => linux-oem-5.6 (Ubuntu)
** Also affects: linux-oem-5.6 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-oem-5.6 (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Status: New => Confirmed
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Importance: Undecided => Medium
** Tags added: oem-priority originate-from-1896207 sutton
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1904430
Title:
Fix AMD GFX where no HDMI audio when hotplugging different monitors
Status in HWE Next:
New
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux-oem-5.6 source package in Focal:
Confirmed
Bug description:
[Impact]
Hotplugging different monitors on different ports makes HDMI audio
disappears.
[Fix]
Make sure new EDID is added.
[Test case]
Boot up with a HDMI monitor with audio output, unplug the monitor and
plug another monitor without speaker and without audio jack.
Then plug back the original monitor.
With the patch applied, there's still HDMI audio output from the
original monitor.
[Where problems could occur]
If the EDID is valid, the driver does the correct thing.
If the EDID is invalid, then the driver spends a bit more time setting
up EDID, without doing any harm.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1904430/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
