From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Cameron Gutman <aicommander@gmail.com>
Cc: rojtberg@gmail.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] Input: xpad - restore LED state after device resume
Date: Mon, 6 Feb 2017 14:05:18 -0800 [thread overview]
Message-ID: <20170206220518.GE17441@dtor-ws> (raw)
In-Reply-To: <20170205003002.28160-5-aicommander@gmail.com>
On Sat, Feb 04, 2017 at 04:30:01PM -0800, Cameron Gutman wrote:
> The state of pad LEDs can be inconsistent when the system is
> woken up after sleep. Rather than leaving the controllers blinking,
> let's resend the last LED command to Xbox 360 pads on resume.
>
> Since Xbox One pads stop flashing only when reinitialized, we'll
> send them the initialization packet so they calm down too.
>
> Signed-off-by: Cameron Gutman <aicommander@gmail.com>
> ---
> drivers/input/joystick/xpad.c | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/input/joystick/xpad.c b/drivers/input/joystick/xpad.c
> index 13f298d..1179266 100644
> --- a/drivers/input/joystick/xpad.c
> +++ b/drivers/input/joystick/xpad.c
> @@ -1683,11 +1683,23 @@ static int xpad_resume(struct usb_interface *intf)
> retval = xpad360w_start_input(xpad);
> } else {
> mutex_lock(&input->mutex);
> - if (input->users)
> + if (input->users) {
> retval = xpad_start_input(xpad);
> + } else if (xpad->xtype == XTYPE_XBOXONE) {
> + /*
> + * Even if there are no users, we'll send Xbox One pads
> + * the startup sequence so they don't sit there and
> + * blink until somebody opens the input device again.
> + */
> + retval = xpad_start_xbox_one(xpad);
> + }
> mutex_unlock(&input->mutex);
> }
>
> + /* LED state is lost across resume, so resend the last command */
> + if (xpad->led)
> + xpad_send_led_command(xpad, xpad->led->led_cdev.brightness);
I can see that we might need to send the "start" command, but I am not
sure that explicitly calling xpad_send_led_command() is needed: LED core
should restore LED state upon resume, and this should happen after its
parent (i.e. xbox device) is resumed.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2017-02-06 22:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-05 0:29 [PATCH 0/5] Correctly support some quirky Xbox One pads Cameron Gutman
2017-02-05 0:29 ` [PATCH 1/5] Input: xpad - use a packet array to start " Cameron Gutman
2017-02-05 0:29 ` [PATCH 2/5] Input: xpad - add init packet for Hori and Titanfall 2 pads Cameron Gutman
2017-02-05 0:30 ` [PATCH 3/5] Input: xpad - send rumble on Xbox One init to fix PowerA pads Cameron Gutman
2017-02-06 22:13 ` Dmitry Torokhov
2017-02-05 0:30 ` [PATCH 4/5] Input: xpad - restore LED state after device resume Cameron Gutman
2017-02-05 1:17 ` kbuild test robot
2017-02-05 1:47 ` Cameron Gutman
2017-02-06 22:05 ` Dmitry Torokhov [this message]
2017-02-06 22:57 ` Cameron Gutman
2017-02-05 0:30 ` [PATCH 5/5] Input: xpad - fix stuck mode button on Xbox One S pad Cameron Gutman
2017-02-06 22:03 ` Dmitry Torokhov
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=20170206220518.GE17441@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=aicommander@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rojtberg@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;
as well as URLs for NNTP newsgroup(s).