Re: [PATCH 00/05] input: RMI4 Synaptics RMI4 Touchscreen Driver
On 02/03/2014 11:56 PM, Linus Walleij wrote: On Sat, Jan 19, 2013 at 2:12 AM, Christopher Heiny wrote: This patchset implements changes based on the synaptics-rmi4 branch of Dmitry's input tree. What is happening to the RMI4 driver stuff? Has this development stalled? The branch in Dmitry's git seems to be maintained but not much is happening or is there any progress? Hi Linus, Development stalled for several months last year, but picked up again last fall. We've been submitting patches against Dmitry's input tree, sending them to linux-input rather than linux-kernel. If you check the linux-input archives on spinics, you can see what's been going on. If you'd like, we'll make sure to cc you on upcoming patches. I've got some due - hopefully later today. Chris -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 00/05] input: RMI4 Synaptics RMI4 Touchscreen Driver
On 02/03/2014 11:56 PM, Linus Walleij wrote: On Sat, Jan 19, 2013 at 2:12 AM, Christopher Heiny che...@synaptics.com wrote: This patchset implements changes based on the synaptics-rmi4 branch of Dmitry's input tree. What is happening to the RMI4 driver stuff? Has this development stalled? The branch in Dmitry's git seems to be maintained but not much is happening or is there any progress? Hi Linus, Development stalled for several months last year, but picked up again last fall. We've been submitting patches against Dmitry's input tree, sending them to linux-input rather than linux-kernel. If you check the linux-input archives on spinics, you can see what's been going on. If you'd like, we'll make sure to cc you on upcoming patches. I've got some due - hopefully later today. Chris -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 00/05] input: RMI4 Synaptics RMI4 Touchscreen Driver
On Sat, Jan 19, 2013 at 2:12 AM, Christopher Heiny wrote: > This patchset implements changes based on the synaptics-rmi4 branch of > Dmitry's input tree. What is happening to the RMI4 driver stuff? Has this development stalled? The branch in Dmitry's git seems to be maintained but not much is happening or is there any progress? Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 00/05] input: RMI4 Synaptics RMI4 Touchscreen Driver
On Sat, Jan 19, 2013 at 2:12 AM, Christopher Heiny che...@synaptics.com wrote: This patchset implements changes based on the synaptics-rmi4 branch of Dmitry's input tree. What is happening to the RMI4 driver stuff? Has this development stalled? The branch in Dmitry's git seems to be maintained but not much is happening or is there any progress? Yours, Linus Walleij -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH 00/05] input: RMI4 Synaptics RMI4 Touchscreen Driver
This patchset implements changes based on the synaptics-rmi4 branch of Dmitry's input tree. The base for the patchset is Dmitry's commit 0af25383d395fb5ece54b79d12d06138bf8b9836 from 2012-11-28. It supersedes our previous patch submission from 2012-12-18. Overall this patchset implements the following changes with respect to the Dmitry's 2012-11-28 commit: * updates to Dmitry's RMI4_CORE structure from his 2012-11-28 patches. This tries to maintain the same approach as Dmitry's implementation, but we had to move away from using the bus probe() routine, since it wasn't possible for that routine to readily determine if it had a struct driver() for an RMI4 sensor or an RMI4 device. Otherwise, we've stuck close to Dmitry's work, which has tidied things up nicely. * We've renamed the structures rmi_function_handler to rmi_function_driver and rmi_device to rmi_function_dev, mainly because they actually were being treated as drivers and devices for individual RMI4 functions, and the previous terminology was somewhat confusing. * Changed a bunch of bools to u32 to support standard debugfs macros. Moved almost all the debugfs and sysfs handling out of these files into their own modules, simplifying the core functionality of the driver. Once the core is stable, we can look into adding modules to support the debug/control features. * Many other bools were changed to u8, per Dmitry's request. * Trivial - file copyright header is updated to be more in line with the rest of the files under ./input. We've broken this patch into 6 parts, as follows: 01 - public header file 02 - core sensor and bus implementation 03 - I2C physical layer driver 04.05 - drivers for individual RMI functions Hopefully this is the last time we'll have wide-ranging structural changes in the driver code, and future patchsets can be much smaller and confined to one or two areas of interest. Comments and other feedback on this driver are welcomed. Christopher Heiny and the Synaptics RMI4 driver team Signed-off-by: Christopher Heiny Cc: Dmitry Torokhov Cc: Jean Delvare Cc: Linus Walleij Cc: Joeri de Gram --- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH 00/05] input: RMI4 Synaptics RMI4 Touchscreen Driver
This patchset implements changes based on the synaptics-rmi4 branch of Dmitry's input tree. The base for the patchset is Dmitry's commit 0af25383d395fb5ece54b79d12d06138bf8b9836 from 2012-11-28. It supersedes our previous patch submission from 2012-12-18. Overall this patchset implements the following changes with respect to the Dmitry's 2012-11-28 commit: * updates to Dmitry's RMI4_CORE structure from his 2012-11-28 patches. This tries to maintain the same approach as Dmitry's implementation, but we had to move away from using the bus probe() routine, since it wasn't possible for that routine to readily determine if it had a struct driver() for an RMI4 sensor or an RMI4 device. Otherwise, we've stuck close to Dmitry's work, which has tidied things up nicely. * We've renamed the structures rmi_function_handler to rmi_function_driver and rmi_device to rmi_function_dev, mainly because they actually were being treated as drivers and devices for individual RMI4 functions, and the previous terminology was somewhat confusing. * Changed a bunch of bools to u32 to support standard debugfs macros. Moved almost all the debugfs and sysfs handling out of these files into their own modules, simplifying the core functionality of the driver. Once the core is stable, we can look into adding modules to support the debug/control features. * Many other bools were changed to u8, per Dmitry's request. * Trivial - file copyright header is updated to be more in line with the rest of the files under ./input. We've broken this patch into 6 parts, as follows: 01 - public header file 02 - core sensor and bus implementation 03 - I2C physical layer driver 04.05 - drivers for individual RMI functions Hopefully this is the last time we'll have wide-ranging structural changes in the driver code, and future patchsets can be much smaller and confined to one or two areas of interest. Comments and other feedback on this driver are welcomed. Christopher Heiny and the Synaptics RMI4 driver team Signed-off-by: Christopher Heiny che...@synaptics.com Cc: Dmitry Torokhov dmitry.torok...@gmail.com Cc: Jean Delvare kh...@linux-fr.org Cc: Linus Walleij linus.wall...@stericsson.com Cc: Joeri de Gram j.de.g...@gmail.com --- -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
