From: Eddie James <eajames@linux.ibm.com>
To: linux-fsi@lists.ozlabs.org
Cc: linux-hwmon@vger.kernel.org, jdelvare@suse.com,
openbmc@lists.ozlabs.org, eajames@linux.ibm.com,
linux-kernel@vger.kernel.org, linux@roeck-us.net
Subject: [PATCH v2 0/3] OCC: fsi and hwmon: Set sequence number in submit interface
Date: Wed, 21 Jul 2021 14:02:28 -0500 [thread overview]
Message-ID: <20210721190231.117185-1-eajames@linux.ibm.com> (raw)
Conflicting sequence numbers have resulted in users of the OCC interface
getting the wrong response. For example, both the hwmon driver and an
application might send a transfer near the same time with the same sequence
number, and then one or both will get an incorrect respnse, but cannot tell
because the sequence number looks correct.
Perform the sequence numbering in the submit interface to make sure each
transfer has a unique sequence number. This also requires that the submit
interface perform the checksum calculation for the command. Adjust the hwmon
driver accordingly too.
Changes since v1:
- fix 0day warnings and errors.
Eddie James (3):
fsi: occ: Force sequence numbering per OCC
hwmon: (occ) Remove sequence numbering and checksum calculation
fsi: occ: Add dynamic debug to dump command and response
drivers/fsi/fsi-occ.c | 99 +++++++++++++++++++++++++++++++-------
drivers/hwmon/occ/common.c | 30 +++++-------
drivers/hwmon/occ/common.h | 3 +-
drivers/hwmon/occ/p8_i2c.c | 15 +++---
drivers/hwmon/occ/p9_sbe.c | 4 +-
5 files changed, 106 insertions(+), 45 deletions(-)
--
2.27.0
next reply other threads:[~2021-07-21 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 19:02 Eddie James [this message]
2021-07-21 19:02 ` [PATCH v2 1/3] fsi: occ: Force sequence numbering per OCC Eddie James
2021-07-21 19:02 ` [PATCH v2 2/3] hwmon: (occ) Remove sequence numbering and checksum calculation Eddie James
2021-07-21 19:02 ` [PATCH v2 3/3] fsi: occ: Add dynamic debug to dump command and response Eddie James
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=20210721190231.117185-1-eajames@linux.ibm.com \
--to=eajames@linux.ibm.com \
--cc=jdelvare@suse.com \
--cc=linux-fsi@lists.ozlabs.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=openbmc@lists.ozlabs.org \
/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).