diff options
| author | Imre Deak <imre.deak@intel.com> | 2021-02-16 14:34:48 +0200 |
|---|---|---|
| committer | Imre Deak <imre.deak@intel.com> | 2021-02-18 16:41:35 +0200 |
| commit | f0297cc0fd2bded129ccc1e00528d06362b6075d (patch) | |
| tree | e82977f7f8b158b48539c4eec2bbc0748de2ed66 /mm/sparse-vmemmap.c | |
| parent | 1b588c82f63ebef55bccac4f0ca9c2825b9a9ae4 (diff) | |
| download | linux-f0297cc0fd2bded129ccc1e00528d06362b6075d.tar.bz2 | |
drm/dp_mst: Tune down the WARN modesetting a port with full_pbn=0
It's possible to modeset a connector/mst port that has a 0 full_pbn
value: if the sink on the port deasserts its HPD and a branch device
reports this via a CSN with the port's ddps=0 and pdt!=NONE the driver
clears full_pbn, but the corresponding connector can be still
modesetted.
This happened on a DELL U2719D monitor as the branch device and an LG
27UL650-W daisy-chained to it, the LG monitor generating a long HPD
pulse (doing this for some reason always when waking up from some power
saving state).
Tune down the WARN about this scenario to a debug message.
v2: Use the correct atomic debug message level. (Lyude)
References: https://gitlab.freedesktop.org/drm/intel/-/issues/1917
Cc: Lyude Paul <lyude@redhat.com>
Signed-off-by: Imre Deak <imre.deak@intel.com>
Reviewed-by: Lyude Paul <lyude@redhat.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20210216123448.410545-1-imre.deak@intel.com
Diffstat (limited to 'mm/sparse-vmemmap.c')
0 files changed, 0 insertions, 0 deletions