[Bug 108014] AMD WX4150 - Hotplugging on an MST hub doesn't work

[bugzilla-daemon@freedesktop.org]

[-- Attachment #1.1: Type: text/plain, Size: 2218 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=108014

Lyude Paul <lyude@redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|AMD WX4150 - MST is         |AMD WX4150 - Hotplugging on
                   |entirely nonfunctional,     |an MST hub doesn't work
                   |spams dmesg with errors     |
           Priority|high                        |medium
           Severity|major                       |normal

--- Comment #8 from Lyude Paul <lyude@redhat.com> ---
(In reply to Jerry Zuo from comment #4)
> Created attachment 141903 [details] [review]
> MST patch

First off sorry for this taking so long. I had been prepared to test this
pretty quickly originally, but there was a mixup in the office and the laptop I
needed to reproduce this got sent to another office until today. So this might
not get done in the time I was hoping for, but that's ok as that isn't AMD's
fault. Additionally, the problem is less severe then I originally thought
anyway.

So, after testing a couple of kernels mst seems to work now that I'm back from
XDC. I think what must have happened is I didn't get enough time to look at it
closely, and got confused by two things:

- The external monitors on the MST hub not coming on were most likely caused by
the keypress spam from the ACPI hotplug events and I just didn't notice at the
time. I have a fix for this by the way which still needs reviews!
https://patchwork.freedesktop.org/patch/251897/
- I /thought/ I was actually testing hotplugging by removing the entire
topology instead of just downstream sinks, as downstream sink hotplugging isn't
nearly as important as the former and I kind of expected downstream sink
hotplugging to be broken anyway. But, I guess not? Weird.

All of that being said, that means this is a lot more severe then I thought!
:), phew.

----
Now onto the actual patch that you sent: what exactly is this supposed to be
doing? Are we dereferencing an mstb's port too early somewhere in the DRM MST
core?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4107 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel