On 1/17/2014 07:21, Jiri Kosina wrote:
On Fri, 17 Jan 2014, Antonio Ospite wrote:
Use a modified HID descriptor for the Dualshock 4 to assign the gyroscope
sensors and accelerometers to axes.
What about putting the descriptor fixup on hold for now?
Jiri, have you already pushed these patches?
Once the ABS2 stuff from David Hermann is done then proper mapping
following the Gamepad API[1] and the Motion-Tracking API[2] could be
added.
[1] Documentation/input/gamepad.txt
[2] Documentation/input/motion-tracking.txt
We could even have the DS3 and DS4 expose the same mapping.
Just a suggestion.
Hi,
yes, I have already pushed it, but we can of course discuss not including
it into pull for Linus if necessary.
My understanding is that once ABS2 stuff is done, this can just be
switched to using it in a backwards-compatible way, and the report fixup
could be dropped, no?
The default descriptor doesn't map the accelerometers or gyros to
anything. It's just a 'user defined' page that causes the HID system to
skip over the bytes in the report. My changes to the descriptor map the
accelerometers to usage 0x40, 0x41 and 0x42 and the gyroscope values to
0x43, 0x44 and 0x45. These are the proper HID usage values for
accelerometers and gyros according to the HID spec and according to the
updated motion-tracking.txt this is exactly what they need to be mapped
to to work with the ABS2 changes. Unless I'm missing something, these
descriptor changes should be forward-compatible.
If I recall, the Dualshock 3 maps it's accelerometers and gyros to the
same set of usage values as well.
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
