Bug 94419

Summary: [APL] HDMI and DP pixel_clocks are always 25.2MHz on different resolutions
Product: DRI Reporter: Lu, Han <han.lu>
Component: DRM/IntelAssignee: Libin Yang <libin.yang>
Status: CLOSED FIXED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: critical    
Priority: highest CC: han.lu, intel-gfx-bugs, libin.yang, przanoni
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: BXT i915 features: display/HDMI
Attachments:
Description Flags
dmesg with drm.debug=0xe none

Description Lu, Han 2016-03-07 01:40:55 UTC 
At different display resolution such as 1920x1080, 1280x720, the pixel_clock is always 25.2 MHz.

Reproduce Steps
==============
1. connect DP or HDMI cable to monitor
2. run $ intel_audio_dump | grep AUD_CONFIG, check the pixel_clock
3. change to other resolutions such as 1920x1080, 1280x720, and check the pixel_clock

Expected Result
=============
The pixel_clock changes at different resolution. For example, 148.5 MHz at 1920x1080, 74.25 MHz at 1280x720, etc.

Actual Result
===========
The pixel_clock is always 25.2 MHz

System Environment
=======
linux OS version: Ubuntu 15.10
CRB: Apollo Lake RVP1a FabA
Platform: Apollo Lake Platform
BIOS:APLKRVPA.X86.119.R10.1601031622
Tree: git://anongit.freedesktop.org/drm-intel
Branch: drm-intel-nightly
Commit: 60803e27ae17d7e853c7872c5574f9380b902a57
Comment 1 Paulo Zanoni 2016-03-08 18:40:19 UTC 
Please boot with drm.debug=0xe, reproduce the bug, then attach the dmesg output
here.

Do the modes actually work? Does xrandr report the expected value? Have you tried using intel_reg read to check the real register values?

Maybe this is a problem with intel_audio_dump?
Comment 2 Libin Yang 2016-03-10 07:32:11 UTC 
The dmesg is too long. I will upload the dmesg as a file
Comment 3 Libin Yang 2016-03-10 07:33:29 UTC 
Created attachment 122195 [details]
dmesg with drm.debug=0xe
Comment 4 cprigent 2016-03-26 17:53:09 UTC 
Libin Yang, Lu Han,
Could you answer to the questions from Paulo. Then reassign it to him.
Thanks.
Comment 5 Lu, Han 2016-03-28 10:35:54 UTC 
The issue is fixed after upgrade APL and apply the LSPCON patches. After upstream the LSPCON patches, the issue can be closed.
Comment 6 Lu, Han 2016-03-29 04:16:22 UTC 
The issue is fixed without applying the LSPCON patch, so close it.

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.