Since the new ll_driver functions allow for reports to be sent on the control channel the LEDs and force-feedback can be enabled for the Sixaxis/Dualshock 3. The second patch only sets the force-feedback flags for devices that actually support force feedback. It also moves the cancel_work_sync function out of the ff shutdown function since the worker functions are initialized and used for the LEDs even when force-feedback support is disabled at compile time. The final patch is an updated version of the duplicate controller detection code that was originally part of the Bluetooth patch set. It now works on both the Sixaxis and Dualshock 4. On USB the MAC can be retrieved via feature reports. Unfortunately, neither controller supports retrieving the MAC address via a feature report when connected via Bluetooth so it needs to be parsed from the uniq string where HIDP stores it. Based on previous discussions (http://www.spinics.net/lists/linux-input/msg29530.html), uniq should provide a stable way for retrieving a Bluetooth MAC address under normal circumstances, unless the behavior in HIDP changes for some reason. If a MAC cannot be parsed from the uniq string the duplicate check will be skipped and the connection will proceed, so even in the case of a uHID device or the behavior of HIDP changing in the future, a user's controller will still work. -- 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
