Hello Lars. Thank you for your interest and sorry for the late answer. When I posted the proposal I was still studying the event interface, so I decided not to add it as a possible use case yet. I believe an input abstracted evdev would allow the creation of a more flexible and simpler to use event interface. Every event generated by a device could be broadcasted trough a single file in /dev (created by the abstracted evdev) and read by an application with the help of an header file describing the new event interface (like input currently does with evdev and input.h). This approach will allow to have an event interface that's simpler to use for an userspace app because instead of reading N sysfs files concurrently the app will have to read just one file in /dev and then handle the events received with something like a switch statement. Input abstracted evdev will help by creating the /dev file and forwarding the file_operations on that file to iio. I have added a bit more detailed explanations on my proposal. This is just an idea, I'm looking for your feedbacks to make it better. Regards, Alessandro Osima On May 3, 2013, at 9:50 AM, Lars-Peter Clausen <lars@xxxxxxxxxx> wrote: > On 04/30/2013 04:24 AM, alessandro osima wrote: >> Hello everyone, my name is Alessandro Osima and I'm a computer >> science student at Università degli Studi di Milano, Italy (second >> year, equivalent to bachelor). >> >> >> For this year's Google Summer of Code I have decided to submit an >> application proposal focused on abstracting evdev from input to allow >> iio and other subsystems to take advantage of it to send/receive >> events and data to userspace application troughout files located in >> the /dev directory. >> >> This http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/asion/1# >> is my proposal. >> >> I would kindly ask your opinions about this project and would be very >> grateful for any comments and suggestion to improve it. >> > > Hi, > > Sounds interesting. Did you hd a look at the existing IIO event interface > (drivers/iio/industrialio-event.c)? I'm asking because you don't seem to > mention it in your proposal. > > - Lars -- 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