From: "Bao D. Nguyen" <quic_nguyenb@quicinc.com>
To: <quic_cang@quicinc.com>, <quic_nitirawa@quicinc.com>,
<bvanassche@acm.org>, <avri.altman@wdc.com>, <beanhuo@micron.com>,
<adrian.hunter@intel.com>, <martin.petersen@oracle.com>
Cc: <linux-scsi@vger.kernel.org>, "Bao D. Nguyen" <quic_nguyenb@quicinc.com>
Subject: [PATCH v2 0/1] Allow platform drivers to update UIC command timeout
Date: Thu, 30 May 2024 14:36:39 -0700 [thread overview]
Message-ID: <cover.1717104518.git.quic_nguyenb@quicinc.com> (raw)
The UIC command timeout default value remains as 500ms.
Allow platform drivers to change the UIC command timeout as they wish.
During product development where a lot of debug logging/printing can
occur, the uart may print from different modules with interrupt disabled
for more than 500ms, causing interrupt starvation and UIC command timeout
as a result. The UIC command timeout may eventually cause a watchdog
timeout unnecessarily. With this change, the platform drivers can set a
different UIC command timeout as desired. The supported values range
from 500ms to 2 seconds.
v1 -> v2: - Created kernel module parameter namely uic_cmd_timeout
as recommended by Bart. Addressed some other comments.
- Un-do the change in the include/ufs/ufshcd.h file
which added the uic_cmd_timeout field to the hba struct.
- Removed the patch 2 in the series where the UIC command
timeout value was overridden by the platform driver.
Bao D. Nguyen (1):
scsi: ufs: core: Support Updating UIC Command Timeout
drivers/ufs/core/ufshcd.c | 35 ++++++++++++++++++++++++++++++-----
1 file changed, 30 insertions(+), 5 deletions(-)
--
2.7.4
next reply other threads:[~2024-05-30 21:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 21:36 Bao D. Nguyen [this message]
2024-05-30 21:36 ` [PATCH v2 1/1] scsi: ufs: core: Support Updating UIC Command Timeout Bao D. Nguyen
2024-06-12 1:43 ` Martin K. Petersen
2024-06-12 3:25 ` Bart Van Assche
2024-06-12 3:24 ` Bart Van Assche
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=cover.1717104518.git.quic_nguyenb@quicinc.com \
--to=quic_nguyenb@quicinc.com \
--cc=adrian.hunter@intel.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=quic_cang@quicinc.com \
--cc=quic_nitirawa@quicinc.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