From: <Mario.Limonciello@dell.com>
To: <jerome.debretagne@gmail.com>
Cc: <platform-driver-x86@vger.kernel.org>, <dvhart@infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-acpi@vger.kernel.org>,
<rjw@rjwysocki.net>, <andy.shevchenko@gmail.com>,
<alex.hung@canonical.com>
Subject: RE: [PATCH] platform/x86: intel-hid: Power button suspend on Dell Latitude 7275
Date: Wed, 20 Sep 2017 20:07:41 +0000 [thread overview]
Message-ID: <c288f2dae8594a438e07aea67211a308@ausx13mpc120.AMER.DELL.COM> (raw)
In-Reply-To: <CA+kEDGGv3twZP4od16bPHjW8-S3PHs=SpQZEF1tqr5M4cBpzFQ@mail.gmail.com>
> -----Original Message-----
> From: Jérôme de Bretagne [mailto:jerome.debretagne@gmail.com]
> Sent: Monday, September 18, 2017 5:41 PM
> To: Limonciello, Mario <Mario_Limonciello@Dell.com>
> Cc: platform-driver-x86@vger.kernel.org; Darren Hart <dvhart@infradead.org>;
> LKML <linux-kernel@vger.kernel.org>; ACPI Devel Maling List <linux-
> acpi@vger.kernel.org>; Rafael J. Wysocki <rjw@rjwysocki.net>; Andy Shevchenko
> <andy.shevchenko@gmail.com>; Alex Hung <alex.hung@canonical.com>
> Subject: Re: [PATCH] platform/x86: intel-hid: Power button suspend on Dell
> Latitude 7275
>
> 2017-09-18 23:29 GMT+02:00 <Mario.Limonciello@dell.com>:
> >> -----Original Message-----
> >> From: Jérôme de Bretagne [mailto:jerome.debretagne@gmail.com]
> >> Sent: Sunday, September 17, 2017 5:57 PM
> >> To: platform-driver-x86@vger.kernel.org
> >> Cc: Darren Hart <dvhart@infradead.org>; LKML <linux-kernel@vger.kernel.org>;
> >> Linux ACPI <linux-acpi@vger.kernel.org>; Rafael J. Wysocki
> <rjw@rjwysocki.net>;
> >> Andy Shevchenko <andy.shevchenko@gmail.com>; Limonciello, Mario
> >> <Mario_Limonciello@Dell.com>; Alex Hung <alex.hung@canonical.com>
> >> Subject: [PATCH] platform/x86: intel-hid: Power button suspend on Dell Latitude
> >> 7275
> >>
> >> From: Jérôme de Bretagne <jerome.debretagne@gmail.com>
> >>
> >> On Dell Latitude 7275 the 5-button array is not exposed in the
> >> ACPI tables, but still notifies are sent to the Intel HID device
> >> object (device ID INT33D5) in response to power button actions.
> >> They were ignored as the intel-hid driver was not prepared to
> >> take care of them until recently.
> >>
> >> Power button wakeup from suspend-to-idle was added in:
> >> 635173a17b03 ("intel-hid: Wake up Dell Latitude 7275 from
> >> suspend-to-idle"). However power button suspend doesn't work
> >> yet on this platform so it would be good to add it also.
> >>
> >> On the affected platform (for which priv->array is NULL), add
> >> a new upfront check against the power button press notification
> >> (0xCE) to notify_handler(), outside the wakeup mode this time,
> >> which allows to report the power button press event and
> >> trigger the suspend. Also catch and ignore the corresponding
> >> power button release notification (0xCF) to stop it from being
> >> reported as an "unknown event" in the logs.
> >>
> >> Link: https://bugzilla.kernel.org/show_bug.cgi?id=196115
> >> Tested-by: Jérôme de Bretagne <jerome.debretagne@gmail.com>
> >> Signed-off-by: Jérôme de Bretagne <jerome.debretagne@gmail.com>
> >> ---
> >> drivers/platform/x86/intel-hid.c | 16 ++++++++++++++++
> >> 1 file changed, 16 insertions(+)
> >>
> >> diff --git a/drivers/platform/x86/intel-hid.c b/drivers/platform/x86/intel-hid.c
> >> index a782c78e7c63..b19f8dcf9d8c 100644
> >> --- a/drivers/platform/x86/intel-hid.c
> >> +++ b/drivers/platform/x86/intel-hid.c
> >> @@ -226,6 +226,22 @@ static void notify_handler(acpi_handle handle, u32
> event,
> >> void *context)
> >> return;
> >> }
> >>
> >> + /*
> >> + * Needed for suspend to work on some platforms that don't expose
> >> + * the 5-button array, but still send notifies with power button
> >> + * event code to this device object on power button actions.
> >> + *
> >> + * Report the power button press; catch and ignore the button release.
> >> + */
> >> + if (!priv->array) {
> >> + if (event == 0xce) {
> >> + input_report_key(priv->input_dev, KEY_POWER, 1);
> >> + input_sync(priv->input_dev);
> >> + return;
> >> + } else if (event == 0xcf)
> >> + return;
> >> + }
> >> +
> >> /* 0xC0 is for HID events, other values are for 5 button array */
> >> if (event != 0xc0) {
> >> if (!priv->array ||
> >
> > LGTM, it's improved from what you posted to that bug already.
> >
> > Acked-By: Mario Limonciello <mario.limonciello@dell.com>
>
> Thanks Mario.
>
> In fact, I updated my initial fix proposal on the 12th in [1] and
> this patch matches exactly the updated version. You didn't receive
> the update notification from Bugzilla?
>
> [1] https://bugzilla.kernel.org/show_bug.cgi?id=196115#c12
No I didn't get one (or some enterprise spam filter helpfully avoided
letting it into my inbox).
next prev parent reply other threads:[~2017-09-20 20:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 22:57 Jérôme de Bretagne
2017-09-18 21:29 ` Mario.Limonciello
2017-09-18 22:40 ` Jérôme de Bretagne
2017-09-20 20:07 ` Mario.Limonciello [this message]
2017-09-22 23:45 ` Darren Hart
2017-09-25 10:57 ` Andy Shevchenko
2017-09-27 7:31 ` Darren Hart
2017-09-27 8:58 ` Andy Shevchenko
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=c288f2dae8594a438e07aea67211a308@ausx13mpc120.AMER.DELL.COM \
--to=mario.limonciello@dell.com \
--cc=alex.hung@canonical.com \
--cc=andy.shevchenko@gmail.com \
--cc=dvhart@infradead.org \
--cc=jerome.debretagne@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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®