[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220517100505.2569874-1-suichen@google.com>
Date: Tue, 17 May 2022 03:05:04 -0700
From: Sui Chen <suichen@...gle.com>
To: linux-kernel@...r.kernel.org, linux-i2c@...r.kernel.org,
wsa@...nel.org, openbmc@...ts.ozlabs.org, tali.perry1@...il.com
Cc: joel@....id.au, andrew@...id.au, benjaminfair@...gle.com,
krellan@...gle.com, Sui Chen <suichen@...gle.com>
Subject: [RFC Patch v5 0/1] i2c: core: Adapter and client stats as sysfs attributes
This change adds statistics to the i2c_adapter structure as Wolfram
previously suggested
(https://lore.kernel.org/linux-i2c/YgEYEk355t8C4J1x@shikoro/).
It also adds relevant statistics to the per-address i2c_clients where
applicable.
The list of statistics are:
- bus_errors
- nacks
- recovery_successes / recovery_failures (only applicable to
i2c_adapter)
- timeouts
- messages (only applicable to i2c_client)
- transfers (only applicable to i2c_adapter)
The statistics are located in /sys/class/i2c-adapter/i2c-x/stats and
/sys/class/i2c-adapter/i2c-x/x-xxxx/stats respectively.
Since the counting is done in __i2c_transfer, where the number of
messages transferred is not known upon error, the error counters are
attributed to all unique addresses that appear in the message list
passed into __i2c_transfer.
Currently an rbtree is used to find the i2c_client located at a certain
address. Would be happy to know if there is a better way of doing this.
Thanks!
Sui Chen (1):
i2c debug counters as sysfs attributes
drivers/i2c/i2c-core-base.c | 240 +++++++++++++++++++++++++++++++++++-
drivers/i2c/i2c-dev.c | 94 ++++++++++++++
include/linux/i2c.h | 41 ++++++
3 files changed, 374 insertions(+), 1 deletion(-)
--
2.36.0.550.gb090851708-goog
Powered by blists - more mailing lists