summaryrefslogtreecommitdiffstats
path: root/Documentation/devicetree/bindings
diff options
context:
space:
mode:
authorCameron Gutman <aicommander@gmail.com>2016-11-27 20:37:56 -0800
committerDmitry Torokhov <dmitry.torokhov@gmail.com>2016-11-27 20:45:13 -0800
commitae3b4469dbcd3b842a9fd20940946e4d092d8731 (patch)
treeaf5777cd9e2104653d340acf3fe56c185d08e43c /Documentation/devicetree/bindings
parent599b8c09d974d6e4d85a8f7bc8ed7442977866a8 (diff)
downloadop-kernel-dev-ae3b4469dbcd3b842a9fd20940946e4d092d8731.zip
op-kernel-dev-ae3b4469dbcd3b842a9fd20940946e4d092d8731.tar.gz
Input: xpad - fix Xbox One rumble stopping after 2.5 secs
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>
Diffstat (limited to 'Documentation/devicetree/bindings')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud