On Fri, Nov 12, 2010 at 03:34:36PM +0530, Hemanth V wrote: > ----- Original Message ----- From: "Hemanth V" <hemanthv@xxxxxx> > To: "Jonathan Cameron" <jic23@xxxxxxxxx>; "Dmitry Torokhov" <dtor@xxxxxxx> > > >> ----- Original Message ----- From: "Jonathan Cameron" <jic23@xxxxxxxxx> >> To: "Jonathan Cameron" <jic23@xxxxxxxxx> >> Sent: Thursday, September 30, 2010 3:36 PM >> Subject: Re: Sensor event related attribute naming. >> >> >>> Given the lack of further comment, I went ahead and implemented the above >>> naming >>> scheme for IIO. As the above discussion with Hemanth shows, there are >>> some corner cases >>> that will need futher thought in the future. >>> >> >> Jonathan, haven't seen many comments on this. Do u think the reason >> might be that these interfaces are hidden behind a HAL layer like in >> android and >> might not be a burning issue for many people. >> > > Dmitry, could you let us know your thoughts on this too. > Would using a HAL layer be better compared to creating a standard > sysfs interface, as it seems to be the popular approach. What "HAL layer"? HAL the userspace project is now dead, so you should standardize on a common sysfs or some other user/kernel api that the kernel exports for the same type of devices to make it so that everything works the same way. thanks, greg k-h -- 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
