All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mattia Dongili <malattia@linux.it>
To: "Marco Krüger" <krgsch@gmail.com>
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: sony-laptop crash (Sony VPC SE 1V9E) for 3.8.0+
Date: Fri, 9 Aug 2013 07:17:42 +0900	[thread overview]
Message-ID: <20130808221742.GA27435@kamineko.org> (raw)
In-Reply-To: <51FEF199.7050800@gmail.com>

[Resending as I don't see this mail on the list nor on online archives]

Hi Marco.

On Mon, Aug 05, 2013 at 02:28:09AM +0200, Marco Krüger wrote:
> Am 05.08.2013 00:14, schrieb Mattia Dongili:
...
> >case 0x0143:
> >case 0x014b:
> >
> >Could you send your DSDT?
> My DSDT in raw/decompiled format.


You have two essentially very similar methods to control backlight
(screen, keyboard and ambient light sensor): F143 and F14B.
I should probably fix the code to handle one such situation but have you
by any chance checked if there is a BIOS update that fixes this mess?

For the record, only this bit seems different:

	If (LEqual (BUF1, 0x40))
	{
	    Store (0x40, P80H)
	    Store (BUF2, Local0)
-	    And (Local0, One, Local0)
+	    And (Local0, 0x03, Local0)
	    Store (Local0, ^^H_EC.KLPC)
	}

but we never call into this method with anything other than 0x1 or 0x0
in BUF2 so it won't make any difference at the moment which one we use.

Still it would be interesting to know what happens with 0x2 or 0x3. Do
you remember what states you could set in Windows for the keyboard
backlight?

Thanks
-- 
mattia
:wq!

  reply	other threads:[~2013-08-08 22:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-04 10:38 sony-laptop crash (Sony VPC SE 1V9E) for 3.8.0+ Marco Krüger
2013-08-04 22:14 ` Mattia Dongili
2013-08-05  0:28   ` Marco Krüger
2013-08-08 22:17     ` Mattia Dongili [this message]
2013-08-09 13:35       ` Marco Krüger
2013-09-21 21:39       ` Marco Krüger
2013-09-22  3:10         ` Mattia Dongili
2013-09-22  6:47           ` Marco Krüger
2013-09-22  7:55             ` Mattia Dongili
2013-09-22  9:07               ` Marco Krüger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130808221742.GA27435@kamineko.org \
    --to=malattia@linux.it \
    --cc=krgsch@gmail.com \
    --cc=platform-driver-x86@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.