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 -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
