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: Thu, 19 Jun 2014 14:54:16 +0200 [thread overview]
Message-ID: <20140619125416.GT19375@piout.net> (raw)
In-Reply-To: <20140618174717.GC11977@kroah.com>
Hi,
On 18/06/2014 at 10:47:17 -0700, Greg KH wrote :
> On Wed, Jun 18, 2014 at 02:56:52PM +0200, Peter Meerwald wrote:
> > Hello Kristina,
> >
> > > > Okay so right now I'm getting the following things I could work on:
> > > >
> > > > 1) prefixes on define constants for lpc32xx_ADC (then trying to move it
> > > > out of staging and seeing what other issues people find?)
> > > > 2) resolver/CDC ABI documentation cleanup
> > > > 3) dummy driver fake event interrupt hack
> > > > 4) Lars may have more ideas?
> > > >
> > > > The plan is for me to start working on this stuff full time next week,
> > > > so if you think of anything more, please let me know!
> > >
> > > Haven't heard back from you about this. Have you found anything else
> > > that needs to be done with staging IIO drivers before they can be moved out?
> >
> > IIO is a bit problematic since testing usually requires possessing the
> > sensor chip
>
> Any specific chips / devices we should look into buying for these
> drivers to help make it easier to do development?
>
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.
Crystalfontz provided me some of their boards so that I could give them
out at ELC. If you are interested in the topic, it may be worth asking
whether they are willing to sponsor you ;)
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-06-19 12:54 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 [this message]
2014-06-20 20:42 ` Greg KH
2014-06-21 7:55 ` Alexandre Belloni
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=20140619125416.GT19375@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.