From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 71083] New: (struct drm_encoder_helper_funcs)->mode_set not re-called after display (and EDID) change
Date: Thu, 31 Oct 2013 10:34:13 +0000 [thread overview]
Message-ID: <bug-71083-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2363 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=71083
Priority: medium
Bug ID: 71083
Assignee: dri-devel@lists.freedesktop.org
Summary: (struct drm_encoder_helper_funcs)->mode_set not
re-called after display (and EDID) change
Severity: normal
Classification: Unclassified
OS: All
Reporter: zajec5@gmail.com
Hardware: Other
Status: NEW
Version: unspecified
Component: DRM/other
Product: DRI
I use my DCE5 Barts (HD69xx) with AV-receiver Onkyo TX-SR605 and one of the
following displays:
1) TV Sony Bravia KDL-52X3500
2) Projector Epson EH-TW6100
My problem is that when I change display connected to the Onkyo's output EDID
changes, but drm doesn't call mode_set as long as I use the same resolution.
To force drm to call mode_set I've to change resolution (xrandr --output HDMI-0
--mode X) and then swtich back to the mode I want.
While the display seems to be working fine without that mode_set call, the
audio engine doesn't. As part of the modesetting handler we read ELD-related
info from EDID and write it to the audio engine of the GPU. Without this
happening I can't play correctly audio (because also sees info about previous
device, not the current one).
I think mode_set should be called every time EDID changes. Is that right?
In case someone's curious:
1) EDID with Onkyo + Sony TV:
00ffffffffffff003dcb610700000000
0011010380a05a780a0dc9a057479827
12484c21080081800101010101010101
010101010101023a801871382d40582c
450040846300001e011d007251d01e20
6e28550040846300001e000000fc0054
582d53523630350a20202020000000fd
00303e0e460f000a2020202020200185
02034c705c1f03041213051420071610
15110206010f1e0b1a191d0e0a242625
2335097f070f7f071707503f06c05706
005f7e01671e00834f00006c030c0012
00b82dc000000000e3050301023a80d0
72382d40102c458040846300001e011d
00bc52d01e20b828554040846300001e
00000000000000000000000000000078
2) EDID with Onkyo + Epson projector:
00ffffffffffff004ca333d000000000
0c150104952616780aa0558d515a962a
1c505400000001010101010101010101
0101010101016a4d80a07038fc413020
36007ed710000018d49a80a07038fc41
302036007ed710000038000000fc0053
414d53554e470a2020202020000000fc
00313733485430322d4330310a200035
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3694 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2013-10-31 10:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 10:34 bugzilla-daemon [this message]
2013-10-31 13:17 ` [Bug 71083] (struct drm_encoder_helper_funcs)->mode_set not re-called after display (and EDID) change bugzilla-daemon
2013-10-31 13:42 ` bugzilla-daemon
2019-10-14 13:20 ` bugzilla-daemon
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=bug-71083-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/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).