On 02/22/11 12:25, Alan Cox wrote: >> However, note that Dmitry has previously blocked merges of drivers into input >> precisely because these sysfs interfaces haven't been defined cleanly (in that >> case the relevant bits were just dropped from the driver in favour of platform >> data). He wants to see something general across all such sensors whatever >> subsystem they are actually in. > > Ultimately there is a lot to be said for a common interface, but as you > yourself point out - there isn't actually anything for it to be common > with. In this case some of the user interface side is needed at runtime > so platform interfaces (or hiding ioctls in platform code to hide it from > you ;) ) doesn't help much. > > It's up to Dmitry, it would be nice to have it upstream but if it ends up > only in Meego until IIO is stabilised and out of staging then thats less > ideal. This device looks very much like one that will mainly (if not exclusively) be used as an input device. Hence I'd be keener to see it in input than IIO even if IIO was already out of staging. Still, intent is to share sysfs interfaces in as many subsystems as possible, independent of where the driver actually sits. -- 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
