All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Kean Ren" <rh_king@163.com>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH 1/1] hwmon: (spd5118) support write protected devices
Date: Sun, 20 Sep 2026 06:30:02 +0000	[thread overview]
Message-ID: <20260920063002.DC96E1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260920062230.2437291-1-rh_king@163.com>

> Some systems do not allow writes to SPD devices. On the i801 SMBus
> controller family this happens when the BIOS sets SPD Write Disable, in
> which case the controller refuses writes to addresses 0x50-0x57; other
> platforms may enforce the same in firmware. There is no way for the driver
> to query this.
> 
> spd5118 assumes that it can write to the device, which does not hold on
> such systems:
> 
>   - writes to the hwmon attributes always fail with -ENXIO
>   - the temperature sensor disable in spd5118_suspend() fails silently
>   - spd5118_resume() fails in regcache_sync(), and the system reports
> 
>   spd5118 0-0050: Failed to write b = 0: -6
>   spd5118 0-0050: PM: failed to resume async: error -6
> [ ... ]
> becomes read-only. Document that, and leave the shared regmap
> configuration alone by selecting a separate one without a register
> cache.
> 
> Signed-off-by: Kean Ren <rh_king@163.com>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260920062230.2437291-2-rh_king@163.com?part=1


  parent reply	other threads:[~2026-09-20  6:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-20  6:22 [PATCH 1/1] hwmon: (spd5118) support write protected devices Kean Ren
2026-09-20  6:22 ` [PATCH 0/1] " Kean Ren
2026-09-20  6:30 ` sashiko-bot [this message]
2026-09-21 14:16 ` [PATCH 1/1] " Guenter Roeck
2026-09-22  2:31   ` Kean Ren

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=20260920063002.DC96E1F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=rh_king@163.com \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.