> Not yet supported are new unique features introduced by the DualSense such as Adaptive Triggers and the VCM based Haptics. These features require a large amou

> Not yet supported are new unique features introduced by the DualSense such as Adaptive Triggers and the VCM based Haptics. These features require a large amount of data and complex data structures. It is not clear how to expose these. The current Evdev and FF frameworks are too limiting. We hope to have a dialog on how to expose these over time in a generic way. It looks like the Sony devs want to support the new vibration features, but don't want to abuse the existing hid/input layer for the amounts of data it apparently requires. It is good they're looking for feedback (I assume via the kernel development mailing lists) on the right route to implement them. It'd be neat if we started to see a lot of open source projects that used this controller in the same way Kinect projects took off.