Re: Brightness and "touchpad dis-/enable" keys not working for Fujitsu e7x6

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Jan-Marek

On Tue, Jun 14, 2016 at 10:48:32AM +0200, Jan-Marek Glogowski wrote:
> I recently got new Skylake hardware (e7x6) from Fujitsu. Compared to
> previous Haswell generation (e7x4), some of the Fn+X key combination
> stopped working. This includes the brightness and "touchpad dis-/enable"
> key combinations.
> 
> For the brightness control it's understandable, as this was handled by a
> ACPI device FUJ02B1, which is no longer available.

I see.  Perhaps they've rolled this functionality into FUJ02E3 (which
previously has handled everything except brightness control).

> I don't know how the touchpad disable key was actually working, as I don't
> get any scan codes or ACPI events in userspace - probably I'm missing
> something here.

Maybe on the previous hardware generation the touchpad keys were controlled
solely in hardware, and for some reason they've moved them to software in
the latest generation.

> I compiled the git fujitsu-notebook driver ...

I assume this was "fujitsu-laptop".

> ... can see ACPI notifications when any of the non-working combination is
> pressed like:
> 
> [  408.997023] FUJ02B1: call_fext_func: FUNC 0x1000 (args 0x4, 0x0, 0x0)
> returned 0x100
> [  408.997072] FUJ02B1: call_fext_func: FUNC 0x1002 (args 0x1, 0x0, 0x0)
> returned 0x0
> 
> so these button states seems to be handled differently then all the
> other buttons. (FUNC 0x1002 is used to check the special button states).

For clarity, which buttons are the "non-working combinations"?  Is it just
the brightness/touchpad buttons, or are there others which are behaving
similarly?

> BTW: the debug message is a little misleading, as all of them are prefixed
> 'FUJ02B1', even if the ACPI event is handled by the FUJ02E3 device.

Yes, good point.  The use of "FUJ02B1" (via ACPI_FUJITSU_HID) would have
been for convenience and possibly dates from before FUJ02E3 support was
included in the driver.  A case can certainly be made for a more generic
descriptor.

> I checked the DSTD from the old and new HW. The size has more then
> duplicated (414k => 955k) with a 43k diff. The diff for the FUJ02E3
> device is just 356 lines, but I couldn't identify anything, which might
> relate to the keys.

Perhaps they've introduced a new backlight control device with a different
HID (except you mentioned that only FUJ02E3 was listed even on other OSes,
so I guess this is unlikely).

> Any help would be appreciated to get this fixed.

I don't have access to any of the newer Fujitsu hardware so I can't do much
in relation to debugging the problem.  Obviously the buttons concerned
generate ACPI notifications.  Without a FUJ02B1 and any obvious extension 
to FUJ02E3, my only thought at present is that they've taken backlight
control out of ACPI (that is, based on the ACPI button notification they
poke other hardware to effect the brightness control).  It does seem a bit
odd though.

In any case, we'd have to identify what is meant to be done (and what is
done under other OSes) in reponse to these buttons.

I assume that the brightness buttons don't do anything when fujitsu-laptop
is unloaded?  I'm wondering whether the standard backlight driver might be
operational on this hardware.

Regards
  jonathan
--
To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Kernel Development]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux