public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ranjan Kumar <ranjan.kumar@broadcom.com>
To: linux-scsi@vger.kernel.org, martin.petersen@oracle.com
Cc: rajsekhar.chundru@broadcom.com, sathya.prakash@broadcom.com,
	sumit.saxena@broadcom.com, chandrakanth.patil@broadcom.com,
	prayas.patel@broadcom.com,
	Ranjan Kumar <ranjan.kumar@broadcom.com>
Subject: [PATCH v3 0/6] mpi3mr: Host diag buffer support
Date: Thu, 16 May 2024 20:50:04 +0530	[thread overview]
Message-ID: <20240516152010.88227-1-ranjan.kumar@broadcom.com> (raw)

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

The controllers managed by mpi3mr driver requires system memory to
save hardware and firmware diagnostic information, this patch set
enhances the drivers to provide host memory to the controller for
diagnostic information.  This patch set also provides driver changes
to push kernel messages into the diagnostic buffers reserved for the
driver, so that the information will be available as part of debug
data fetched from the controller.  In addition, support for
configuring automatic diagnostic information is added in the driver.

Change since v1:
- Fixed test robot build warnings

Change since v2:
- Fixed test robot build warnings

Ranjan Kumar (6):
  mpi3mr: HDB allocation and posting for hardware and Firmware buffers
  mpi3mr: Driver buffer allocation and posting
  mpi3mr: Dump driver and dmesg logs into driver diag buffer
  mpi3mr: Trigger support
  mpi3mr: Ioctl support for HDB
  mpi3mr: Update driver version to 8.9.1.0.50

 drivers/scsi/mpi3mr/mpi/mpi30_tool.h |   59 ++
 drivers/scsi/mpi3mr/mpi3mr.h         |  162 +++-
 drivers/scsi/mpi3mr/mpi3mr_app.c     | 1080 ++++++++++++++++++++++++++
 drivers/scsi/mpi3mr/mpi3mr_fw.c      |  550 ++++++++++++-
 drivers/scsi/mpi3mr/mpi3mr_os.c      |  113 +++
 include/uapi/scsi/scsi_bsg_mpi3mr.h  |    3 +-
 6 files changed, 1956 insertions(+), 11 deletions(-)
 create mode 100644 drivers/scsi/mpi3mr/mpi/mpi30_tool.h

-- 
2.31.1


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4209 bytes --]

             reply	other threads:[~2024-05-16 15:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-16 15:20 Ranjan Kumar [this message]
2024-05-16 15:20 ` [PATCH v3 1/6] mpi3mr: HDB allocation and posting for hardware and Firmware buffers Ranjan Kumar
2024-05-16 15:20 ` [PATCH v3 2/6] mpi3mr: Driver buffer allocation and posting Ranjan Kumar
2024-05-16 15:20 ` [PATCH v3 3/6] mpi3mr: Dump driver and dmesg logs into driver diag buffer Ranjan Kumar
2024-05-31  1:04   ` Martin K. Petersen
2024-06-05  9:04     ` Ranjan Kumar
2024-05-16 15:20 ` [PATCH v3 4/6] mpi3mr: Trigger support Ranjan Kumar
2024-05-16 15:20 ` [PATCH v3 5/6] mpi3mr: Ioctl support for HDB Ranjan Kumar
2024-05-16 15:20 ` [PATCH v3 6/6] mpi3mr: Update driver version to 8.9.1.0.50 Ranjan Kumar

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=20240516152010.88227-1-ranjan.kumar@broadcom.com \
    --to=ranjan.kumar@broadcom.com \
    --cc=chandrakanth.patil@broadcom.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=prayas.patel@broadcom.com \
    --cc=rajsekhar.chundru@broadcom.com \
    --cc=sathya.prakash@broadcom.com \
    --cc=sumit.saxena@broadcom.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