From mboxrd@z Thu Jan  1 00:00:00 1970
From: Carsten Emde <C.Emde@osadl.org>
Subject: Re: [PATCH 1/2] drm/i915: clear up backlight inversion
 confusion on gen4
Date: Mon, 23 Apr 2012 17:06:53 +0200
Message-ID: <4F95700D.9080609@osadl.org>
References: <1335173535-14811-1-git-send-email-daniel.vetter@ffwll.ch>
	<4F9542EF.3010208@osadl.org>
	<20120423123257.GE4935@phenom.ffwll.local>
	<20120423123619.GF4935@phenom.ffwll.local>
	<4F9555D6.2020708@osadl.org>
	<20120423133934.GG4935@phenom.ffwll.local>
	<4F956077.3040103@osadl.org>
	<20120423142205.GI4935@phenom.ffwll.local>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org>
Received: from toro.web-alm.net (toro.web-alm.net [62.245.132.31])
	by gabe.freedesktop.org (Postfix) with ESMTP id 473629E779
	for <intel-gfx@lists.freedesktop.org>;
	Mon, 23 Apr 2012 08:13:16 -0700 (PDT)
In-Reply-To: <20120423142205.GI4935@phenom.ffwll.local>
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>
Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
List-Id: intel-gfx@lists.freedesktop.org

On 04/23/2012 04:22 PM, Daniel Vetter wrote:
> On Mon, Apr 23, 2012 at 04:00:23PM +0200, Carsten Emde wrote:
>> # intel_reg_write 0x61250 0x80000000
>> Value before: 0xE0000000
>> Value after: 0x80000000
>> # intel_reg_read 0x61254
>> 0x61254 : 0xB4A0B4A
>>
>> # intel_reg_write 0x61250 0xa0000000
>> Value before: 0x80000000
>> Value after: 0xA0000000
>> # intel_reg_read 0x61254
>> 0x61254 : 0xB4A0B4A
>>
>> # intel_reg_write 0x61250 0x90000000
>> Value before: 0xA0000000
>> Value after: 0x90000000
>> # intel_reg_read 0x61254
>> 0x61254 : 0xB4A0B4A
>>
>> # intel_reg_write 0x61250 0xb0000000
>> Value before: 0x90000000
>> Value after: 0xB0000000
>> # intel_reg_read 0x61254
>> 0x61254 : 0xB4A0B4A
>>
>> Not much.
>
> The idea was to boot with kms and see whether any of these values would
> restore the backlight. Writing to CTL1 should change anything in CTL2.
Ah, sorry, ok. Removed the quirk again and tested the various settings:

-> Initial screen: dark

# intel_reg_write 0x61250 0x80000000
Value before: 0xE0000000
Value after: 0x80000000
-> Still dark

# intel_reg_write 0x61250 0xa0000000
Value before: 0x80000000
Value after: 0xA0000000
-> Still dark

# intel_reg_write 0x61250 0x90000000
Value before: 0xA0000000
Value after: 0x90000000
-> BACKLIGHT ON!

# intel_reg_write 0x61250 0xb0000000
Value before: 0x90000000
Value after: 0xB0000000
-> Still ON.

	-Carsten.