From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.linux.dev
Cc: James Prestwood <prestwoj@gmail.com>
Subject: [PATCH 7/7] doc: Document [DriverFlags].PowerSaveDisable
Date: Thu, 15 Jun 2023 12:24:15 -0700 [thread overview]
Message-ID: <20230615192415.1718516-7-prestwoj@gmail.com> (raw)
In-Reply-To: <20230615192415.1718516-1-prestwoj@gmail.com>
---
src/iwd.config.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/iwd.config.rst b/src/iwd.config.rst
index 190f2c69..6b52b040 100644
--- a/src/iwd.config.rst
+++ b/src/iwd.config.rst
@@ -403,6 +403,10 @@ are buggy or just don't behave similar enough to the majority of other drivers.
not be used, and PAE will be used instead. Some drivers do not properly
support ControlPortOverNL80211 even though they advertise support for it.
+ * - PowerSaveDisable
+ - Values: comma-separated list of drivers or glob matches
+
+ If a driver in user matches one in this list power save will be disabled.
SEE ALSO
========
--
2.25.1
prev parent reply other threads:[~2023-06-15 19:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 19:24 [PATCH 1/7] wiphy: store driver flags directly in wiphy object James Prestwood
2023-06-15 19:24 ` [PATCH 2/7] wiphy: allow for user-defined driver flags James Prestwood
2023-06-18 19:03 ` Denis Kenzior
2023-06-15 19:24 ` [PATCH 3/7] doc: document [DriverFlags] group settings James Prestwood
2023-06-15 19:24 ` [PATCH 4/7] wiphy: add [DriverFlags].PowerSaveDisable flag James Prestwood
2023-06-18 19:07 ` Denis Kenzior
2023-06-19 14:49 ` James Prestwood
2023-06-15 19:24 ` [PATCH 5/7] netdev: disable power save if required James Prestwood
2023-06-18 19:11 ` Denis Kenzior
2023-06-19 14:54 ` James Prestwood
2023-06-15 19:24 ` [PATCH 6/7] wiphy: print driver flags on startup James Prestwood
2023-06-15 19:24 ` James Prestwood [this message]
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=20230615192415.1718516-7-prestwoj@gmail.com \
--to=prestwoj@gmail.com \
--cc=iwd@lists.linux.dev \
/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