From: Linus Walleij <linus.ml.walleij@gmail.com>
To: Jonathan Cameron <kernel@jic23.retrosnub.co.uk>
Cc: arjun rath <rath.arjun@gmail.com>,
spi-devel-general@lists.sourceforge.net,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [spi-devel-general] SPI-ADC
Date: Sat, 13 Feb 2010 22:20:06 +0100 [thread overview]
Message-ID: <63386a3d1002131320u5afbc35ak2bc3533aab3f1e54@mail.gmail.com> (raw)
In-Reply-To: <4B76D8AE.7040102@jic23.retrosnub.co.uk>
2010/2/13 Jonathan Cameron <kernel@jic23.retrosnub.co.uk>:
>>> can anybody share how to start a spi based ADC linux driver.I am having a
>>> MAXIM 1242 ADC chip.
>>
>> The ḱernel does not contain any generic ADC subsystem abstraction
>> (...)
>
> That's not entirely true. These are covered by the IIO subsystem which
> is admittedly currently in staging as some elements still need cleaning up.
> (...)
> ADC drivers are under drivers/staging/iio/adc.
Great stuff. I knew about IIO and then it fell out of my mind, how
could I...
What strikes me especially about IIO is the underlying assumption, which I
think ought to be written in clear somewhere where I missed it, and that
is that all IIO drivers are supposed to deliver values and be controller from
userspace with this nice ABI, and nothing's wrong with that of course.
But I'm hinting about a few in-kernel uses: for AB3100 we have a battery
charging mechanism, which use a (calibrated) ADC value supporting the
bulk of the driver in the power/ subsystem.
As it looks today IIO is not intended for the case where another subsystem
needs to grab and use and ADC for its own purposes. Is this correct or did
I get it all wrong?
Would you say it'd be a good idea to hack the IIO ADC interface (for
example) to be used also internally in the kernel, or would that violate
the idea behind IIO?
If these are disparate categories it would warrant a separate adc/
subsystem, see.
> Currently all discussions take place on LKML, but we are working on a more
> focused alternative list which I'll announce once it is sorted out.
LKML is just fine with me, for one.
Yours,
Linus Walleij
next prev parent reply other threads:[~2010-02-13 21:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-13 5:48 SPI-ADC arjun rath
[not found] ` <dc6d3181002122148v6451ebffka164de288738485d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-02-13 6:38 ` SPI-ADC Ben Gamari
2010-02-13 13:48 ` [spi-devel-general] SPI-ADC Linus Walleij
2010-02-13 16:51 ` Jonathan Cameron
2010-02-13 17:03 ` Mike Frysinger
2010-02-13 21:20 ` Linus Walleij [this message]
[not found] ` <63386a3d1002131320u5afbc35ak2bc3533aab3f1e54-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-02-15 4:29 ` SPI-ADC arjun rath
[not found] ` <dc6d3181002142029j13a9e57la45aa90a269404fa-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-02-15 8:49 ` SPI-ADC jassi brar
2010-02-15 17:33 ` SPI-ADC Ben Gamari
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=63386a3d1002131320u5afbc35ak2bc3533aab3f1e54@mail.gmail.com \
--to=linus.ml.walleij@gmail.com \
--cc=kernel@jic23.retrosnub.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rath.arjun@gmail.com \
--cc=spi-devel-general@lists.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).