From: Tinsae Tadesse <tinsaetadesse2015@gmail.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Jean Delvare <jdelvare@suse.com>,
Andi Shyti <andi.shyti@kernel.org>,
Guenter Roeck <linux@roeck-us.net>
Cc: Tinsae Tadesse <tinsaetadesse2015@gmail.com>,
linux-i2c@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] i2c: i801: Detect SPD Write Disable and expose as adapter quirk
Date: Thu, 5 Feb 2026 13:29:23 +0300 [thread overview]
Message-ID: <20260205102942.28745-1-tinsaetadesse2015@gmail.com> (raw)
Hi I2C and HWMON maintainers,
Intel i801 SMBus controllers feature a "SPD Write Disable" bit
in the SMBHSTCFG register. When set by firmware, the hardware
silently blocks all write transactions to the SPD EEPROM
address range (0x50-0x57) while allowing reads to succeed.
This creates a significant issue for the spd5118 hwmon driver.
The SPD5118 requires write access for switching between
register pages to read temperature data, and for cache
synchronization during suspend/resume. When SPD Write Disable
is set and the spd5118 driver attempts write transactions, the
bus will generate a storm of SMBus DEV_ERR messages.
This patch series proposes a generic solution by:
1. Introducing a new adapter quirk flag in include/linux/i2c.h
to communicate this hardware restriction.
2. Modifying drivers/i2c/i2c-i801.c to detect the SPD Write
Disable bit and set the quirk flag.
3. Modifying drivers/hwmon/spd5118.c to check for this quirk
during probe and fail cleanly, as write access is mandatory.
By using this mechanism, we avoid embedding device-specific
policies in the controller driver and provide client drivers
with the necessary information to make an informed decision.
Tinsae Tadesse (2):
i2c: i801: Detect SPD Write Disable and expose as adapter quirk
hwmon: spd5118: Fail probe if SPD writes are disabled
drivers/hwmon/spd5118.c | 15 +++++++++++++++
drivers/i2c/busses/i2c-i801.c | 16 +++++++++++++++-
include/linux/i2c.h | 3 +++
3 files changed, 33 insertions(+), 1 deletion(-)
--
2.52.0
next reply other threads:[~2026-02-05 10:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 10:29 Tinsae Tadesse [this message]
2026-02-05 10:29 ` [PATCH 1/2] " Tinsae Tadesse
2026-06-08 12:28 ` Andi Shyti
2026-06-10 8:54 ` TINSAE TADESSE
2026-06-11 4:35 ` Guenter Roeck
2026-02-05 10:29 ` [PATCH 2/2] hwmon: spd5118: Fail probe if SPD writes are disabled Tinsae Tadesse
2026-02-05 13:46 ` Guenter Roeck
2026-02-21 9:57 ` [PATCH 0/2] i2c: i801: Detect SPD Write Disable and expose as adapter quirk TINSAE TADESSE
2026-04-21 17:56 ` Mark Pearson
2026-04-23 11:21 ` TINSAE TADESSE
2026-05-04 21:41 ` Mark Pearson
2026-06-30 7:06 Delaida Muminović
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=20260205102942.28745-1-tinsaetadesse2015@gmail.com \
--to=tinsaetadesse2015@gmail.com \
--cc=andi.shyti@kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wsa+renesas@sang-engineering.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
all inboxes | Powered by JetHome®