From: "Pali Rohár" <pali.rohar@gmail.com>
To: Renato Soma <renatoys08@gmail.com>
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
Mario Limonciello <mario.limonciello@dell.com>
Subject: Re: [PATCH 0/1] platform/x86: dell-wmi: Uncomment events that were
Date: Sat, 16 Mar 2019 10:17:56 +0100 [thread overview]
Message-ID: <20190316091756.2zfccpnhfnjogktp@pali> (raw)
In-Reply-To: <20190316010942.6448-1-renatoys08@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1646 bytes --]
On Friday 15 March 2019 22:09:41 Renato Soma wrote:
> Hello,
>
> I noted that by pressing the "Dell Audio with Preset Switch" on my Dell
> 5420, notification messages are displayed at dmesg.
> That is happening because the keys are commented out and marked as
> untested.
> Since the logs purpose are there only for notification and considering
> the history of cases similar to this one, this patch aims to ignore
> those logs. Furthermore, this patch fixes the comments related to the
> keys, since they are marked as "Windows Mobility Center" button, which
> is incorrect.
>
> Do note that the event 0xe02a is generated when pushing the button and
> the event 0xe02b is generated when releasing the button, hence the
> comment on the code.
>
> Finally, as explained earlier, this was tested on an Inspiron 5420, but
> this model shares the specifications of the Inspiron 7520.
>
> Thanks,
> Renato
>
> Renato Soma (1):
> platform/x86: dell-wmi: Uncomment events that were untested
>
> drivers/platform/x86/dell-wmi.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
Hello!
Looks like that those keys are not as obvious as you wrote. Look at my
email with some investigation about Dell Audio With Preset Switch key:
https://www.spinics.net/lists/platform-driver-x86/msg15593.html
Also there is another user who wrote about 0xe02c key generated by
Inspirion 7520: https://ubuntuforum-br.org/index.php?topic=105434.0
You can a testing machine 5420, can you prove that behavior described in
my previous email match also your machine?
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next parent reply other threads:[~2019-03-16 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190316010942.6448-1-renatoys08@gmail.com>
2019-03-16 9:17 ` Pali Rohár [this message]
2019-03-17 18:30 ` Renato Soma
2019-03-18 12:00 ` Pali Rohár
2019-03-19 2:21 ` Renato Soma
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=20190316091756.2zfccpnhfnjogktp@pali \
--to=pali.rohar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@dell.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=renatoys08@gmail.com \
/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
all inboxes | Powered by JetHome®