From: Guenter Roeck <linux@roeck-us.net>
To: Rob Herring <robh@kernel.org>
Cc: Joel Stanley <joel@jms.id.au>, Rick Altherr <raltherr@google.com>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, jdelvare@suse.com,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] hwmon: Aspeed AST2400/AST2500 ADC
Date: Sun, 5 Mar 2017 08:14:57 -0800 [thread overview]
Message-ID: <adbb9c99-d4dc-d5d7-2f44-be835aa51f0a@roeck-us.net> (raw)
In-Reply-To: <20170303062133.dvt5g32n26gqio52@rob-hp-laptop>
On 03/02/2017 10:21 PM, Rob Herring wrote:
> On Tue, Feb 28, 2017 at 07:45:23PM -0800, Guenter Roeck wrote:
>> On 02/28/2017 04:49 PM, Joel Stanley wrote:
>>> On Wed, Mar 1, 2017 at 6:44 AM, Rick Altherr <raltherr@google.com> wrote:
>>>> Aspeed AST2400/AST2500 BMC SoCs include a 16 channel, 10-bit ADC. This
>>>> driver implements reading the ADC values, enabling channels via device
>>>> tree, and optionally providing channel labels via device tree. Low and
>>>> high threshold interrupts are supported by the hardware but not
>>>> implemented.
>>>>
>>>> Signed-off-by: Rick Altherr <raltherr@google.com>
>>>
>>> Looks good. Some minor comments below.
>>>
>>> Is there a reason you wrote a hwmon driver instead of an iio driver? I
>>> wasn't sure what the recommended subsystem is.
>>
>> Excellent point. Question is really if there is a plan to add support for
>> thresholds. If not, an iio driver might be more appropriate.
>
> Sigh. We have ADCs in 2 places? Fine for the kernel I guess, but not
> bindings.
>
Almost every {voltage, current, power, temperature} sensor chip is implemented
as ADC. Given that, we have (at least) three places. hwmon, iio, thermal.
Guenter
next prev parent reply other threads:[~2017-03-05 16:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 20:14 [PATCH 1/2] Documentation: dt-bindings: Document bindings for " Rick Altherr
2017-02-28 20:14 ` [PATCH 2/2] hwmon: " Rick Altherr
2017-03-01 0:49 ` Joel Stanley
2017-03-01 3:45 ` Guenter Roeck
2017-03-02 3:29 ` Rick Altherr
2017-03-05 16:28 ` Guenter Roeck
2017-03-07 23:24 ` Rick Altherr
2017-03-03 6:21 ` Rob Herring
2017-03-05 16:14 ` Guenter Roeck [this message]
2017-03-01 0:50 ` [PATCH 1/2] Documentation: dt-bindings: Document bindings for " Joel Stanley
2017-03-03 6:21 ` Rob Herring
2017-03-06 22:01 ` Rick Altherr
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=adbb9c99-d4dc-d5d7-2f44-be835aa51f0a@roeck-us.net \
--to=linux@roeck-us.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=joel@jms.id.au \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=raltherr@google.com \
--cc=robh@kernel.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
all inboxes | Powered by JetHome®