All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Jonathan Cameron <Jonathan.Cameron@gmail.com>
Cc: Dmitry Baryshkov <dbaryshkov@gmail.com>,
	linux-kernel@vger.kernel.org, cbou@mail.ru,
	Andrew Morton <akpm@linux-foundation.org>,
	Marek Vasut <marek.vasut@gmail.com>
Subject: Re: [PATCH] power_supply: change the way how wm97xx-bat driver is registered
Date: Mon, 3 Nov 2008 20:21:46 +0300	[thread overview]
Message-ID: <20081103172146.GA8913@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <490F2CE1.8070707@gmail.com>

On Mon, Nov 03, 2008 at 04:54:57PM +0000, Jonathan Cameron wrote:
[...]
> It is needlessly complex for this sort of thing, but that's not it's
> purpose.  (though that's not to say it won't be able to do this sort
> of thing).  It's gotten a smigeon delayed due to a change of my own
> requirements for what it does.  As a reminder, the purpose of that
> subsystem was at least partly to provide reasonably high performance
> data capture facilities (ring buffers, triggered sampling etc alongside
> suitably powerful userspace interfaces.)  Possibly my apps are somewhat
> unusual, but the complexity is absolutely necessary for what I'm doing
> (annoyingly!)

Yeah, I understand that. But when you need simple driver for very
simple ADC device, the subsystem is a bit scary. Maybe we could just
implement "simple API" on top of it, that would hide the complexity.

Something like

value = adc_sample_pin(adc_device, "voltage");

And

struct adc_pin pins[2];
pins[0].name = "x-axis";
pins[0].num_samples = 5;
pins[1].name = "y-axis";
pins[2].num_samples = 5;

adc_sample_pins(adc_device, pins);
for (i = 0; i < ARRAY_SIZE(pins); i++) {
	for (j = 0; j < pins[i].num_samples; i++)
		process(pins[i].values[j].value);
}

That would work for most in-kernel ADC users (batteries, touchscreens).

> Anyhow, definitely not given up on it.

Great, looking forward to your patches.

-- 
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2

  reply	other threads:[~2008-11-03 17:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-29  9:04 [PATCH] power_supply: only register tosa_battery driver on tosa Dmitry Baryshkov
2008-10-29  9:04 ` [PATCH] power_supply: change the way how wm97xx-bat driver is registered Dmitry Baryshkov
2008-11-02 20:36   ` Dmitry
2008-11-02 23:41     ` Marek Vasut
2008-11-03 15:11   ` Anton Vorontsov
2008-11-03 16:54     ` Jonathan Cameron
2008-11-03 17:21       ` Anton Vorontsov [this message]
2008-11-03 18:29     ` Dmitry Baryshkov
2008-11-03 19:34       ` Anton Vorontsov
2008-11-02 20:36 ` [PATCH] power_supply: only register tosa_battery driver on tosa Dmitry
2008-11-03 14:55   ` Anton Vorontsov
2008-11-03 16:20     ` Dmitry
2008-11-03 16:25       ` Anton Vorontsov
2008-11-03 16:41         ` Dmitry
2008-11-03 16:58           ` Anton Vorontsov
2008-11-03 17:09             ` Dmitry
2008-11-03 17:32               ` Anton Vorontsov
2008-11-03 18:14                 ` Dmitry
2008-11-03 17:41           ` Mark Brown

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=20081103172146.GA8913@oksana.dev.rtsoft.ru \
    --to=avorontsov@ru.mvista.com \
    --cc=Jonathan.Cameron@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=cbou@mail.ru \
    --cc=dbaryshkov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marek.vasut@gmail.com \
    /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.