From: Marco Chiappero <marco@absence.it>
To: Norbert Preining <preining@logic.at>
Cc: Brad Campbell <lists2009@fnarfbargle.com>,
Mattia Dongili <malattia@linux.it>,
linux-acpi@vger.kernel.org,
platform-driver-x86 <platform-driver-x86@vger.kernel.org>
Subject: Re: sony-laptop on VAIO TT help request
Date: Fri, 01 Jul 2011 15:55:28 +0200 [thread overview]
Message-ID: <4E0DD1D0.7020605@absence.it> (raw)
In-Reply-To: <20110701095049.GE11959@gamma.logic.tuwien.ac.at>
Il 01/07/2011 11:50, Norbert Preining ha scritto:
> Hi Marco,
>
> On Fr, 01 Jul 2011, Marco Chiappero wrote:
>>>> http://www.absence.it/vaio-acpi/source/patches/
>>
>> could you please provide us your DSDT and the exact model string of your TT?
>
> I looked a bit through the patch and I see that it is restricted
> to MM and (forgotten the model number).
MM? What does it stand for?
> I have a VGN-Z11 which has
> also a turn on/off optical drive, a shock sensor etc.
This last one is interesting because, from the other DSTDs I have seen,
I suspect your notebook to have handle 0x0113, an handle that allows to
enable/disable an unknown feature, is it the HDD protection?
> (btw, I also take care for the sony-laptop-zseries variant of the
> kernel module where you can turn off and on the nvidia card,
> and also the led of the speed-stamina switch is controlled.
This is interesting too. Ok, let's not speak about the multiplexer
methods, let us speak about handle 0x0128, related to the Hybrid GFX
feature. I have never done a deep analysis, maybe you can help here.
First of all, newer VPCZ1 models come with a few more methods, dealing
with the screen brightness level, HSC5, HSC6, HSC7. Then:
- HSC0 returns the event reason (1 switch position change? what about
2,3,4?)
- HSC1 returns some state bits (what about their meaning?)
- HSC2, HSC3, HSC4?
Moreover:
Field (ECF2, ByteAcc, Lock, Preserve)
{
Offset (0xF1),
HPWR, 1, <-- ?
HLMX, 1, <-- ?
HCMM, 1, <-- ?
DLED, 1, <-- discrete GFX led
ILED, 1, <-- integr. GFX led
ALED, 1, <-- auto GFX led
Offset (0xF2),
SWPS, 1, <-- ?
HPOK, 1, <-- ?
HHPD, 1, <-- HDMI related
DHPD, 1, <-- DVI related
ATSW, 1 <-- auto switching related
}
What does handle 0x0128 aim to provide?
next prev parent reply other threads:[~2011-07-01 13:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 10:07 sony-laptop on VAIO TT help request Brad Campbell
2011-06-30 13:55 ` Mattia Dongili
2011-06-30 15:52 ` Brad Campbell
2011-07-01 9:46 ` Marco Chiappero
2011-07-01 9:50 ` Norbert Preining
2011-07-01 13:55 ` Marco Chiappero [this message]
2011-07-12 6:21 ` Norbert Preining
2011-07-13 22:11 ` Marco Chiappero
2011-07-13 22:50 ` Norbert Preining
2011-07-04 9:19 ` Brad Campbell
2011-07-04 11:11 ` Marco Chiappero
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=4E0DD1D0.7020605@absence.it \
--to=marco@absence.it \
--cc=linux-acpi@vger.kernel.org \
--cc=lists2009@fnarfbargle.com \
--cc=malattia@linux.it \
--cc=platform-driver-x86@vger.kernel.org \
--cc=preining@logic.at \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox