Re: [PATCH 2/3] Input: alps: drop unlikely before IS_ERR_OR_NULL

On Thursday 01 October 2015 10:55:30 Geliang Tang wrote: > IS_ERR_OR_NULL already contain an unlikely compiler flag. Drop it. > > Signed-off-by: Geliang Tang > --- > drivers/input/mouse/alps.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

[PATCH v2] Input: Add support for FocalTech FT6236 touchscreen controller

This adds support for the FT6x06 and the FT6x36 family of capacitive touch panel controllers, in particular the FT6236. Signed-off-by: Noralf Trønnes --- The driver is based on:

RE: [PATCH v3 1/5] Input: goodix - reset device at init

> -Original Message- > From: mrgarna...@gmail.com [mailto:mrgarna...@gmail.com] On Behalf Of Carlos > Garnacho > Sent: 30 September, 2015 17:02 > To: Bastien Nocera > Cc: Tirdea, Irina; linux-input@vger.kernel.org; Cosimo Cecchi; Christian > Hergert; linux-ker...@vger.kernel.org; Rob

[PATCH 09/15] Input: xpad: handle "present" and "gone" correctly

From: "Pierre-Loup A. Griffais" Handle the "a new device is present" message properly by dynamically creating the input device at this point in time. This means we now do not "preallocate" all 4 devices when a single wireless base station is seen. This requires a

[PATCH 00/15] Input: xpad: updates

From: Pavel Rojtberg This series contains several bug-fixes and updates for the xpad driver from my github repository. See the issue tracker for full discussion of the individual patches: https://github.com/paroj/xpad/issues?q=is%3Aissue+is%3Aclosed Patches 1-2 improve

[PATCH 08/15] Input: xpad: query Wireless controller state at init

From: Pavel Rojtberg When we initialize the driver/device, we really don't know how many controllers are connected. So send a "query presence" command to the base-station. (Command discovered by Zachary Lund) presence packet taken from: https://github.com/computerquip/xpad5

[PATCH 02/15] Input: xpad: fix Razer Atrox Arcade Stick button mapping

From: Dario Scarpa The "Razer Atrox Arcade Stick" features 10 buttons, and two of them (LT/RT) don't work properly. Change its definition in xpad_device[] (mapping field) to fix. Signed-off-by: Dario Scarpa Signed-off-by: Pavel Rojtberg

[PATCH 06/15] Input: xpad: x360w: report dpad as buttons and axes

From: Pavel Rojtberg as discussed here[0], x360w is the only pad that maps dpad_to_button. This is bad for downstream developers as they have to differ between x360 and x360w which is not intuitive. This patch implements the suggested solution of exposing the dpad both as

[PATCH 14/15] Input: xpad: workaround dead irq_out after suspend/ resume

From: Pavel Rojtberg the irq_out urb is dead after suspend/ resume on my x360 wr pad. (also reproduced by Zachary Lund [0]) Work around this by resetting the usb device on resume. Added suspend/ resume callbacks to do so. [0]: https://github.com/paroj/xpad/issues/6

[PATCH 04/15] Input: xpad: remove needless bulk out URB used for LED setup

From: Pavel Rojtberg this code was probably wrong ever since and is redundant with xpad_send_led_command. Both try to send a similar command to the xbox360 controller. However xpad_send_led_command correctly uses the pad_nr instead of bInterfaceNumber to select the led and

[PATCH 15/15] Input: xpad: update Xbox One Force Feedback Support

From: "Pierre-Loup A. Griffais" There's apparently a serial number woven into both input and output packets; neglecting to specify a valid serial number causes the controller to ignore the rumble packets. The scale of the rumble was also apparently halved in the

[PATCH 03/15] Input: xpad: clarify LED enumeration

From: Pavel Rojtberg this changes helps understanding the code 1. rename led_no -> pad_nr: the number stored there is not the LED Nr - it gets translated later on to a LED Nr in xpad_identify_controller 2. move all comments regarding xpad_identify_controller to the function

[PATCH 13/15] Input: xpad: re-submit pending ff and led requests

From: Pavel Rojtberg Store pending brightness and FF effect in the driver structure and replace it with the latest requests until the device is ready to process next request. Alternate serving LED vs FF requests to make sure one does not starve another. See [1] for

[PATCH 11/15] Input: xpad: do not submit active URBs

From: Pavel Rojtberg track the active status of the irq_out URB to prevent submission while it is active. Failure to do so results in the "URB submitted while active" warning/ stacktrace. Also add missing mutex locking around xpad->odata usages. Signed-off-by: Pavel

[PATCH 10/15] Input: xpad: use ida() for finding the pad_nr

From: Pavel Rojtberg The pad_nr corresponds to the lit up LED on the controller. Therefore there should be no gaps when enumerating. Currently a LED is only re-assigned after a controller is re-connected 4 times. This patch uses ida to track connected pads - this way we can

[PATCH 07/15] Input: xpad: move the input device creation to a new function

From: "Pierre-Loup A. Griffais" To allow us to later create / destroy the input device from the urb callback, we need to initialize/ deinitialize the input device from a separate function. So pull that logic out now to make later patches more "obvious" as to what

[PATCH 05/15] Input: xpad: factor out URB submission in xpad_play_effect

From: Pavel Rojtberg Move submisson logic to a single point at the end of the function. This makes it easy to add locking/ queuing code later on. Signed-off-by: Pavel Rojtberg --- drivers/input/joystick/xpad.c | 140

[PATCH 12/15] Input: xpad: replace mutex by spinlock

From: Pavel Rojtberg since we cannot use mutexes in xpad_play_effect. see: http://www.spinics.net/lists/linux-input/msg40242.html Signed-off-by: Pavel Rojtberg --- drivers/input/joystick/xpad.c | 30 +++--- 1 file changed, 19

Re: [PATCH 10/15] Input: xpad: use ida() for finding the pad_nr

sorry, I messed up this one. This would be the correct patch. Should I re-spin the whole series or would it be too much noise? Subject: [PATCH 10/15] Input: xpad: use ida() for finding the pad_nr The pad_nr corresponds to the lit up LED on the controller. Therefore there should be no gaps when

Re: [PATCH] usbhid: Fix lockdep unannotated irqs-off warning

I was thinking of disabling trace or ftrace and fell over some ftrace patches in llvmlinux. Comments? - Sedat - [1] http://git.linuxfoundation.org/?p=llvmlinux.git;a=blob;f=arch/x86_64/patches/ARCHIVE/0033-Various-fixes-in-arch-x86-include-asm.patch [2]

linux-input

付费电影不花钱www.4aw.GANDada.com

[PATCH RESEND v4] cap11xx: add runtime PM support

Changes from v3: * Dropped cap11xx_remove() and devm_add_action a powerdown and runtime pm cleanup. That runs afters input and LEDs devices have been reaped. * Move cap11xx_init_leds() after input device register becuase it was causing a hangup condition if an LED was lit on module removal.

Re: Input: gamecon - use parallel port device model

On Fri, Oct 02, 2015 at 01:05:32AM +0300, Dan Carpenter wrote: > Hello Sudip Mukherjee, > > The patch a517e87c3dfc: "Input: gamecon - use parallel port device > model" from Sep 29, 2015, leads to the following static checker > warning: > > drivers/input/joystick/gamecon.c:988 gc_attach() >

[PATCH RESEND v4] cap11xx: add runtime PM support

Puts device into DEEP SLEEP when no LEDs are in in the on-state, and no input_handlers are in use. Also uses *_autosuspend to prevent a LED trigger from constantly suspending and resuming device. Signed-off-by: Matt Ranostay --- drivers/input/keyboard/cap11xx.c | 84