[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160323075145.GA4216@eudyptula.hq.kempniu.pl>
Date: Wed, 23 Mar 2016 08:51:45 +0100
From: Michał Kępień <kernel@...pniu.pl>
To: Jonathan Woithe <jwoithe@...t42.net>
Cc: Darren Hart <dvhart@...radead.org>,
platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] fujitsu-laptop: Support radio LED
> > If you could let me know how you went about
> > acquiring the values on your machine I could try the exact same steps on the
> > S7020 to see what we get.
>
> The BTNI value is printed to the kernel log buffer by
> acpi_fujitsu_hotkey_add(), so all it takes to retrieve it is:
>
> dmesg | grep BTNI
>
I forgot to write that the other value I suggested could perhaps be used
to determine whether a radio toggle button is present on a given model
(0x00020320 on a Lifebook E744) is the return value of:
call_fext_func(FUNC_RFKILL, 0x0, 0x0, 0x0);
It is stored in the rfkill_supported field of struct fujitsu_hotkey_t.
You can also look it up in a DSDT dump. On a Lifebook E744:
Method (S000, 3, Serialized)
{
Name (_T_0, Zero) // _T_x: Emitted by ASL Compiler
Local0 = Zero
While (One)
{
_T_0 = Arg0
If ((_T_0 == Zero))
{
>> Local0 |= 0x00020000
Local0 |= 0x0200
Local0 |= 0x0100
Local0 |= 0x20
}
...
Break
}
Return (Local0)
}
On an E8420:
Method (S000, 3, NotSerialized)
{
Local0 = 0x80000000
If ((Arg0 == 0x00))
{
Local0 = Zero
Local0 |= 0x20
Local0 |= 0x0100
Local0 |= 0x0200
}
...
Return (Local0)
}
--
Best regards,
Michał Kępień
Powered by blists - more mailing lists