From: Darren Hart <dvhart@infradead.org>
To: "Michał Kępień" <kernel@kempniu.pl>
Cc: "Mario Limonciello" <mario_limonciello@dell.com>,
"Pali Rohár" <pali.rohar@gmail.com>,
"Gowda, Srinivas G" <Srinivas_G_Gowda@dell.com>,
"Brown, Michael E" <Michael_E_Brown@dell.com>,
"Warzecha, Douglas" <Douglas_Warzecha@dell.com>,
"Matthew Garrett" <mjg@redhat.com>,
"Kabir, Rezwanul" <Rezwanul_Kabir@dell.com>,
"Alex Hung" <alex.hung@canonical.com>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>
Subject: Re: Dell Vostro V131 hotkeys revisited
Date: Wed, 9 Sep 2015 21:38:12 -0700 [thread overview]
Message-ID: <20150910043812.GB108260@vmdeb7> (raw)
In-Reply-To: <20150831095107.GA2397@eudyptula.hq.kempniu.pl>
On Mon, Aug 31, 2015 at 11:51:07AM +0200, Michał Kępień wrote:
> > > > Now as for actually simulating a keypress, it can be programmed using
> > > > the following calling interface (on receiving the e025 WMI notification).
> > > > To actually simulate the keypress:
> > > > Arg1=0x41
> > > > Arg2 Byte [1:0]: Scan code to simulate
> > > > Byte [3:2]
> > > > * Bit0 - L Alt
> > > > * Bit1 - R Alt
> > > > * Bit2 - L Ctrl
> > > > * Bit3 - R Ctrl
> > > > * Bit4 - L Shift
> > > > * Bit5 - R shift
> > > > * Bit6 - L Win
> > > > * Bit7 - R Win
> > > > * Bit8 - Fn key
> > >
> > > And is it possible to disable keypress simulation on systems that have
> > > that capability?
> > >
> > > My understanding is that all hardware equipped with an Instant Launch
> > > button is capable of generating a WMI event upon its press, but not all
> > > models can generate a keypress at the same time, correct? If that's the
> > > case, then the arguably cleanest solution would be to change the keymap
> > > entry for event 0xe025 in dell-wmi.c to KE_KEY and ensure (probably in
> > > dell-laptop.c) no i8042 interrupt is raised when the Instant Launch
> > > button is pressed. Though that would still leave us with the question of
> > > how to determine (ideally without side effects) whether a given model
> > > needs disabling keypress simulation. I imagine the pseudocode would be
> > > like:
> > >
> > > if (ec_can_simulate_keypresses)
> > > disable_keypress_simulation();
> > > else
> > > enable_wmi_event_generation();
> > >
> > > If disabling keypress simulation is not possible, dell-wmi.c has to
> > > somehow determine whether a 0xe025 WMI event should be ignored or not.
> > >
> > > Am I making any sense here?
>
> As the holiday season is coming to an end, I'm taking my last shot at
> reviving this thread. Could anyone please tell us:
>
> * Is there a way to determine whether the EC is capable of simulating
> keypresses without the side effects that the SMBIOS call 4, 11 with
> argument 64 causes on certain hardware (e.g. disabling keyboard
> backlight on an E6440)? Or is there perhaps a well-defined list of
> machines that SMBIOS call is (un)safe on?
>
> * Is it possible to disable keypress simulation on machines on which
> the EC supports it? If so, how would one do that?
I certainly don't know myself, not what you were hoping to hear back I'm sure.
Some of that requires documentation, which I don't know if we have. Does anyone
from Dell on Cc have documentation they can share to help answer these
questions?
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2015-09-10 4:38 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 11:26 Dell Vostro V131 hotkeys revisited Michał Kępień
2015-06-23 11:46 ` Pali Rohár
2015-06-23 19:40 ` Michał Kępień
2015-06-23 19:47 ` Pali Rohár
2015-06-24 11:18 ` Michał Kępień
2015-06-24 13:23 ` Pali Rohár
2015-06-25 9:02 ` Michał Kępień
2015-06-27 18:50 ` Pali Rohár
2015-06-30 7:38 ` Michał Kępień
2015-06-30 8:00 ` Pali Rohár
2015-07-01 8:32 ` Michał Kępień
2015-07-01 8:40 ` Pali Rohár
2015-07-01 10:11 ` Michał Kępień
2015-07-01 10:55 ` Pali Rohár
2015-07-02 20:41 ` Michał Kępień
2015-07-02 20:58 ` Pali Rohár
2015-07-03 6:52 ` Michał Kępień
2015-07-03 7:48 ` Pali Rohár
2015-07-03 11:26 ` Michał Kępień
2015-07-03 11:43 ` Pali Rohár
2015-07-03 13:23 ` Michał Kępień
2015-07-03 13:32 ` Pali Rohár
2015-07-03 13:50 ` Michał Kępień
2015-07-03 14:09 ` Pali Rohár
2015-07-03 14:14 ` Pali Rohár
2015-07-03 18:22 ` Gabriele Mazzotta
2015-07-03 20:07 ` Michał Kępień
2015-07-03 20:30 ` Gabriele Mazzotta
2015-07-04 19:41 ` Pali Rohár
2015-07-04 20:34 ` Gabriele Mazzotta
2015-07-03 20:55 ` Michał Kępień
2015-07-04 19:13 ` Pali Rohár
2015-07-04 19:47 ` Pali Rohár
2015-07-27 19:27 ` Michał Kępień
2015-07-07 18:36 ` Mario Limonciello
2015-07-07 21:01 ` Pali Rohár
2015-07-08 3:21 ` Michał Kępień
2015-07-08 3:53 ` Michał Kępień
2015-07-22 7:35 ` Michał Kępień
2015-08-31 9:51 ` Michał Kępień
2015-09-10 4:38 ` Darren Hart [this message]
2015-11-13 10:17 ` Michał Kępień
2015-12-07 11:43 ` Pali Rohár
2015-12-16 9:05 ` Michał Kępień
2015-12-16 9:30 ` Pali Rohár
2015-12-16 10:29 ` Hans de Goede
2015-12-17 8:05 ` Michał Kępień
2015-12-17 9:48 ` Hans de Goede
2015-12-17 18:47 ` Pali Rohár
2015-12-17 18:54 ` Hans de Goede
2015-12-19 0:02 ` Darren Hart
2015-12-19 9:59 ` Pali Rohár
2015-12-18 7:10 ` Michał Kępień
2015-12-18 10:44 ` Hans de Goede
2015-12-19 12:31 ` Michał Kępień
2015-07-04 21:24 ` Pali Rohár
2015-07-05 4:51 ` Michał Kępień
2015-06-23 12:18 ` Pali Rohár
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=20150910043812.GB108260@vmdeb7 \
--to=dvhart@infradead.org \
--cc=Douglas_Warzecha@dell.com \
--cc=Michael_E_Brown@dell.com \
--cc=Rezwanul_Kabir@dell.com \
--cc=Srinivas_G_Gowda@dell.com \
--cc=alex.hung@canonical.com \
--cc=kernel@kempniu.pl \
--cc=mario_limonciello@dell.com \
--cc=mjg@redhat.com \
--cc=pali.rohar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox