| Priority | medium |
|---|---|
| Bug ID | 80691 |
| Assignee | dri-devel@lists.freedesktop.org |
| Summary | HDMI audio stops working when drm_kms_helper edid overwrite in place |
| Severity | normal |
| Classification | Unclassified |
| OS | Linux (All) |
| Reporter | warlock0@hotmail.com |
| Hardware | x86-64 (AMD64) |
| Status | NEW |
| Version | XOrg CVS |
| Component | DRM/Radeon |
| Product | DRI |
Created attachment 101987 [details]
dmesg
When powering on a PC with radeon gpu (E350 in this case), without an output
device powered on (on the hdmi out), X won't start.
Therefore using drm_kms_helper to overwrite the edid information and forcing
the display to on is needed.
In this combination the hdmi audio output is not working.
It also is not working if the system is started with the overwrite in place and
TV / AVR turned on.
It seems as if the audio codec is not enabled when EDID is loaded with
drm_kms_helper
Expectation: Audio will continue to work when overwriting EDID with
drm_kms_helper.
Created attachment 101988 [details]
edid parsed with edid-decode
Created attachment 101989 [details]
extracted edid.bin
I am also affected by this bug, running a Zotac ZBox AD02 with AMD Fusion. Can I provide more information that is needed to get this fixed?
The driver caches a copy of the edid in the driver connector structure (radeon_connector->edid) when it it reads the edid from the monitor via the get_modes() or detect() connector callbacks. When you provide a user supplied edid, the driver's copy never gets updated since no additional driver callbacks are called. It should be handled properly on my 3.17-wip branch: http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-3.17-wip
(In reply to Alex Deucher from comment #4) > The driver caches a copy of the edid in the driver connector structure > (radeon_connector->edid) when it it reads the edid from the monitor via the > get_modes() or detect() connector callbacks. When you provide a user > supplied edid, the driver's copy never gets updated since no additional > driver callbacks are called. It should be handled properly on my 3.17-wip > branch: > http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-3.17-wip Alex, did not look at what you did there, but there's no confirmation from the reporters either. I submitted [1] to fix bug 82349, maybe that's relevant for you too? [1] http://patchwork.freedesktop.org/patch/45675/
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | MOVED |
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this = link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/509.