Summary: | [BXT-P] hotplug is not working on HDMI | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Humberto Israel Perez Rodriguez <humberto.i.perez.rodriguez> | ||||||
Component: | DRM/Intel | Assignee: | Humberto Israel Perez Rodriguez <humberto.i.perez.rodriguez> | ||||||
Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||
Severity: | normal | ||||||||
Priority: | medium | CC: | intel-gfx-bugs | ||||||
Version: | XOrg git | ||||||||
Hardware: | x86-64 (AMD64) | ||||||||
OS: | Linux (All) | ||||||||
Whiteboard: | |||||||||
i915 platform: | BXT | i915 features: | display/HDMI, display/LSPCON | ||||||
Attachments: |
|
Description
Humberto Israel Perez Rodriguez
2016-06-15 17:07:35 UTC
the command : $ udevadm monitor does not shows any hotplug events DP is hotplug/hotunplug capable I assume you connect the HDMI display via the DDI0 HDMI plug. In that case it's expected that HDMI won't work if it's not connected when booting, since the driver is missing LSPCON support. If the display is connected BIOS will configure LSPCON. An HDMI display connected to the DDI1 DP++ port via a type 1 HDMI dongle should work fine. Hot plug is now working for me on APL with the following config: Software information ============================================ Kernel version : 4.7.0-rc5-nightly+ Linux distribution : Ubuntu 16.04 LTS Architecture : 64-bit Mesa version : 11.2.2 (git-3a9f628 xf86-video-intel version : 2.99.917 Xorg-Xserver version : 1.18.99.1 DRM version : 2.4.68 VAAPI version : Intel i965 driver for Intel(R) Broxton - 1.7.2.pre1 (1.7.0-53-gbcde10d) Cairo version : 1.15.2 Intel GPU Tools version : Tag [intel-gpu-tools-1.15-87-g376b813] / Commit [376b813] Kernel driver in use : i915 Hardware acceleration : Enabled Bios revision : 144.10 KSC revision : 1.15 Hardware information ============================================ Platform : BXT-P Motherboard model : Broxton P Fab 2 GPU Card : Intel Corporation Device 5a84 (rev 0a) (prog-if 00 [VGA controller]) Memory ram : 8 GB CPU's number : 4 Firmwares information ============================================ DMC version : 1.7 GUC version found : 8.7 Please try https://patchwork.freedesktop.org/series/8024/ on top of drm-intel-nightly branch of http://cgit.freedesktop.org/drm-intel Please test with latest -nightly it has LSPCON support. Humberto can you please try again with latest lightly Created attachment 129877 [details]
attachment-13591-0.html
I will be out speaking at the Emebdedd Linux Conference North America 2017 from 02/21 to 02/23 with limited email access.
Regards
Manasi
wit the commercial APL this issue does not happen anymore ====================================== Software ====================================== kernel version : 4.10.2-mainline-ww12-version-4.10.2 architecture : x86_64 os version : Ubuntu 16.10 os codename : yakkety bios revision : 5.6 bios release date : 11/08/2016 ksc : 13.0 ====================================== Graphic drivers ====================================== mesa : 17.0.1 (git-8fee1d3 modesetting : modesetting_drv.so xorg-xserver : 1.18.4 libdrm : 2.4.75 cairo : 1.15.4 xserver : X.Org X Server 1.19.2 intel-gpu-tools (tag) : intel-gpu-tools-1.18 intel-gpu-tools (commit) : bb97a05 ====================================== Hardware ====================================== motherboard model : NUC6CAYS motherboard id : NUC6CAYB form factor : Desktop manufacturer : Intelcorporation cpu family : Celeron cpu family id : 6 cpu information : Intel(R) Celeron(R) CPU J3455 @ 1.50GHz gpu card : Intel Corporation Device 5a85 (rev 0b) (prog-if 00 [VGA controller]) max memory ram : 16 GB display resolution : 5760x2160 cpu thread : 4 cpu core : 4 cpu model : 92 cpu stepping : 9 socket : Other signature : Type 0, Family 6, Model 92, Stepping 9 hard drive : 55GiB (60GB) ====================================== Firmware ====================================== dmc fw loaded : yes dmc version : 1.7 guc fw loaded : NONE guc version wanted : 8.7 guc version found : 0.0 closing this bug |
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.