From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Richter <thor@math.tu-berlin.de>
Subject: Re: Partial success - Fixing resume from s2ram on S6010
Date: Mon, 09 Jun 2014 20:41:24 +0200
Message-ID: <5395FFD4.9010302@math.tu-berlin.de>
References: <5394EE4E.3040402@rus.uni-stuttgart.de>
 <1402296430-5065-1-git-send-email-chris@chris-wilson.co.uk>
 <20140609083025.GL27580@intel.com>
 <28223_1402303866_5395757A_28223_3428_1_20140609085045.GE16767@nuc-i3427.alporthouse.com>
 <5395932A.5080904@math.tu-berlin.de>
 <28223_1402312148_539595D3_28223_4884_1_20140609110857.GM27580@intel.com>
 <53959852.4000504@math.tu-berlin.de>
 <2086_1402313568_53959B5F_2086_895_1_20140609113155.GN27580@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <intel-gfx-bounces@lists.freedesktop.org>
Received: from charon.rus.uni-stuttgart.de (charon.rus.uni-stuttgart.de
 [129.69.192.1])
 by gabe.freedesktop.org (Postfix) with ESMTP id E1CD76E5D0
 for <intel-gfx@lists.freedesktop.org>; Mon,  9 Jun 2014 11:41:31 -0700 (PDT)
In-Reply-To: <2086_1402313568_53959B5F_2086_895_1_20140609113155.GN27580@intel.com>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/intel-gfx>,
 <mailto:intel-gfx-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/intel-gfx>
List-Post: <mailto:intel-gfx@lists.freedesktop.org>
List-Help: <mailto:intel-gfx-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/intel-gfx>,
 <mailto:intel-gfx-request@lists.freedesktop.org?subject=subscribe>
Errors-To: intel-gfx-bounces@lists.freedesktop.org
Sender: "Intel-gfx" <intel-gfx-bounces@lists.freedesktop.org>
To: =?ISO-8859-1?Q?Ville_Syrj=E4l=E4?= <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
List-Id: intel-gfx@lists.freedesktop.org

Hi Ville, dear Intel experts,

more on the partial resume from suspend for the S6010. It seems that the 
culprit is really the lack of a proper
initialization of the DVO. The minimum sequence to restore the display 
does not require to modify the 830 registers
directly, but rather needs to setup the DVO.

xrandr --output DVI1 --mode 640x480
# without this, access to the DVO is blocked, thus
# all the following fails. The above initializes the
# PLLs such that the DVO can be accessed.

modprobe i2c-hid
modprobe i2c-algo-bit
modprobe i2c-dev
modprobe i2c-scmi
modprobe i2c-i801
modprobe i2c-ismt
modprobe i2c-gpio
modprobe i2c-piix4
modprobe i2c-isch
modprobe i2c-mux
modprobe i2c-core

#
# Only the following two are required.
i2cset -y 5 0x38 0x34 0x02
i2cset -y 5 0x38 0x35 0x7f

# This restores the old resolution.
xrandr --output DVI1 --mode 1024x768

Thus, it really seems that the culprit is here that the resume operation 
does
not provide access to the DVO correctly.

Greetings,
     Thomas