From: Kashyap Desai <kashyap.desai@broadcom.com>
To: linux-scsi@vger.kernel.org
Cc: jejb@linux.ibm.com, martin.petersen@oracle.com,
steve.hagan@broadcom.com, mpi3mr-linuxdrv.pdl@broadcom.com,
Kashyap Desai <kashyap.desai@broadcom.com>
Subject: [PATCH 0/7] adding application support
Date: Wed, 22 Sep 2021 00:15:53 +0530 [thread overview]
Message-ID: <20210921184600.64427-1-kashyap.desai@broadcom.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1831 bytes --]
This patch series covers application support for the
MPI3MR high performance storage I/O & RAID controllers (Avenger series).
Patches are logical split mainly for better code review. Full patch set is
recommended for functional stability.
You can find the source at -
https://github.com/kadesai16/mpi3mr/tree/app_v2
Kashyap Desai (7):
mpi3mr: upgrade mpi30 Rev-V
[SCSI] miscdevice: adding support for MPI3MR_MINOR(243)
mpi3mr: controller management application support
mpi3mr: misc changes and use __builtin_return_address for debug
mpi3mr: PEL support added
mpi3mr: nvme pass-through support
mpi3mr: task management for pass through command
drivers/scsi/mpi3mr/Makefile | 1 +
drivers/scsi/mpi3mr/mpi/mpi30_cnfg.h | 603 +++++++--
drivers/scsi/mpi3mr/mpi/mpi30_image.h | 59 +-
drivers/scsi/mpi3mr/mpi/mpi30_init.h | 15 +-
drivers/scsi/mpi3mr/mpi/mpi30_ioc.h | 128 +-
drivers/scsi/mpi3mr/mpi/mpi30_pci.h | 44 +
drivers/scsi/mpi3mr/mpi/mpi30_sas.h | 14 +
drivers/scsi/mpi3mr/mpi/mpi30_tool.h | 303 +++++
drivers/scsi/mpi3mr/mpi/mpi30_transport.h | 31 +-
drivers/scsi/mpi3mr/mpi3mr.h | 72 +-
drivers/scsi/mpi3mr/mpi3mr_app.c | 1411 +++++++++++++++++++++
drivers/scsi/mpi3mr/mpi3mr_app.h | 399 ++++++
drivers/scsi/mpi3mr/mpi3mr_fw.c | 345 ++++-
drivers/scsi/mpi3mr/mpi3mr_os.c | 36 +-
include/linux/miscdevice.h | 1 +
15 files changed, 3289 insertions(+), 173 deletions(-)
create mode 100644 drivers/scsi/mpi3mr/mpi/mpi30_pci.h
create mode 100644 drivers/scsi/mpi3mr/mpi/mpi30_tool.h
create mode 100644 drivers/scsi/mpi3mr/mpi3mr_app.c
create mode 100644 drivers/scsi/mpi3mr/mpi3mr_app.h
base-commit: f959a1319db1096ed1a133feba74dfdb582db9cb
--
2.18.1
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4212 bytes --]
next reply other threads:[~2021-09-21 18:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 18:45 Kashyap Desai [this message]
2021-09-21 18:45 ` [PATCH 1/7] mpi3mr: upgrade mpi30 Rev-V Kashyap Desai
2021-09-21 18:45 ` [PATCH 2/7] miscdevice: adding support for MPI3MR_MINOR(243) Kashyap Desai
2021-10-05 4:27 ` Martin K. Petersen
2021-10-26 11:16 ` Kashyap Desai
2021-10-27 3:38 ` Martin K. Petersen
2021-10-28 18:34 ` Kashyap Desai
2021-12-13 12:23 ` [mpi3mr] " Sumit Saxena
2021-12-17 3:57 ` Martin K. Petersen
2021-09-21 18:45 ` [PATCH 3/7] mpi3mr: controller management application support Kashyap Desai
2021-09-21 18:45 ` [PATCH 4/7] mpi3mr: misc changes and use __builtin_return_address for debug Kashyap Desai
2021-09-21 18:45 ` [PATCH 5/7] mpi3mr: PEL support added Kashyap Desai
2021-09-21 18:45 ` [PATCH 6/7] mpi3mr: nvme pass-through support Kashyap Desai
2021-09-21 18:46 ` [PATCH 7/7] mpi3mr: task management for pass through command Kashyap Desai
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=20210921184600.64427-1-kashyap.desai@broadcom.com \
--to=kashyap.desai@broadcom.com \
--cc=jejb@linux.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mpi3mr-linuxdrv.pdl@broadcom.com \
--cc=steve.hagan@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.