From: Guenter Roeck <linux@roeck-us.net>
To: Luca Carlon <carlon.luca@gmail.com>, w_armin@gmx.de
Cc: jdelvare@suse.com, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org, lucas.demarchi@intel.com
Subject: Re: Suspend/resume failing due to SPD5118
Date: Sun, 4 May 2025 16:31:31 -0700 [thread overview]
Message-ID: <310fe3a3-e585-46e0-aae7-3e4d41af1f53@roeck-us.net> (raw)
In-Reply-To: <20250504184117.4795-1-carlon.luca@gmail.com>
On 5/4/25 11:41, Luca Carlon wrote:
...
> When I was told that the problem may lie in the i2c bus, I started to search elsewhere
> and this thread came up: https://bugzilla.kernel.org/show_bug.cgi?id=213345. I
> therefore provided in that thread some more info I collected.
>
From there:
[ 5.416572] i801_smbus 0000:00:1f.4: SPD Write Disable is set
I think you are out of luck. The above is incompatible with spd5118 devices;
See [1] for details. I don't immediately see why that would cause the i2c bus
to lock up, but even if it didn't lock up the bus I don't see a means to get
this to work.
It is still puzzling that reading the i2c data using i2cdump fails. The spd5118
driver should not even probe if that is the case. Maybe Armin has an idea.
Guenter
---
[1] https://lore.kernel.org/linux-i2c/20250430-for-upstream-i801-spd5118-no-instantiate-v2-0-2f54d91ae2c7@canonical.com/
next prev parent reply other threads:[~2025-05-04 23:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 22:59 Suspend/resume failing due to SPD5118 Lucas De Marchi
2024-12-20 1:20 ` Guenter Roeck
2025-05-02 23:07 ` carlon.luca
2025-05-02 23:51 ` Armin Wolf
2025-05-03 0:33 ` Luca Carlon
2025-05-03 0:14 ` Guenter Roeck
2025-05-03 0:58 ` Luca Carlon
2025-05-03 1:40 ` Guenter Roeck
2025-05-04 16:59 ` Armin Wolf
2025-05-04 18:41 ` Luca Carlon
2025-05-04 23:31 ` Guenter Roeck [this message]
2025-05-05 0:27 ` Armin Wolf
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=310fe3a3-e585-46e0-aae7-3e4d41af1f53@roeck-us.net \
--to=linux@roeck-us.net \
--cc=carlon.luca@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=w_armin@gmx.de \
/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