From: Yiwei Lin <s921975628@gmail.com>
To: corbet@lwn.net, linux-doc@vger.kernel.org, rdunlap@infradead.org
Cc: hdegoede@redhat.com, srinivas.pandruvada@linux.intel.com,
linux-kernel@vger.kernel.org, Yiwei Lin <s921975628@gmail.com>
Subject: [PATCH v2] scsi: docs: Add description for missing options of link_power_management_policy
Date: Thu, 15 Jan 2026 14:53:41 +0800 [thread overview]
Message-ID: <20260115065341.10230-1-s921975628@gmail.com> (raw)
With the kernel update we have more different policy for SCSI
link power management. Add the corresponding description to
the file.
Signed-off-by: Yiwei Lin <s921975628@gmail.com>
---
.../scsi/link_power_management_policy.rst | 23 ++++++++++++++-----
1 file changed, 17 insertions(+), 6 deletions(-)
diff --git a/Documentation/scsi/link_power_management_policy.rst b/Documentation/scsi/link_power_management_policy.rst
index 64288dcf1..e350892cc 100644
--- a/Documentation/scsi/link_power_management_policy.rst
+++ b/Documentation/scsi/link_power_management_policy.rst
@@ -5,13 +5,13 @@ Link Power Managent Policy
==========================
This parameter allows the user to set the link (interface) power management.
-There are 3 possible options:
+There are 6 possible options:
-===================== =====================================================
+====================== =====================================================
Value Effect
-===================== =====================================================
-min_power Tell the controller to try to make the link use the
- least possible power when possible. This may
+====================== =====================================================
+min_power Enable slumber mode(no partial mode) for the link to
+ use the least possible power when possible. This may
sacrifice some performance due to increased latency
when coming out of lower power states.
@@ -22,4 +22,15 @@ max_performance Generally, this means no power management. Tell
medium_power Tell the controller to enter a lower power state
when possible, but do not enter the lowest power
state, thus improving latency over min_power setting.
-===================== =====================================================
+
+keep_firmware_settings Do not change the current firmware settings for
+ Power management. This is the default setting.
+
+med_power_with_dipm Same as medium_power, but additionally with
+ Device-initiated power management(DIPM) enabled,
+ as Intel Rapid Storage Technology(IRST) does.
+
+min_power_with_partial Same as min_power, but additionally with partial
+ power state enabled, which may improve performance
+ over min_power setting.
+====================== =====================================================
--
2.34.1
next reply other threads:[~2026-01-15 6:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 6:53 Yiwei Lin [this message]
2026-01-15 7:00 ` [PATCH v2] scsi: docs: Add description for missing options of link_power_management_policy Randy Dunlap
2026-01-20 21:59 ` Jonathan Corbet
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=20260115065341.10230-1-s921975628@gmail.com \
--to=s921975628@gmail.com \
--cc=corbet@lwn.net \
--cc=hdegoede@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=srinivas.pandruvada@linux.intel.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