Am 2015-03-18 um 17:59 schrieb Bastien Nocera: > On Wed, 2015-03-18 at 17:42 +0100, Martin Kepplinger wrote: >> > <snip> >> It could have gone to drivers/iio/accel if it would use an iio >> interface, which would make more sense, you are right, but I simply >> don't have the time to merge it in to iio. >> >> It doesn't use an input interface either but I don't see a good >> place for an accelerometer that uses sysfs only. >> >> It works well, is a relatively recent chip and a clean dirver. But >> this is all I can provide. > > As a person who works on the user-space interaction of those with > desktops [1]: Urgh. > > I already have 3 (probably 4) types of accelerometers to contend with, > I'm not fond of adding yet another type. > > Is there any way to get this hardware working outside the SoCs it's > designed for (say, a device with I2C like a Raspberry Pi), so that a > kind soul could handle getting this using the right interfaces? > It works on basically any SoC and is in no way limited in this regard. Sure, userspace has to expicitely support it and I hear you. Using the iio interface would make more sense. I can only say I'd love to have the time to move this driver over. I'm very sorry. > Cheers > > [1]: https://github.com/hadess/iio-sensor-proxy > -- 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
