linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joel Stanley <joel@jms.id.au>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-fsi@lists.ozlabs.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Jeffery <andrewrjeffery@gmail.com>,
	Guenter Roeck <linux@roeck-us.net>,
	Eddie James <eajames@linux.ibm.com>
Subject: [GIT PULL] fsi changes for v5.16
Date: Fri, 22 Oct 2021 00:10:58 +0000	[thread overview]
Message-ID: <CACPK8Xf0_D6P8ru5-UyqXQsF9uTejks8E1O06+1qTs7_R7No1w@mail.gmail.com> (raw)

Hello Greg,

Here are a set of FSI changes targeting the v5.16 merge window. They
have been through a few cycles of review on the list and appear ready
to be merged.

There are some dependent hwmon changes that Guenter has acked and
indicated he is ok with them going through the fsi tree.

The following changes since commit 6880fa6c56601bb8ed59df6c30fd390cc5f6dd8f:

  Linux 5.15-rc1 (2021-09-12 16:28:37 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/joel/fsi.git tags/fsi-for-v5.16

for you to fetch changes up to 7cc2f34e1f4da07c791737cc6b3d965b31815ea0:

  fsi: sbefifo: Use interruptible mutex locking (2021-10-22 09:54:33 +1030)

----------------------------------------------------------------
FSI changes for v5.16

 - SBEFIFO usersapce interfaces to perform FFDC (First Failure
   Data Capture) and detect timeouts

 - A fix to handle multiple messages in flight

----------------------------------------------------------------
Eddie James (9):
      fsi: occ: Force sequence numbering per OCC
      hwmon: (occ) Remove sequence numbering and checksum calculation
      fsi: occ: Use a large buffer for responses
      fsi: occ: Store the SBEFIFO FFDC in the user response buffer
      docs: ABI: testing: Document the OCC hwmon FFDC binary interface
      hwmon: (occ) Provide the SBEFIFO FFDC in binary sysfs
      docs: ABI: testing: Document the SBEFIFO timeout interface
      fsi: sbefifo: Add sysfs file indicating a timeout error
      fsi: sbefifo: Use interruptible mutex locking

 .../ABI/testing/sysfs-bus-fsi-devices-sbefifo      |  10 +
 .../testing/sysfs-bus-platform-devices-occ-hwmon   |  13 ++
 drivers/fsi/fsi-occ.c                              | 218 ++++++++++++---------
 drivers/fsi/fsi-sbefifo.c                          |  28 ++-
 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                         |  90 ++++++++-
 include/linux/fsi-occ.h                            |   2 +
 9 files changed, 282 insertions(+), 127 deletions(-)
 create mode 100644 Documentation/ABI/testing/sysfs-bus-fsi-devices-sbefifo
 create mode 100644
Documentation/ABI/testing/sysfs-bus-platform-devices-occ-hwmon

             reply	other threads:[~2021-10-22  0:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22  0:10 Joel Stanley [this message]
2021-10-22  7:46 ` [GIT PULL] fsi changes for v5.16 Greg KH

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=CACPK8Xf0_D6P8ru5-UyqXQsF9uTejks8E1O06+1qTs7_R7No1w@mail.gmail.com \
    --to=joel@jms.id.au \
    --cc=andrewrjeffery@gmail.com \
    --cc=eajames@linux.ibm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-fsi@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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).