Looks like it didn't go to the thread... Fixing that. :)
---------- Forwarded message ---------
From: Daniel Turton <mistertwo@xxxxxxxxx>
Date: Mon, Mar 7, 2016 at 1:23 PM
Subject: Re: TP 460 Yoga tablet mode switch not supported
To: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx>
From: Daniel Turton <mistertwo@xxxxxxxxx>
Date: Mon, Mar 7, 2016 at 1:23 PM
Subject: Re: TP 460 Yoga tablet mode switch not supported
To: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx>
Hey Henrique,
Thanks for getting back with me. :) I've done some digging on my end, and I've found a few functions within the DSDT that appear to be of interest:
Method (_Q52, 0, NotSerialized) // _Qxx: EC Query
{
LIDS = HPLD /* \_SB_.PCI0.LPCB.H_EC.HPLD */
If (VIGD)
{
^^^GFX0.GLID (LIDS ())
}
If (IOST)
{
If (!ISOC (Zero))
{
IOST = Zero
^HKEY.MHKQ (0x60D0)
}
}
^HKEY.MHKQ (0x5002)
Notify (LID0, 0x80) // Status Change
}
Method (_Q53, 0, NotSerialized) // _Qxx: EC Query
{
LIDS = HPLD /* \_SB_.PCI0.LPCB.H_EC.HPLD */
If (VIGD)
{
^^^GFX0.GLID (LIDS ())
}
If ((IOEN && !IOST))
{
If (!ISOC (One))
{
IOST = One
^HKEY.MHKQ (0x60D0)
}
}
^HKEY.MHKQ (0x5001)
Notify (LID0, 0x80) // Status Change
}
The "IOST" field seems to hold what we're looking for, as far as the state of the screen in tablet mode. As for the trigger that was mentioned by the driver...
Method (_Q77, 0, NotSerialized) // _Qxx: EC Query
{
^HKEY.MHKQ (0x60C0)
If ((EMMS == Zero)) {}
Else
{
}
}
Not seeing where _Q77 is specifically being triggered though in the DSDT. I don't remember there being anything sensitive within the DSDT, but let me know if I'm clear to go ahead and attach the DSDT to a reply.
Thanks!
Daniel
On Sat, Feb 20, 2016 at 7:06 AM Henrique de Moraes Holschuh <hmh@xxxxxxxxxx> wrote:
On Fri, 19 Feb 2016, Daniel Turton wrote:
> I've recently picked up a Thinkpad 460 Yoga, and it appears that the tablet
> switch isn't supported just yet. "event 0x60c0" is repeated whether the
> screen is swung back or forward. Here's the debug output from syslog:
>
> Feb 14 22:29:52 DT-Yoga-14 kernel: [13921.288473] thinkpad_acpi: unknown
> possible thermal alarm or keyboard event received Feb 14 22:29:52
> DT-Yoga-14 kernel: [13921.288559] thinkpad_acpi: temperatures (Celsius): 47
> 37 43 47 47 0 41 37 Feb 14 22:29:52 DT-Yoga-14 kernel: [13921.288578]
> thinkpad_acpi: unhandled HKEY event 0x60c0 Feb 14 22:29:52 DT-Yoga-14
> kernel: [13921.288585] thinkpad_acpi: please report the conditions when
> this event happened to ibm-acpi-devel@xxxxxxxxxxxxxxxxxxxxx
>
> Let me know if anything else is needed, and how I can get started on
> submitting a patch to you.
It is necessary to locate in the ACPI tables the register that contains the
current mode. Event 0x60c0 only tells you that "it changed", so we need to
be able to know "to what"...
Hopefully, tracing in the ACPI DSDT and XSDT dumps for what sends event
0x60c0 will also show candidates of the method or register that can be used
to query the current state of the switch.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
_______________________________________________ ibm-acpi-devel mailing list ibm-acpi-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
