All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Brigham Campbell" <me@brighamcampbell.com>
To: "Wolfram Sang" <wsa+renesas@sang-engineering.com>,
	"Brigham Campbell" <me@brighamcampbell.com>
Cc: "Stephen Horvath" <s.horvath@outlook.com.au>,
	linux-i2c@vger.kernel.org, "Jean Delvare" <jdelvare@suse.com>,
	"Benoît Monin" <benoit.monin@bootlin.com>
Subject: Re: [PATCH i2c-tools] TODO: add file and describe items for the 4.5 release
Date: Tue, 07 Jul 2026 21:41:46 -0600	[thread overview]
Message-ID: <DJSVN4OMOMB7.EBB9SV2PLWTR@brighamcampbell.com> (raw)
In-Reply-To: <akzuG3VpcoUWRhUr@shikoro>

On Tue Jul 7, 2026 at 6:16 AM MDT, Wolfram Sang wrote:
> You might try busses 0 and 1, too. Some laptops use the Synopsis
> controller.

No such luck, apparently. Busses 0 and 1 each report no devices
attached.

$ sudo i2cdetect -y 0
Warning: Can't use SMBus Quick Write command, will skip some addresses
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:
10:
20:
30: -- -- -- -- -- -- -- --
40:
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60:
70:

Instructing i2cdetect to instead probe using SMBus receive byte shows
the full range, with no devices on synopsis bus 1, but one device bound
to a driver on synopsis 0:

$ sudo i2cdetect -yr 0
[sudo] password for brigham:
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

It looks like it's bound to i2c_hid_acpi. No ddr5 temperature sensors in
sight...

> How many? If it is in the 120 range, then every access from i2cdetect
> fails with it.

When I run i2cdetect on the i801 controller, on one invocation I count
111 repetitions of the "SMBus is busy, can't use it!" error once, then
on another invocation I count 112 repetitions. The error condition
appears to be encountered very frequently, but not quite every time.
When the kernel's i2c bus arbitration retry logic kicks in, it appears
to be able to eventually complete the operation successfully before the
i2c core driver code gives up because otherwise I would expect i2cdetect
to exit prematurely and report an error.

Wolfram, if you or any other kernel developers think this may be
indicative of some underlying issue, I'm happy to investigate further
and report back. I'm using a Dell XPS 14 DA14260 laptop.

Cheers!
-- 
Brigham Campbell
https://brighamcampbell.com


  reply	other threads:[~2026-07-08  3:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-05 18:10 [PATCH i2c-tools] TODO: add file and describe items for the 4.5 release Wolfram Sang
2026-07-06  4:45 ` Brigham Campbell
2026-07-06  5:19   ` Stephen Horvath
2026-07-06  6:33     ` Brigham Campbell
2026-07-07 12:16       ` Wolfram Sang
2026-07-08  3:41         ` Brigham Campbell [this message]
2026-07-08  8:38           ` Wolfram Sang
2026-07-08 11:10             ` Andy Shevchenko
2026-07-06  8:04 ` Benoît Monin
2026-07-07 11:51 ` Wolfram Sang

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=DJSVN4OMOMB7.EBB9SV2PLWTR@brighamcampbell.com \
    --to=me@brighamcampbell.com \
    --cc=benoit.monin@bootlin.com \
    --cc=jdelvare@suse.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=s.horvath@outlook.com.au \
    --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 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.