Hi Henrik, On Mon, Jun 25, 2012 at 01:34:12PM +0200, Henrik Rydberg wrote: > Hi Simon, > > > > I would very much prefer if the driver functioned well without > > > such settings, since they complicate userspace and are not likely > > > to ever go away. Oh well. > > > > I would prefer to have the touchscreen adjust itself as well, > > unfortunately this is not available and you definitely need different > > settings depending for different touch setups. > > > > Would an ioctl() be more acceptable? Would make it harder to adjust it > > in startup scripts etc. though. > > The format (ioctl, sysfs or whatnot) is of no consequence, it is the > a) special handling of certain drivers and b) forcing userspace to > tune the driver that makes maintenance problematic in the long > run. With every screen project ending in its own solution, this > quickly becomes a problem, both in the kernel and in > userspace. Preventing such predicaments is my concern. The issue here is that the parameters exposed are truly device-specific and hard to standardize. We can try adding these parameters to the platform data so board code could set them up for the users, but I can see some users wanting to adjust the settings... Thanks. -- Dmitry -- 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
