From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Peter Meerwald" <pmeerw@pmeerw.net>,
"Kristina Martšenko" <kristina.martsenko@gmail.com>,
"Jonathan Cameron" <jic23@kernel.org>,
linux-iio@vger.kernel.org, "Lars-Peter Clausen" <lars@metafoo.de>
Subject: Re: IIO drivers left in drivers/staging/
Date: Sat, 21 Jun 2014 09:55:22 +0200 [thread overview]
Message-ID: <20140621075522.GY19375@piout.net> (raw)
In-Reply-To: <20140620204248.GF16973@kroah.com>
On 20/06/2014 at 13:42:48 -0700, Greg KH wrote :
> >
> > I would say that the latest addition to the TODO file is quite valid ;)
> > We have been looking at moving the mxs-lradc out of staging for a while
> > now. It still has a few contributions coming from time to time and can
> > definitely be improved. The main thing to do would be to create an MFD.
> >
> > I understand this may be a considerable amount of work but it has the
> > advantage of allowing to have a look at at least 3 different subsystems.
> >
> > I am willing to review and test patches.
> >
> > I would suggest that board:
> > http://www.crystalfontz.com/product/CFA921TS
> >
> > It may not be the cheapeast one but it has good mainline support and I
> > know it well.
>
> What sensors does it have on it that are iio drivers that need fixing
> up?
>
It is i.mx28 based so it has the mxs LRADC which is currently supported
through drivers/staging/iio/adc/mxs-lradc.c.
It is also a touchscreen controller, a temperature sensor and a battery
voltage monitor so it would make sense to create an mfd and move the
touchscreen part in the input subsystem and add a driver for the voltage
monitor in the power subsystem.
You can also have a look at that thread:
http://www.spinics.net/lists/linux-iio/msg11004.html
> It's not that expensive, my budget for Linux devices can cover it...
>
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-06-21 7:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 1:30 IIO drivers left in drivers/staging/ Greg KH
2014-06-11 6:37 ` Jonathan Cameron
2014-06-11 8:05 ` Jonathan Cameron
2014-06-12 11:21 ` Kristina Martšenko
2014-06-18 12:43 ` Kristina Martšenko
2014-06-18 12:56 ` Peter Meerwald
2014-06-18 16:33 ` Jonathan Cameron
2014-06-18 17:47 ` Greg KH
2014-06-18 18:06 ` Jonathan Cameron
2014-06-18 19:45 ` Jonathan Cameron
2014-06-19 12:54 ` Alexandre Belloni
2014-06-20 20:42 ` Greg KH
2014-06-21 7:55 ` Alexandre Belloni [this message]
2014-06-21 20:18 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140621075522.GY19375@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=kristina.martsenko@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.