[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1426697978.6764.8.camel@hadess.net>
Date: Wed, 18 Mar 2015 17:59:38 +0100
From: Bastien Nocera <hadess@...ess.net>
To: Martin Kepplinger <martink@...teo.de>
Cc: Alexander Stein <alexander.stein@...tec-electronic.com>,
robh+dt@...nel.org, pawel.moll@....com, mark.rutland@....com,
ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
dmitry.torokhov@...il.com, akpm@...ux-foundation.org,
gregkh@...uxfoundation.org, linux-api@...r.kernel.org,
devicetree@...r.kernel.org, linux-input@...r.kernel.org,
linux-kernel@...r.kernel.org,
Martin Kepplinger <martin.kepplinger@...obroma-systems.com>,
Christoph Muellner <christoph.muellner@...obroma-systems.com>
Subject: Re: [PATCH v2] add support for Freescale's MMA8653FC 10 bit
accelerometer
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?
Cheers
[1]: https://github.com/hadess/iio-sensor-proxy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists