Bug 94592

Summary: [BSW] HDMI hotplug does not working
Product: DRI Reporter: cprigent <christophe.prigent>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED DUPLICATE QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: BSW/CHT i915 features: display/HDMI
Attachments:
Description Flags
bsw-kern.log none

Description cprigent 2016-03-17 14:37:34 UTC 
Created attachment 122380 [details]
bsw-kern.log

Hardware: 
Motherboard: Aspire XC-704 
cpu model name : Intel(R) Pentium(R) CPU N3700 @ 1.60GHz 
cpu model : 76 
cpu family : 6 
Graphic card: Device 22b1 (rev 21)

Software:
Ubuntu 14.04
Bios: R01-A2
Kernel mainline 4.4.0 from
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
  commit afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc
  Author: Linus Torvalds <torvalds@linux-foundation.org>
  Date:   Sun Jan 10 15:01:32 2016 -0800
  Linux 4.4
drm: libdrm-2.4.67-5 ea07de9 from git://anongit.freedesktop.org/mesa/drm
mesa: tag mesa-11.1.2 7bcd827 from git://anongit.freedesktop.org/mesa/mesa
cairo: tag 1.15.2 db8a7f1 from git://anongit.freedesktop.org/cairo
waffle: master bb29b2a from git://github.com/waffle-gl/waffle
xorg-server-macros: tag: util-macros-1.19.0-2 d7acec2 from
git://git.freedesktop.org/git/xorg/util/macros
xserver: tag: xorg-server-1.18.1 23e60f9 from
git://git.freedesktop.org/git/xorg/xserver
xf86-video-intel: tag 2.99.917-560 d167280 from
git://anongit.freedesktop.org/xorg/driver/xf86-video-intel
libva: tag libva-1.7.0.pre1 35f1447 from
git://git.freedesktop.org/git/vaapi/libva
vaapi-intel-driver: tag 1.7.0.pre1 ab8e4e3 from
git://anongit.freedesktop.org/vaapi/intel-driver
IGT 1.14 364d378 from
http://anongit.freedesktop.org/git/xorg/app/intel-gpu-tools.git

External screen: Asus PB238Q

Steps:
------
1. Shutdown
2. Unplug external screen
3. Power on
4. Wait a moment
5. Hotplug HDMI cable

Actual result:
--------------
5. Screen turns on and displays "HDMI no signal" and turns off

Expected result:
----------------
5. Display works when hot-pluging screen after boot

Info:
-----
DUT is responding via SSH
Not reproduced when booting with the screen connected
Comment 1 cprigent 2016-03-17 14:51:44 UTC 
Reproduced with following steps:
1. Boot with screen connected, execute command "cat /proc/asound/card*/eld"
2. Execute command: "udevadm monitor"
3. Unplug HDMI cable
4. Plug it again, execute command "cat /proc/asound/card*/eld"

Actual result:
--------------
1.
$ cat /proc/asound/card*/eld*
monitor_present         1
eld_valid               1
monitor_name            ASUS PB238
connection_type         HDMI
eld_version             [0x2] CEA-861D or below
edid_version            [0x3] CEA-861-B, C or D
manufacture_id          0x6904
product_id              0x23a2
port_id                 0x0
support_hdcp            0
support_ai              0
audio_sync_delay        0
speakers                [0x1] FL/FR
sad_count               1
sad0_coding_type        [0x1] LPCM
sad0_channels           2
sad0_rates              [0x4e0] 32000 44100 48000 96000
sad0_bits               [0xe0000] 16 20 24
monitor_present         0
eld_valid               0
3.
$ udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[97.764995] change   /devices/pci0000:00/0000:00:02.0/drm/card0 (drm)
UDEV  [97.768234] change   /devices/pci0000:00/0000:00:02.0/drm/card0 (drm)

4. "udevadm monitor" does not output any log
$ cat /proc/asound/card*/eld*
monitor_present         0
eld_valid               0
monitor_present         0
eld_valid               0
Screen stays off
Comment 2 Ville Syrjala 2016-03-17 14:59:03 UTC 
HPD doesn't work when the display power well is down.

*** This bug has been marked as a duplicate of bug 89008 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.