[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160113213415.24667399@gromit>
Date: Wed, 13 Jan 2016 21:34:15 +0100
From: Clement Calmels <clement.calmels@...e.fr>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: Pavel Rojtberg <rojtberg@...il.com>, linux-input@...r.kernel.org,
"Pierre-Loup A. Griffais" <githubpublic@...gman.net>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Input: xpad - use LED API when identifying wireless
controllers
On Tue, 12 Jan 2016 10:04:51 -0800
Dmitry Torokhov <dmitry.torokhov@...il.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
Powered by blists - more mailing lists