> This patch series: > 1) Adds "ff-memless-next" module [1] > 2) Ports all hardware-specific drivers to MLNX's API [2-23] > 3) Removes FFML and replaces it with MLNX [24] > > Signed-off-by: Michal Malý <madcatxster@xxxxxxxxxxxxxxxxxx> > > v4: > - Add a summary of changes between MLNX and FFML to the last patch > - Remove a stale empty line in hid-sony.c > - Add "Tested-by: Elias Vanderstuyft <elias.vds@xxxxxxxxx>" to hid-lg4ff > patch. > > v3: > - Rebase against latest linux-next. Fixes conflict in hid-sony.c and > max8997_haptic.c > - Updated documentation in ff-memless-next.h. The documentation now > describes > parameters of the callback function and specifically mentions that > HW-specific drivers must not keep a reference to mlnx_effect_command > struct > to which a pointer is passed in the callback function. > - Fix a minor brace inconsistency in hid-lgff > I believe that all concerns regarding v2 have been resolved as false > alarms. > > v2: > - Add missing msecs to jiffies conversion in ff-memless-next > - lgff: Properly convert force on Y axis from MLNX to device range > Support periodic effects for "joystick_ac" device class > - lg3ff: Properly convert forces from MLNX to device range > - Very minor coding style issues fixed Hi all, I'd confirm that I build v2 and tested on a number of devices (1), and it appears to work OK. The only slight hiccup was with an older version (Xubuntu 12.10) 'ffcfstress' application which did not correctly detect the CF capabilities of my gaming wheel(s). This is believed to be a fault with the application not using correct bit-field testing and appears to have been fixed on later versions (Xubuntu 13.10). I also built v4, but have not yet had time/access to all the devices (other than DS4) to test. Cheers, Simon Tested-by: Simon Wood <simon@xxxxxxxxxxxxx> (1) Devices: Logitech Momo Red, Momo Black, DFGT, WiiWheel, G27 Sony DS3-SA, DS4, Intec 3rd Party PS3 controller Nintendo Wii Remote -- 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