From: Frank Crawford <frank@crawford.emu.id.au>
To: Jean Delvare <jdelvare@suse.com>, Guenter Roeck <linux@roeck-us.net>
Cc: linux-hwmon@vger.kernel.org, Frank Crawford <frank@crawford.emu.id.au>
Subject: [PATCH v1 0/4] hwmon: (it87) Add access control for SMBus
Date: Sun, 9 Apr 2023 13:47:14 +1000 [thread overview]
Message-ID: <20230409034718.1938695-1-frank@crawford.emu.id.au> (raw)
Some chips support Environmental Controller access through SMBus.
On those chips, it is possible that an Embedded Controller accesses
Environmental Controller chip registers at any time. There is no real
means for synchronization. On banked chips, this can and will result in
access errors with unpredictable result.
Disable SMBus access while reading or writing environmental controller
registers to work around the problem.
---
Frank Crawford (4):
Some chips support Environmental Controller access through SMBus.
Disable SMBus access while reading or writing environmental
controller registers.
Add calls to smbus_enable/smbus_disable as required.
Test for error in call to it87_update_device and return error.
Disable/enable SMBus access for IT8622E chipset.
drivers/hwmon/it87.c | 288 +++++++++++++++++++++++++++++++++++--------
1 file changed, 240 insertions(+), 48 deletions(-)
--
2.39.2
next reply other threads:[~2023-04-09 3:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-09 3:47 Frank Crawford [this message]
2023-04-09 3:47 ` [PATCH v1 1/4] hwmon: (it87) Disable SMBus access for environmental controller registers Frank Crawford
2023-04-09 3:47 ` [PATCH v1 2/4] hwmon: (it87) Add calls to smbus_enable/smbus_disable as required Frank Crawford
2023-04-12 18:44 ` Guenter Roeck
2023-04-09 3:47 ` [PATCH v1 3/4] hwmon: (it87) Test for error in it87_update_device Frank Crawford
2023-04-12 18:46 ` Guenter Roeck
2023-04-09 3:47 ` [PATCH v1 4/4] hwmon: (it87) Disable/enable SMBus access for IT8622E chipset Frank Crawford
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=20230409034718.1938695-1-frank@crawford.emu.id.au \
--to=frank@crawford.emu.id.au \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@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;
as well as URLs for NNTP newsgroup(s).