From mboxrd@z Thu Jan 1 00:00:00 1970 From: Darren Hart Subject: Re: Dell Vostro V131 hotkeys revisited Date: Wed, 9 Sep 2015 21:38:12 -0700 Message-ID: <20150910043812.GB108260@vmdeb7> References: <20150623112621.GA3071@eudyptula.hq.kempniu.pl> <20150701105544.GD17577@pali> <20150702204122.GA2610@eudyptula.hq.kempniu.pl> <201507022258.32104@pali> <20150703065244.GA2401@eudyptula.hq.kempniu.pl> <20150703074813.GD1841@pali> <559C1C17.3060009@dell.com> <20150708035346.GB2413@eudyptula.hq.kempniu.pl> <20150722073513.GA2381@eudyptula.hq.kempniu.pl> <20150831095107.GA2397@eudyptula.hq.kempniu.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from bombadil.infradead.org ([198.137.202.9]:48490 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750843AbbIJEiQ (ORCPT ); Thu, 10 Sep 2015 00:38:16 -0400 Content-Disposition: inline In-Reply-To: <20150831095107.GA2397@eudyptula.hq.kempniu.pl> Sender: platform-driver-x86-owner@vger.kernel.org List-ID: To: =?utf-8?B?TWljaGHFgiBLxJlwaWXFhA==?= Cc: Mario Limonciello , Pali =?iso-8859-1?Q?Roh=E1r?= , "Gowda, Srinivas G" , "Brown, Michael E" , "Warzecha, Douglas" , Matthew Garrett , "Kabir, Rezwanul" , Alex Hung , "platform-driver-x86@vger.kernel.org" On Mon, Aug 31, 2015 at 11:51:07AM +0200, Micha=C5=82 K=C4=99pie=C5=84 = wrote: > > > > Now as for actually simulating a keypress, it can be programmed= using > > > > the following calling interface (on receiving the e025 WMI noti= fication). > > > > To actually simulate the keypress: > > > > Arg1=3D0x41 > > > > 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 > > >=20 > > > And is it possible to disable keypress simulation on systems that= have > > > that capability? > > >=20 > > > My understanding is that all hardware equipped with an Instant La= unch > > > button is capable of generating a WMI event upon its press, but n= ot 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 (probab= ly in > > > dell-laptop.c) no i8042 interrupt is raised when the Instant Laun= ch > > > button is pressed. Though that would still leave us with the ques= tion of > > > how to determine (ideally without side effects) whether a given m= odel > > > needs disabling keypress simulation. I imagine the pseudocode wou= ld be > > > like: > > >=20 > > > if (ec_can_simulate_keypresses) > > > disable_keypress_simulation(); > > > else > > > enable_wmi_event_generation(); > > >=20 > > > If disabling keypress simulation is not possible, dell-wmi.c has = to > > > somehow determine whether a 0xe025 WMI event should be ignored or= not. > > >=20 > > > Am I making any sense here? >=20 > As the holiday season is coming to an end, I'm taking my last shot at > reviving this thread. Could anyone please tell us: >=20 > * Is there a way to determine whether the EC is capable of simulati= ng > keypresses without the side effects that the SMBIOS call 4, 11 wi= th > argument 64 causes on certain hardware (e.g. disabling keyboard > backlight on an E6440)? Or is there perhaps a well-defined list o= f > machines that SMBIOS call is (un)safe on? >=20 > * Is it possible to disable keypress simulation on machines on whic= h > 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. Doe= s anyone from Dell on Cc have documentation they can share to help answer these questions? --=20 Darren Hart Intel Open Source Technology Center