From: Peter Hung <hpeter@gmail.com>
To: jdelvare@suse.de, linux@roeck-us.net
Cc: lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org,
tom_tsai@fintek.com.tw, peter_hong@fintek.com.tw,
Peter Hung <hpeter+linux_kernel@gmail.com>
Subject: [PATCH V3 0/3] hwmon:f71882fg add new Fintek SuperIO support
Date: Tue, 7 Jul 2015 16:22:35 +0800 [thread overview]
Message-ID: <1436257358-31360-1-git-send-email-hpeter+linux_kernel@gmail.com> (raw)
The first patch will add Fintek F81866/F71868 SuperIO
with H/W monitor function to f71882fg.c.
But some F81866 functional address is differ from F71882fg.
The following 2 patches will fix this problem.
The test report is upload to following link. If I lost something,
with test, please let me know. I'll append it to the report.
Here is F81866 on customer MB report:
https://drive.google.com/file/d/0B8vRwwYO7aMFUmliSFVWVVRUaTA/view?pli=1
Cause we had no F71868 MB currently, we just check and mapping
register to driver.
Changelog:
V3
1. Fix fatal compile error. (Thanks to Guenter Roeck)
2. Fix array size and content not match error.
(Thanks to Dan Carpenter)
V2
1. Fix comments by Guenter Roeck <linux@roeck-us.net>
all newer add IC should keep chip IDs in numeric order.
Peter Hung (3):
hwmon:f71882fg add f81866/f71868 SuperIO support
hwmon:f71882fg fix f81866a temp/beep setting
hwmon:f71882fg fix f81866a voltage protection
drivers/hwmon/f71882fg.c | 163 +++++++++++++++++++++++++++++++++++++----------
1 file changed, 131 insertions(+), 32 deletions(-)
--
1.9.1
next reply other threads:[~2015-07-07 8:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 8:22 Peter Hung [this message]
2015-07-07 8:22 ` [PATCH V3 1/3] hwmon:f71882fg add f81866/f71868 " Peter Hung
2015-07-07 8:22 ` [PATCH V3 2/3] hwmon:f71882fg fix f81866a temp/beep setting Peter Hung
2015-07-07 8:22 ` [PATCH V3 3/3] hwmon:f71882fg fix f81866a voltage protection Peter Hung
2015-07-07 19:32 ` [PATCH V3 0/3] hwmon:f71882fg add new Fintek SuperIO support 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=1436257358-31360-1-git-send-email-hpeter+linux_kernel@gmail.com \
--to=hpeter@gmail.com \
--cc=hpeter+linux_kernel@gmail.com \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lm-sensors@lm-sensors.org \
--cc=peter_hong@fintek.com.tw \
--cc=tom_tsai@fintek.com.tw \
/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
Powered by JetHome