linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: Sui Chen <suichen@google.com>
Cc: linux-i2c@vger.kernel.org
Subject: Re: [RFC Patch 0/2] I2C statistics as sysfs attributes
Date: Mon, 29 Nov 2021 18:09:58 +0100	[thread overview]
Message-ID: <YaUJZn0aLf7GknY9@kunai> (raw)
In-Reply-To: <CAJOps0s4qY3O36BGUpffzzA=gxw_crDzf_iif2fq0RdVhfCydg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]

Hi Sui Chen,

> It appears bus errors and NACK counts are frequently found in many
> I2C controllers; a few I2C bus drivers now export those counters to
> debugfs. There is some effort in attempting to monitor a large
> number of BMCs (board management controllers) and we are wondering if
> it is possible to have a more stable and unified interface for those
> counters to be exported to compared to the debugfs, so that a single
> command can be used to obtain the counters from different types of I2C
> controllers.

There are at least two things to consider here:

1) Why do you need this information? I don't think values like NACK
count describe the health of a system. NACKs are perfectly OK in regular
I2C communication. So, for now, I think debugfs is the better place.
An exception might be the bus speed. Some people already had an interest
in this.

2) Even when this information is kept in debugfs, we can still add some
core helper to have a standardized structure for the created files. This
is independent from sysfs. I don't think I want this a standardized ABI,
currently. Unless you explain good reasons to me :)

Thanks and happy hacking,

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2021-11-29 20:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-12  1:07 [RFC Patch 0/2] I2C statistics as sysfs attributes Sui Chen
2021-11-29 17:09 ` Wolfram Sang [this message]

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=YaUJZn0aLf7GknY9@kunai \
    --to=wsa@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=suichen@google.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;
as well as URLs for NNTP newsgroup(s).