On Sat, Mar 3, 2012 at 1:09 PM, Jonathan Cameron <jic23@xxxxxxxxxx> wrote: > From: Jonathan Cameron <jic23@xxxxxxxxx> > > This is no where near ready to merge. Lots of stuff missing. > > Signed-off-by: Jonathan Cameron <jic23@xxxxxxxxxx> Overall this is looking very interesting, this is definately where we want to go with this IMO. > +static int iio_input_store_to(u8 *data, void *private) > +{ > + struct iio_input_state *st = private; > + > + /* DUMMY - need to put boiler plate conversion code > + * in place */ > + input_report_abs(st->idev, ABS_X, data[0]); > + input_sync(st->idev); > + > + return 0; > +} If I have understood correctly, a lot of contemporary input handling is in need of strict timestamping such as available in IIO. (Strict control feedback loops etc.) I guess these applications should use the "real" IIO interfaces, whereas the input interface should be kept as-is? Or ... is it possible to get the input subsystem to propagate the timestamps to userspace? Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html