Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1301213 > unrolled thread

Re: [PATCH] Input: xpad - use LED API when identifying wireless controllers

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH] Input: xpad - use LED API when identifying wireless  controllers Dmitry Torokhov <dmitry.torokhov@gmail.com> - 2016-01-05 02:00 +0100
    Re: [PATCH] Input: xpad - use LED API when identifying wireless  controllers Dmitry Torokhov <dmitry.torokhov@gmail.com> - 2016-01-12 19:10 +0100
      Re: [PATCH] Input: xpad - use LED API when identifying wireless  controllers Clement Calmels <clement.calmels@free.fr> - 2016-01-13 21:40 +0100

#1301213 — Re: [PATCH] Input: xpad - use LED API when identifying wireless controllers

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?

Thanks!

-- 
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]

#1307709

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.

-- 
Dmitry

[toc] | [prev] | [next] | [standalone]

#1308790

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web