mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	mingo@elte.hu, linux-kernel@vger.kernel.org,
	Jonathan Cameron <jic23@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH RESEND] x86, intel_mid: ADC management
Date: Wed, 11 Apr 2012 07:19:01 +0100	[thread overview]
Message-ID: <e65fbfb8-1169-46dc-aad9-1dc9dbb91e8f@email.android.com> (raw)
In-Reply-To: <20120410223722.GY7499@opensource.wolfsonmicro.com>



Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:

>On Tue, Apr 10, 2012 at 08:39:40PM +0100, Jonathan Cameron wrote:
>
>> 1)  Review of code.  This is crucial. If people have a little time
>> ripping holes in the core IIO code is what we need.  Arnd did a good
>job
>> of this a while back. Others have done bits of it since.
>
>> 2) Getting the push code tidied up and pushed out.  I'll post it as
>an
>> updated rfc to linux-iio shortly.  All I had left that definitely
>> wanted doing here was cleaning up the example iio to input bridge
>> driver.  That can happen later.
>
>For these two can we refactor in place?  That's pretty much what seems
>to have been happening anyway...
>
I guess it comes down to whether Linus will pull.  2 should be there within a week or so anyway depending mostly on analog testing I haven't broken any of their drivers.
>> * Event passing to consumers else where in the kernel. Right now an
>> input driver can readings from a sensor, but there is no way of
>> requesting threshold interrupts.
>
>> * Interaction between consumer drivers (e.g. hwmon or input) where
>some
>> are requesting data by polling when they want it and others want a
>
>These sound like something that can be added incrementally?
>
>> > If the code was moved out of staging today what would go wrong?
>
>> Churn in interfaces is probably about it.  Maybe a good use of any
>time
>
>I guess the big question is then if we can live with that.

Agreed.  
>> would be for people to take their non IIO drivers that they think
>might
>> fit (or data sheets!) and see whether there are things that they
>would
>> like to be different.
>
>In tree there's a few auxadc and comparator drivers in drivers/mfd,
>plus
>things like arch/arm/plat-samsung/adc.c in the arch direcories.  These
>are all broadly similar to the at91 code that's been sent to IIO
>already.  There's also the code Alan posted at the top of this thread.
Quite a lot of things in miscellaneous as well to possibly pull in over time.



-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

  reply	other threads:[~2012-04-11  6:19 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10 13:20 Alan Cox
2012-04-10 13:12 ` Mark Brown
2012-04-10 13:25   ` Alan Cox
2012-04-10 13:33     ` Mark Brown
2012-04-10 13:42       ` Alan Cox
2012-04-10 14:07         ` Mark Brown
2012-04-10 14:15           ` Alan Cox
2012-04-10 15:19             ` Mark Brown
2012-04-10 16:56               ` Alan Cox
2012-04-10 17:58                 ` Mark Brown
2012-04-10 19:39                   ` Jonathan Cameron
2012-04-10 22:37                     ` Mark Brown
2012-04-11  6:19                       ` Jonathan Cameron [this message]
2012-04-11  7:44                         ` Jonathan Cameron
2012-04-11 15:38                         ` Greg Kroah-Hartman
2012-04-11 16:30                           ` Jonathan Cameron
2012-04-11 23:46                             ` Greg Kroah-Hartman
2012-04-12  6:25                               ` Jonathan Cameron
2012-04-11 10:24                   ` Alan Cox
2012-04-11 10:38                     ` Mark Brown
2012-04-11 10:48                       ` Jonathan Cameron
2012-04-11 11:13                         ` Alan Cox
2012-04-11 11:19                           ` Jonathan Cameron
2012-04-11 12:30                             ` Alan Cox
2012-04-11 12:55                               ` Jonathan Cameron
2012-04-12 17:53                               ` Mark Brown
2012-04-12 18:04                             ` Mark Brown
2012-04-11 11:38                     ` Jonathan Cameron

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=e65fbfb8-1169-46dc-aad9-1dc9dbb91e8f@email.android.com \
    --to=jic23@cam.ac.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®