From: Clement Calmels <clement.calmels@free.fr>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Pavel Rojtberg <rojtberg@gmail.com>,
linux-input@vger.kernel.org,
"Pierre-Loup A. Griffais" <githubpublic@plagman.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: xpad - use LED API when identifying wireless controllers
Date: Wed, 13 Jan 2016 21:34:15 +0100 [thread overview]
Message-ID: <20160113213415.24667399@gromit> (raw)
In-Reply-To: <20160112180451.GA32064@dtor-ws>
On Tue, 12 Jan 2016 10:04:51 -0800
Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> On Mon, Jan 04, 2016 at 04:50:17PM -0800, Dmitry Torokhov wrote:
> > On Thu, Dec 24, 2015 at 07:11:22PM +0100, Pavel Rojtberg wrote:
> > >
> > > for me this one did the trick. The correct LED lights up after
> > > resume.
> > >
> > > Integrated it here (master):
> > > https://github.com/paroj/xpad
> >
> > Pavel, I refreshed my xpad branch on kernel.org folding the
> > reset_resume and anchor changes into your original suspend/resume
> > patch. Could you please try it out so that I can send it to
> > mainline in the upcoming merge window?
>
> Gentle ping. I can still fit it in my 2nd pull request but time is
> running out...
>
> Thanks.
>
Hi Dimitry,
Source code from
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git, branch
xpad, head d9be398afb2c3333716324352d062c50112e4e86.
After suspend (systemctl suspend) my xpad wireless controller is still
blinking. Tried "echo 2 > /sys/class/leds/xpad0/brightness" but it did
not work.
That said, I also tried the same xpad code but built for my current
kernel (4.3.0 from debian/sid): led is still blinking after resume but
this time the sysfs file is functional.
Hopefully I did not make a mistake in the build process...
Best regards,
Clement
prev parent reply other threads:[~2016-01-13 20:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 22:44 [PATCH] Input: xpad - use LED API when identifying wireless controllers Dmitry Torokhov
2015-12-19 21:17 ` Clement Calmels
2015-12-20 7:55 ` Dmitry Torokhov
2015-12-20 12:49 ` Pavel Rojtberg
2015-12-21 20:06 ` Dmitry Torokhov
2015-12-22 9:55 ` Clement Calmels
2015-12-24 18:11 ` Pavel Rojtberg
2016-01-05 0:50 ` Dmitry Torokhov
2016-01-12 18:04 ` Dmitry Torokhov
2016-01-13 20:34 ` Clement Calmels [this message]
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=20160113213415.24667399@gromit \
--to=clement.calmels@free.fr \
--cc=dmitry.torokhov@gmail.com \
--cc=githubpublic@plagman.net \
--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).