Created attachment 132980 [details] dmesgS3 ==Bug detailed description== -------------------------------------------------- Mipi screen gets blank screen after resuming from S3 state ==Steps to reproduce== -------------------------------------------------- # echo mem > /sys/power/state Resume system ==Actual results== -------------------------------------------------- Mipi screen gets blank screen after resuming from S3 state ==Expected results== -------------------------------------------------- displays should resume with no corruption nor any kind of failures ==Hardware configuration== -------------------------------------------------- CPU Name : Genuine Intel(R) CPU @ 1.10GHz (family: 6, model: 122) 4 cores Graphic: Intel Corporation Device 3184 (rev 01) prog-if 00 VGA controller RVP SKU : GLK RVP1 SOC : GML A1 Soc QDF : Ql9R Reworks : F23 Display: MIPI AUO 10.1" 1920x1200 Non-Touch MIPI Kit - B101UAN01.7 ==Software configuration== -------------------------------------------------- kernel version : 4.13.0-rc2-mipi-july-25-2-g92845e5-dirty architecture : x86_64 os version : Ubuntu 17.04 bios revision : 53.51 ksc : 1.36 swap partition : enabled on (/dev/sda2) ====================================== Graphic drivers ====================================== modesetting : enabled modesetting compiled for : 1.19.3 X.Org Video Driver xorg-xserver : 1.19.3 intel-gpu-tools : 1.17-1 ==kernel configuration== -------------------------------------------------- commit 92845e5dff13907ccebff6b9ae742e793ddc6a74 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Tue Jul 25 15:41:37 2017 +0100 drm-tip: 2017y-07m-25d-14h-41m-13s UTC integration manifest ==Attachments== -------------------------------------------------- dmesgS3 dmesgS4 ==Additional Info== -------------------------------------------------- MIPI screen works fine after resuming from S4. I am adding dmesgS4 too.
Created attachment 132981 [details] dmesgS4
This is a regression, this bug was also related to this issue: https://bugs.freedesktop.org/show_bug.cgi?id=100664
Adding tag into "Whiteboard" field - ReadyForDev *Status is correct *Platform is included *Feature is included *Priority and Severity correctly set *Logs included
Changing to Critical/High since is Feature failure w/o workaround always reproducible. Thanks.
It seems that GPIO requests fail here. Could you dump the ACPI table so see if the GPIO's are defined or not. Run acpidump > acpidump.out or more precisely, look for https://01.org/linux-acpi/utilities
Can you add Kernel config used for this testing??
Created attachment 133425 [details] config Adding config file.
Changing to REOPEN since information was provided.
Created attachment 133572 [details] [review] Use NULL for GPIO connection ID Could you try this Andy's GPIO patch on your end? On my GLK + MIPI/DSI setup the patch + latest drm-tip solved the GPIO request failures.
commit cd55a1fbd21a820b7dd85a208b3170aa0b06adfa Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Date: Thu Aug 17 13:55:41 2017 +0300 drm/i915/bxt: use NULL for GPIO connection ID in drm-tip now, please check again.
Resolving as in drm-tip. QA folks please verify.
Issue is still present in latest drm-tip kernel: commit ad6ab9f96437f0cb1f4d8a7840fd9eeb894eb12e Author: Gustavo Padovan <gustavo.padovan@collabora.com> Date: Fri Aug 18 15:26:42 2017 -0300 drm-tip: 2017y-08m-18d-18h-21m-46s UTC integration manifest Adding dmesg and acpidump
Created attachment 133621 [details] dmesg
Created attachment 133622 [details] acpidump
Mika? Wonder why the commit helps you but not Luis.
It is working now with latest drm-tip kernel and CONFIG_PINCTRL_GEMINILAKE=y. 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.