From: Guenter Roeck <linux@roeck-us.net>
To: Michael Welling <mwelling@ieee.org>,
Daniel Baluta <daniel.baluta@intel.com>
Cc: jic23@kernel.org, knaack.h@gmx.de, lars@metafoo.de,
pmeerw@pmeerw.net, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org, lucas.demarchi@intel.com,
eibach@gdsys.de
Subject: Re: [PATCH] iio: adc: Add TI ADS1015 ADC driver support
Date: Thu, 14 Jan 2016 09:34:34 -0800 [thread overview]
Message-ID: <5697DC2A.5000801@roeck-us.net> (raw)
In-Reply-To: <20160114165133.GA20246@deathstar>
On 01/14/2016 08:51 AM, Michael Welling wrote:
> On Thu, Jan 14, 2016 at 06:25:08PM +0200, Daniel Baluta wrote:
>> The driver has sysfs readings with runtime PM support for power saving.
>> It also offers buffer support that can be used together with IIO software
>> triggers.
>>
>
> It should be noted that the hwmon driver subsystem has support for this device.
>
> http://lxr.free-electrons.com/source/drivers/hwmon/ads1015.c
>
> The driver could likely be removed if this is accepted into iio.
> The hwmon subsystem has an iio wrapper driver.
>
> http://lxr.free-electrons.com/source/drivers/hwmon/iio_hwmon.c
>
> The only hurdle is adding support for the ads1115 before removing the other driver.
>
Yes, plus one would hope that there are not going to be a different set of
devicetree properties associated with the new driver, and that the new driver
will support (at least) the same properties.
You'll also have to make sure that only one of the two drivers can be selected.
Guenter
next prev parent reply other threads:[~2016-01-14 17:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 16:25 [PATCH] iio: adc: Add TI ADS1015 ADC driver support Daniel Baluta
2016-01-14 16:51 ` Michael Welling
2016-01-14 17:04 ` Lars-Peter Clausen
2016-01-14 17:34 ` Guenter Roeck [this message]
2016-01-16 12:07 ` Jonathan Cameron
2016-01-27 16:31 ` Daniel Baluta
2016-01-27 17:23 ` Jonathan Cameron
2016-01-26 22:28 ` Lucas De Marchi
2016-01-27 9:49 ` Daniel Baluta
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=5697DC2A.5000801@roeck-us.net \
--to=linux@roeck-us.net \
--cc=daniel.baluta@intel.com \
--cc=eibach@gdsys.de \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=mwelling@ieee.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.