From: Michael Walle <michael@walle.cc>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-hwmon@vger.kernel.org, Jean Delvare <jdelvare@suse.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC,2/2] hwmon: adt7411: add min, max and alarm attributes
Date: Mon, 21 Nov 2016 17:53:01 +0100 [thread overview]
Message-ID: <3353d7477aec9b78fb6e5aa3f145fec1@walle.cc> (raw)
In-Reply-To: <20161119180552.GA27002@roeck-us.net>
Am 2016-11-19 19:05, schrieb Guenter Roeck:
> Hi Michael,
>
> On Fri, Oct 14, 2016 at 11:43:35AM +0200, Michael Walle wrote:
>> This patch adds support for the min, max and alarm attributes of the
>> voltage and temperature channels. Additionally, the temp2_fault
>> attribute
>> is supported which indicates a fault of the external temperature
>> diode.
>>
>> Signed-off-by: Michael Walle <michael@walle.cc>
>
> Sorry for the late reply. Mostly looks ok.
> Couple of comments below.
thanks for the review. I will send an updated version, soon.
[snip]
>> +static int adt7411_write_temp(struct device *dev, u32 attr, int
>> channel,
>> + long val)
>> +{
>> + struct adt7411_data *data = dev_get_drvdata(dev);
>> + struct i2c_client *client = data->client;
>> + int reg;
>> +
>> + val = DIV_ROUND_CLOSEST(val, 1000);
>> + val = clamp_val(val, -128, 127);
>> + val = val < 0 ? 0x100 + val : val;
>
> Does this add any value ? It doesn't change the low byte.
mh? if val is negative 256 will be added.
>> static umode_t adt7411_is_visible(const void *_data,
>> enum hwmon_sensor_types type,
>> u32 attr, int channel)
>> {
>> const struct adt7411_data *data = _data;
>> + bool visible;
>>
>> switch (type) {
>> case hwmon_in:
>> - if (channel > 0 && channel < 3)
>> - return data->use_ext_temp ? 0 : S_IRUGO;
>> - else
>> - return S_IRUGO;
>> + visible = channel == 0 || channel >= 2 || !data->use_ext_temp;
>
> in2 is now visible even if external temperature is measured.
> This is not correct. Yes, one can read the register, but the
> external pin (AIN2) is connected to the temperature sensor.
i guess
visible = channel == 0 || channel >= 3 || !data->use_ext_temp;
makes more sense.
-michael
next prev parent reply other threads:[~2016-11-21 16:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 9:43 [RFC PATCH 1/2] hwmon: adt7411: update to new hwmon registration API Michael Walle
2016-10-14 9:43 ` [RFC PATCH 2/2] hwmon: adt7411: add min, max and alarm attributes Michael Walle
2016-11-19 18:05 ` [RFC,2/2] " Guenter Roeck
2016-11-21 16:53 ` Michael Walle [this message]
2016-11-21 20:35 ` Guenter Roeck
2016-11-19 20:54 ` Guenter Roeck
2016-11-19 21:01 ` Guenter Roeck
2016-11-10 13:04 ` [RFC PATCH 1/2] hwmon: adt7411: update to new hwmon registration API Michael Walle
2016-11-10 15:46 ` Guenter Roeck
2016-11-19 17:31 ` [RFC,1/2] " Guenter Roeck
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=3353d7477aec9b78fb6e5aa3f145fec1@walle.cc \
--to=michael@walle.cc \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.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
all inboxes | Powered by JetHome®