All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>, Peter Meerwald <pmeerw@pmeerw.net>
Cc: "Kristina Martšenko" <kristina.martsenko@gmail.com>,
	linux-iio@vger.kernel.org, "Lars-Peter Clausen" <lars@metafoo.de>
Subject: Re: IIO drivers left in drivers/staging/
Date: Wed, 18 Jun 2014 20:45:50 +0100	[thread overview]
Message-ID: <53A1EC6E.3010606@kernel.org> (raw)
In-Reply-To: <53A1D534.9090105@kernel.org>

On 18/06/14 19:06, Jonathan Cameron wrote:
> On 18/06/14 18:47, 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?
On that note, perhaps ask for people to shout what they have access
to and we'll see what is left.

Of stuff still in staging I have:
* lis3l02dq (it's there because we probably want to add this part to the
   much more general st-sensors driver rather than moving it out as is).
* sca3000 (still there because we now have a better idea of how to handle
   chips with hardware buffers - route them through a software buffer,
   dropping the explicit trigger as done in the am35x driver last summer).

J

>>
>>> regarding staging/iio/magnetometer/hmc5843:
>>> the driver has one specific DEVICE_ATTR left (meas_conf), otherwise clean
>>> I think; so we could (a) document it as special ABI or (b) drop it
>>
>> Which is it?  It should be easy to delete a driver :)
> Drop the attribute, not the driver!
>>
>> thanks,
>>
>> greg k-h
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2014-06-18 19:43 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 [this message]
2014-06-19 12:54           ` Alexandre Belloni
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=53A1EC6E.3010606@kernel.org \
    --to=jic23@kernel.org \
    --cc=gregkh@linuxfoundation.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.