From: James Prestwood <prestwoj@gmail.com>
To: Denis Kenzior <denkenz@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH 4/7] wiphy: add [DriverFlags].PowerSaveDisable flag
Date: Mon, 19 Jun 2023 07:49:56 -0700 [thread overview]
Message-ID: <f0558c33-1435-62cc-32f2-fe0673788531@gmail.com> (raw)
In-Reply-To: <a3621173-3b82-2954-2454-a3039dd985ef@gmail.com>
Hi Denis,
On 6/18/23 12:07 PM, Denis Kenzior wrote:
> Hi James,
>
> On 6/15/23 14:24, James Prestwood wrote:
>> Certain drivers do not handle power save very well resulting in
>> missed frames, firmware crashes, or other bad behavior. Its easy
>> enough to disable power save via iw, iwconfig, etc but since IWD
>> removes and creates the interface on startup it blows away any
>> previous power save setting. The setting must be done *after* IWD
>> creates the interface which can be done, but needs to be via some
>> external daemon monitoring IWD's state. For minimal systems,
>> e.g. without NetworkManager, it becomes difficult and annoying to
>> persistently disable power save.
>>
>> For this reason a new driver flag POWER_SAVE_DISABLE is being
>> added. This can then be referenced when creating the interfaces
>> and if set, disable power save.
>> ---
>> src/wiphy.c | 13 +++++++++++++
>> src/wiphy.h | 1 +
>> 2 files changed, 14 insertions(+)
>>
>
> <snip>
>
>> @@ -723,6 +725,17 @@ bool wiphy_control_port_enabled(struct wiphy *wiphy)
>> return enabled;
>> }
>> +bool wiphy_disable_power_save(struct wiphy *wiphy)
>
> I named this wiphy_power_save_disabled to be consistent with
> wiphy_control_port_enabled()...
>
> I went ahead and applied this, but I think we have to fix the behavior
> of this and wiphy_control_port_enabled(). Namely:
>
>> +{
>> + if (wiphy->driver_flags & POWER_SAVE_DISABLE) {
>> + l_info("Disabling power save due to driver quirks: %s",
>> + wiphy_get_driver(wiphy));
>
> We shouldn't really use l_info here. This method is meant more as a
> getter and might have other users in the future. Same case with
> wiphy_control_port_enabled(), but that one is a little bit more complex
> to fix.
Ok I can send a follow up patch. The only use for all these APIs is when
creating the netdev so we *should* only see it then but now that we
print these flags with wiphy_print_basic_info I'll just remove them
entirely.
>
> Patches 4, 6 and 7 applied.
>
> Regards,
> -Denis
next prev parent reply other threads:[~2023-06-19 14:50 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 [this message]
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 ` [PATCH 7/7] doc: Document [DriverFlags].PowerSaveDisable James Prestwood
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=f0558c33-1435-62cc-32f2-fe0673788531@gmail.com \
--to=prestwoj@gmail.com \
--cc=denkenz@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