- 28 Nov, 2016 2 commits
-
-
Cameron Gutman authored
Unlike previous Xbox pads, the Xbox One pad doesn't have "sticky" rumble packets. The duration is encoded into the command and expiration is handled by the pad firmware. ff-memless needs pseudo-sticky behavior for rumble effects to behave properly for long duration effects. We already specify the maximum rumble on duration in the command packets, but it's still only good for about 2.5 seconds of rumble. This is easily reproducible running fftest's sine vibration test. It turns out there's a repeat count encoded in the rumble command. We can abuse that to get the pseudo-sticky behavior needed for rumble to behave as expected for effects with long duration. By my math, this change should allow a single ff_effect to rumble for 10 minutes straight, which should be more than enough for most needs. Signed-off-by:
Cameron Gutman <aicommander@gmail.com> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
Cameron Gutman authored
This is the new gamepad that ships with the Xbox One S which includes Bluetooth functionality. Signed-off-by:
-
- 25 Nov, 2016 2 commits
-
-
Benjamin Tissoires authored
The PNP0C40 device of the Surface 3 doesn't have any GPIO attached to it. Instead of trying to access the GPIO, request the count beforehand and bail out if it is null or if an error is returned. Signed-off-by:
Benjamin Tissoires <benjamin.tissoires@redhat.com> Signed-off-by:
-
Benjamin Tissoires authored
gpio_keys will later use gpio_is_valid(). To match the actual behavior, we should use it here too. Signed-off-by:
-
- 23 Nov, 2016 1 commit
-
-
Marcos Paulo de Souza authored
Signed-off-by:
Marcos Paulo de Souza <marcos.souza.org@gmail.com> Signed-off-by:
-
- 17 Nov, 2016 4 commits
-
-
Sudeep Holla authored
Commit 700a38b2 ("Input: gpio_keys - switch to using generic device properties") switched to use generic device properties for GPIO keys and commit 5feeca3c ("Input: gpio_keys - add support for GPIO descriptors") switched from legacy GPIO numbers to GPIO descriptors. Previously devm_gpio_request_one was explicitly passed GPIOF_DIR_IN flag to set the GPIO direction as input. However devm_get_gpiod_from_child doesn't have such provisions and hence fwnode_get_named_gpiod can't set it as input. This breaks few platforms with the following error: " gpiochip_lock_as_irq: tried to flag a GPIO set as output for IRQ unable to lock HW IRQ <n> for IRQ genirq: Failed to request resources for POWER (irq <x>) on irqchip gpio_keys: Unable to claim irq <x>; error -22 gpio-keys: probe failed with error -22 " This patch fixes the issue by setting input direction explicitly for gpio lines described by generic properties. Fixes: 700a38b2 ("Input: gpio_keys - switch to using generic device properties") Signed-off-by:
Sudeep Holla <sudeep.holla@arm.com> Signed-off-by:
-
Colin Ian King authored
Trivial fix to spelling mistake "failied" to "failed" in dev_err message. Signed-off-by:
Colin Ian King <colin.king@canonical.com> Signed-off-by:
-
Hans de Goede authored
On some tablets the touchscreen controller is powered by separate regulators, add support for this. Signed-off-by:
Hans de Goede <hdegoede@redhat.com> Acked-by:
Rob Herring <robh@kernel.org> Signed-off-by:
-
Hans de Goede authored
commit ef3714fd ("Input: bma150 - extend chip detection for bma180"), adds bma180 chip-ids to the input bma150 driver, assuming that they are 100% compatible, but the bma180 is not compatible with the bma150 at all, it has 14 bits resolution instead of 10, and it has quite different control registers too. Treating the bma180 as a bma150 wrt its data registers will just result in throwing away the lowest 4 bits, which is not too bad. But the ctrl registers are a different story. Things happen to just work but supporting that certainly does not make treating the bma180 the same as the bma150 right. Since some setups depend on the evdev interface the bma150 driver offers on top of the bma180, we cannot simply remove the bma180 ids. So this commit only removes the bma180 id when the bma180 iio driver, which does treat the bma180 properly, is enabled. Signed-off-by:
-
- 09 Nov, 2016 2 commits
-
-
Steve Twiss authored
Add binding information for DA9061 onkey. This patch updates the compatible string "dlg,da9061-onkey" to support DA9061, removes the reference to KEY_SLEEP (which the driver no longer supports) and fixes a typo in the example for DA9063. Supporting KEY_SLEEP was not the general convention and the typical solution should have been for KEY_POWER to support both cases of suspend and S/W power off. This change was sent to the DA9063 ONKEY device driver in a separate patch, but the documentation was not updated at that time. - f889beaa Report KEY_POWER instead of KEY_SLEEP during power key-press This patch also adds two new examples, one for DA9062 and one for DA9061. The DA9061 examples uses a fall-back compatible string for the DA9062 onkey driver. Signed-off-by:
Steve Twiss <stwiss.opensource@diasemi.com> Signed-off-by:
-
Sangwon Jee authored
Add reporting product ID through input_id. Signed-off-by:
Sangwon Jee <jeesw@melfas.com> Signed-off-by:
-
- 08 Nov, 2016 6 commits
-
-
Dmitry Torokhov authored
Make use of the device property API in this driver so that both OF based systems and ACPI based systems can use this driver. Suggested-by:
Geert Uytterhoeven <geert+renesas@glider.be> Suggested-by:
Mika Westerberg <mika.westerberg@linux.intel.com> Tested-by:
-
Geert Uytterhoeven authored
GPIO descriptors are the preferred way over legacy GPIO numbers nowadays. Convert the driver to use GPIO descriptors internally but still allow passing legacy GPIO numbers from platform data to support existing platforms. Based on commits 633a21d8 ("input: gpio_keys_polled: Add support for GPIO descriptors") and 1ae5ddb6 ("Input: gpio_keys_polled - request GPIO pin as input."). Signed-off-by:
Linus Walleij <linus.walleij@linaro.org> Tested-by:
-
Dmitry Torokhov authored
for_each_available_child_of_node(node, pp) takes reference to 'pp' and drops it when attempting next iteration. However if we exit the loop early we need to drop the reference ourselves. Tested-by:
-
Dmitry Torokhov authored
Instead of using #ifdef, let's mark suspend and resume methods as __maybe_unused to provide better compile coverage. Tested-by:
-
Dmitry Torokhov authored
It does not matter if given GPIO may sleep or not when reading state, polling is always done in a non-atomic context, so we should always be able to simply use gpiod_get_value_cansleep(). Also let's note in the logs when we fail to read gpio state. Reviewed-by:
-
Dmitry Torokhov authored
Commit 633a21d8 ("input: gpio_keys_polled: Add support for GPIO descriptors") placed gpio descriptor into gpio_keys_button structure, which is supposed to be part of platform data and not modifiable by the driver. To keep the data constant, let's move the descriptor to gpio_keys_button_data structure instead. Tested-by:
-
- 26 Oct, 2016 7 commits
-
-
Javier Martinez Canillas authored
If the driver is built as a module, autoload won't work because the module alias information is not filled. So user-space can't match the registered device with the corresponding module. Export the module alias information using the MODULE_DEVICE_TABLE() macro. Before this patch: $ modinfo drivers/input/misc/da9063_onkey.ko | grep alias alias: platform:da9063-onkey After this patch: $ modinfo drivers/input/misc/da9063_onkey.ko | grep alias alias: platform:da9063-onkey alias: of:N*T*Cdlg,da9062-onkeyC* alias: of:N*T*Cdlg,da9062-onkey alias: of:N*T*Cdlg,da9063-onkeyC* alias: of:N*T*Cdlg,da9063-onkey Signed-off-by:
Javier Martinez Canillas <javier@osg.samsung.com> Signed-off-by:
-
Javier Martinez Canillas authored
If the driver is built as a module, autoload won't work because the module alias information is not filled. So user-space can't match the registered device with the corresponding module. Export the module alias information using the MODULE_DEVICE_TABLE() macro. Before this patch: $ modinfo drivers/input/touchscreen/fsl-imx25-tcq.ko | grep alias After this patch: $ modinfo drivers/input/touchscreen/fsl-imx25-tcq.ko | grep alias alias: of:N*T*Cfsl,imx25-tcqC* alias: of:N*T*Cfsl,imx25-tcq Signed-off-by:
-
Benjamin Tissoires authored
it's always easier to retrieve these information in bug reports when it is always printed in the dmesg. Signed-off-by:
-
Arnd Bergmann authored
Older versions of gcc warn about the tca8418_irq_handler function as they can't keep track of the variable assignment inside of the loop when using the -Wmaybe-unintialized flag: drivers/input/keyboard/tca8418_keypad.c: In function ‘tca8418_irq_handler’: drivers/input/keyboard/tca8418_keypad.c:172:9: error: ‘reg’ may be used uninitialized in this function [-Werror=maybe-uninitialized] drivers/input/keyboard/tca8418_keypad.c:165:5: note: ‘reg’ was declared here This is fixed in gcc-6, but it's possible to rearrange the code in a way that avoids the warning on older compilers as well. Signed-off-by:
Arnd Bergmann <arnd@arndb.de> Signed-off-by:
-
Sangwon Jee authored
Use product id for firmware name to request compatible firmware. Signed-off-by:
-
Steve Twiss authored
Copyright header is updated to add DA9061 in its description and the module description macro is extended to include DA9061. Minor change to the code, alters dev_dbg() statements to report a generic "PMIC" instead of DA9063. This device driver is compatible with DA9061, DA9062 and DA9063. Kconfig is updated to reflect support for DA9061/62/63. Signed-off-by:
-
Colin Ian King authored
Trivial fix to typo in dev_err message Signed-off-by:
-
- 21 Oct, 2016 2 commits
-
-
Marcos Paulo de Souza authored
Instead of relying on this model zoo let's skip selftest on all newer Asus laptops (newer as in when they changed "Computer" -> "COMPUTER" in their DMI data). Signed-off-by:
-
Sangwon Jee authored
Add product_id sysfs attribute and update protocol version to support it. Signed-off-by:
-
- 14 Oct, 2016 1 commit
-
-
Dmitry Torokhov authored
Sync up with mainline to bring in I2C host notify changes and other updates.
-
- 11 Oct, 2016 2 commits
-
-
Marcos Paulo de Souza authored
On suspend/resume cycle, selftest is executed to reset i8042 controller. But when this is done in Asus devices, subsequent calls to detect/init functions to elantech driver fails. Skipping selftest fixes this problem. An easier step to reproduce this problem is adding i8042.reset=1 as a kernel parameter. On Asus laptops, it'll make the system to start with the touchpad already stuck, since psmouse_probe forcibly calls the selftest function. This patch was inspired by John Hiesey's change[1], but, since this problem affects a lot of models of Asus, let's avoid running selftests on them. All models affected by this problem: A455LD K401LB K501LB K501LX R409L V502LX X302LA X450LCP X450LD X455LAB X455LDB X455LF Z450LA [1]: https://marc.info/?l=linux-input&m=144312209020616&w=2 Fixes: "ETPS/2 Elantech Touchpad dies after resume from suspend" (https://bugzilla.kernel.org/show_bug.cgi?id=107971) Signed-off-by:
-
Sangwon Jee authored
Add ic_name sysfs attribute for retrieving IC model name. Signed-off-by:
-
- 07 Oct, 2016 3 commits
-
-
Sangwon Jee authored
Add maintainer information. Signed-off-by:
-
Sangwon Jee authored
Add devicetree binding documentations. Signed-off-by:
-
Dmitry Torokhov authored
Another Lifebook machine that needs the same quirk as other similar models to make the driver working. Also let's reorder elantech_dmi_force_crc_enabled list so LIfebook enries are in alphabetical order. Reported-by:
William Linna <william.linna@gmail.com> Tested-by:
-
- 04 Oct, 2016 8 commits
-
-
Guenter Roeck authored
Instantiating the rmi4 I2C transport driver without interrupts assigned (for example using manual i2c instantiation from the command line) caused the driver to fail to load, but it does not clean up its regulator or transport device registrations. Result is a crash at a later time, for example when rebooting the system. Fixes: 946c8432 ("Input: synaptics-rmi4 - support regulator supplies") Cc: Bjorn Andersson <bjorn.andersson@linaro.org> Signed-off-by:
Guenter Roeck <linux@roeck-us.net> Signed-off-by:
-
Guenter Roeck authored
Instantiating the rmi4 SPI transport driver without an interrupt assigned caused the driver to fail to load, but it does not clean up its transport device registration. Result may be a crash at a later time, for example when rebooting the system. Fixes: 8d99758d ("Input: synaptics-rmi4 - add SPI transport driver") Signed-off-by:
-
Ben Gamari authored
Tested-by:
Michal Hocko <mhocko@suse.com> Signed-off-by:
Ben Gamari <ben@smart-cactus.org> Signed-off-by:
-
Ben Gamari authored
Here we introduce logic in alps_identify to set the ALPS_DUALPOINT flag for touchpad hardware responding to E7 report with 73 03 28, as is found in the Dell Latitude E7470. Tested-by:
-
Ben Gamari authored
The SS5 hardware can report this. Tested-by:
-
Ben Gamari authored
While a button is held SS5 hardware will give us single-finger packets with x, y, and pressure equal to zero. This causes annoying jumps in pointer position if a touch is released while the button is held. Handle this by claiming zero contacts to ensure that no position events are provided to the user. Reviewed-by:
Pali Rohár <pali.rohar@gmail.com> Tested-by:
-
Ben Gamari authored
Add touchstick support for the so-called SS5 hardware, which uses a variant of the SS4 protocol. Reviewed-by:
-
Matti Kurkela authored
Just like Fujitsu CELSIUS H730, the H760 also has an Elantech touchpad with the same quirks. Without this patch, the touchpad is useless out-of-the-box as the mouse pointer won't move. This patch makes the driver aware of both the crc_enabled=1 requirement and the middle button, making the touchpad fully functional out-of-the-box. Signed-off-by:
Matti Kurkela <Matti.Kurkela@iki.fi> Cc: stable@vger.kernel.org Signed-off-by:
-
