From: Ranjan Kumar <ranjan.kumar@broadcom.com>
To: linux-scsi@vger.kernel.org, martin.petersen@oracle.com
Cc: sathya.prakash@broadcom.com, sumit.saxena@broadcom.com,
chandrakanth.patil@broadcom.com, prayas.patel@broadcom.com,
Ranjan Kumar <ranjan.kumar@broadcom.com>
Subject: [PATCH v2 0/6] mpt3sas: Improve device readiness handling and event recovery
Date: Thu, 13 Nov 2025 21:07:04 +0530 [thread overview]
Message-ID: <20251113153712.31850-1-ranjan.kumar@broadcom.com> (raw)
This patch series enhances the mpt3sas driver’s device bring-up,
readiness detection, and event recovery mechanisms to improve
robustness in environments with slow-responding or transient
SAS/PCIe devices.
The series introduces optional control over issuing TEST UNIT READY
(TUR) commands during device unblocking, configurable retry limits,
and a mechanism to requeue firmware topology events when devices are
temporarily busy. Together, these updates reduce discovery failures
and improve recovery reliability following firmware or link events.
Change since v1:
- Fixed test robot build warnings
- Fixed W=1 compilation warnings
Ranjan Kumar (6):
mpt3sas: Added no_turs flag to device unblock logic
mpt3sas: Added issue_scsi_cmd_to_bringup_drive module parameter part-1
mpt3sas: improve device discovery and readiness handling for slow
devices part-2
mpt3sas: Add firmware event requeue support for busy devices
mpt3sas: Add configurable command retry limit for slow-to-respond
devices
mpt3sas: Fixed the W=1 compilation warning
drivers/scsi/mpt3sas/mpt3sas_base.c | 14 +-
drivers/scsi/mpt3sas/mpt3sas_base.h | 4 +
drivers/scsi/mpt3sas/mpt3sas_scsih.c | 1458 ++++++++++++++++++++++++--
3 files changed, 1376 insertions(+), 100 deletions(-)
--
2.47.3
next reply other threads:[~2025-11-13 15:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 15:37 Ranjan Kumar [this message]
2025-11-13 15:37 ` [PATCH v2 1/6] mpt3sas: Added no_turs flag to device unblock logic Ranjan Kumar
2025-11-13 15:37 ` [PATCH v2 2/6] mpt3sas: Added issue_scsi_cmd_to_bringup_drive module parameter part-1 Ranjan Kumar
2025-11-13 15:37 ` [PATCH v2 3/6] mpt3sas: improve device discovery and readiness handling for slow devices part-2 Ranjan Kumar
2025-11-13 15:37 ` [PATCH v2 4/6] mpt3sas: Add firmware event requeue support for busy devices Ranjan Kumar
2025-11-13 15:37 ` [PATCH v2 5/6] mpt3sas: Add configurable command retry limit for slow-to-respond devices Ranjan Kumar
2025-11-13 15:37 ` [PATCH v2 6/6] mpt3sas: Fixed the W=1 compilation warning Ranjan Kumar
2025-12-17 3:17 ` [PATCH v2 0/6] mpt3sas: Improve device readiness handling and event recovery Martin K. Petersen
2026-01-04 21:43 ` Martin K. Petersen
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=20251113153712.31850-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=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