From: Guenter Roeck <linux@roeck-us.net>
To: Chu Lin <linchuyuan@google.com>
Cc: belgaied@google.com, jasonling@google.com, jdelvare@suse.com,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
zhongqil@google.com
Subject: Re: [PATCH v3 0/1] hwmon:max6697: Allow max6581 to create tempX_offset
Date: Mon, 6 Jul 2020 20:03:22 -0700 [thread overview]
Message-ID: <46c25347-a9d9-3997-9aaa-7393cfccb4f7@roeck-us.net> (raw)
In-Reply-To: <20200707011810.2508233-1-linchuyuan@google.com>
On 7/6/20 6:18 PM, Chu Lin wrote:
> Per max6581, reg 4d and reg 4e is used for temperature read offset.
> This patch will let the user specify the temperature read offset for
> max6581. This patch is tested on max6581 and only applies to max6581.
>
Since this is a single patch, you don't need patch 0.
Just add the change log after "---" to the actual patch.
Thanks,
Guenter
> Testing:
> echo 16250 > temp2_offset
> cat temp2_offset
> 16250
>
> echo 17500 > temp3_offset
> cat temp3_offset
> 17500
> cat temp4_offset
> 0
> cat temp2_offset
> 17500
>
> echo 0 > temp2_offset
> cat temp2_offset
> 0
> cat temp3_offset
> 17500
>
> echo -0 > temp2_offset
> cat temp2_offset
> 0
>
> echo -100000 > temp2_offset
> cat temp2_input
> 4875
>
> echo 10000 > temp2_offset
> cat temp2_input
> 47125
>
> echo -2000 > temp2_offset
> cat temp2_input
> 34875
>
> echo -0 > temp2_offset
> cat temp2_input
> 37000
>
> Signed-off-by: Chu Lin <linchuyuan@google.com>
> ---
> ChangeLog v2 -> v3:
> - Use reverse christmas tree order convension
> - Fix the type issue where comparision is always true
> - Change the line limit to 100 char instead of 80 char
>
> ChangeLog v1 -> v2:
> - Simplify the offset reg raw value to milli ceisus conversion
> - Substitute the temp1_offset with dummy attr
> - Avoid using double negative in the macro definition
> - Return the actual error when i2c read/write is failed
> - clamp the value to MAX or MIN respectively if an out of range input is given
> - Provide mux protection when multiple i2c accesses is required
>
> Chu Lin (1):
> hwmon:max6697: Allow max6581 to create tempX_offset attributes
>
> drivers/hwmon/max6697.c | 92 +++++++++++++++++++++++++++++++++++++++--
> 1 file changed, 88 insertions(+), 4 deletions(-)
>
prev parent reply other threads:[~2020-07-07 3:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 1:18 [PATCH v3 0/1] hwmon:max6697: Allow max6581 to create tempX_offset Chu Lin
2020-07-07 1:18 ` [PATCH v3 1/1] hwmon:max6697: Allows max6581 to create tempX_offset attributes Chu Lin
2020-07-07 3:01 ` Guenter Roeck
2020-07-07 3:03 ` Guenter Roeck [this message]
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=46c25347-a9d9-3997-9aaa-7393cfccb4f7@roeck-us.net \
--to=linux@roeck-us.net \
--cc=belgaied@google.com \
--cc=jasonling@google.com \
--cc=jdelvare@suse.com \
--cc=linchuyuan@google.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhongqil@google.com \
/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).