From: Michael Welling <mwelling@ieee.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: lm-sensors@lm-sensors.org, linux-iio@vger.kernel.org,
Jonathan Cameron <jic23@kernel.org>
Subject: Re: ADS1018 ADC driver
Date: Mon, 21 Sep 2015 20:27:07 -0500 [thread overview]
Message-ID: <20150922012707.GA20799@deathstar> (raw)
In-Reply-To: <5600A924.1090303@roeck-us.net>
On Mon, Sep 21, 2015 at 06:04:36PM -0700, Guenter Roeck wrote:
> Hi Michael,
>
> On 09/21/2015 03:06 PM, Michael Welling wrote:
> >I am in the process of starting a new device driver for the ADS1018 ADC.
> >Before starting I did some research as whether similar drivers exist in the kernel.
> >
> >It appears that ADC drivers are in both hwmon and iio/adc. The closest drivers to
> >the device mentioned are in hwmon.
> >
> >Where is the best place for this new ADC driver?
>
> Your call. You could add support for the chip to hwmon/ads1015.c, or you could write
> a new driver in iio/adc. If you do the latter, maybe you can also include support
> for ads1015 and ads1115, so we can ultimately remove the ads1015 driver from hwmon.
Guenter,
Though the iio route may be more work I have a feeling the
driver will be better off there. The use of regmap support
should allow for both the SPI and I2C version to coexist.
I will try my best to implement the driver in a way that
can cover these other I2C devices mentioned.
>
> >Shouldn't ADCs all be in the same subsystem?
> >Has there been any effort to unify or distiguish where drivers should go?
> >
> In general, ADCs primarily used for the purpose of ADC measurements would go
> into iio, and ADCs used primarily for hardware monitoring would go into hwmon.
>
> There are no strict rules, though, and this is not always black-and-white.
> I am sure there are some drivers in hwmon which would be better suited for iio.
> Primarily that would be the case because the iio subsystem is relatively new,
> and such drivers did not have a home other than hwmon until a couple of years ago.
> If you find any drivers in hwmon which you think should be moved, please feel free
> to do the conversion.
Has anyone considered an alternative implementation for generic ADCs?
I was thinking about an implementation similar to gpiolib whereas ADCs can be
resources for other drivers.
For instance, ADC lines could be registered to a joystick driver and used to provide
analog stick or pressure sensitive button. Another example could be registering analog
lines for an analog accelerometer driver.
Is this a bad idea?
-Michael
>
> Guenter
>
next prev parent reply other threads:[~2015-09-22 1:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 22:06 ADS1018 ADC driver Michael Welling
2015-09-22 1:04 ` Guenter Roeck
2015-09-22 1:27 ` Michael Welling [this message]
2015-09-22 2:04 ` Guenter Roeck
2015-09-22 2:57 ` mwelling
[not found] ` <131939B9-E3B7-4E98-B0E2-7DF8F2C081BC@jic23.retrosnub.co.uk>
2015-09-23 7:45 ` Michael Welling
2015-10-20 17:16 ` Michael Welling
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=20150922012707.GA20799@deathstar \
--to=mwelling@ieee.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lm-sensors@lm-sensors.org \
/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).