Linux wireless drivers development
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: "linux-wireless\@vger.kernel.org"
	<linux-wireless@vger.kernel.org>,
	"Kevin Yang" <kevin_yang@realtek.com>
Subject: Re: [PATCH 13/13] rtw89: prohibit mac80211 chanctx ops without HW scan
Date: Fri, 02 Sep 2022 11:28:26 +0300	[thread overview]
Message-ID: <87ler2b2ol.fsf@kernel.org> (raw)
In-Reply-To: <b8f7720937e05c6fd7fde14b8ea57065879928a8.camel@realtek.com> (Ping-Ke Shih's message of "Tue, 9 Aug 2022 11:00:12 +0000")

Ping-Ke Shih <pkshih@realtek.com> writes:

>> > > So if the user has not update the firmware a kernel upgrade will break
>> > > their internet? That's not good, we should not break existing setups. So
>> > > what firmware version is required?
>> > > 
>> > 
>> > Firmware version 0.13.35.0 is required. The firmware has been in
>> > linux-firmware repository on 2022-02-18. I think people being able
>> > to update kernel can update firmware as well.
>> > 
>> > The alternative ways could be
>> > 1. add a module parameter, like no_channel_context. We can add a
>> >    prompt to note people can set it to 1 for old firmware.
>> > 
>> > 2. wait version of request_firmware() as first step of pci probe.
>> >    The probe could cost longer time, because currently we use
>> >    request_firmware_nowait() and continue to initialize in parallel.
>> >    More, hw->priv isn't allocated at that moment, so it could be not
>> >    so straightforward.
>> > 
>> 
>> To prevent break users' existing setups, modified approach 1 is adopted
>> by patchset v2. We add a module parameter rtw89_use_chanctx, and disable
>> it by default. So, users' setups with old firmware can still work.
>> 
>> If a user wants channel context to support concurrency, he can set
>> rtw89_use_chanctx=1 and upgrade firmware. 
>> 
>> I think this could be a better user experience of kernel.
>> 
>
> We have a better idea that load firmware header and parse firmware
> features when probing before ieee80211_register_hw(). If firmware
> doesn't support hw_scan, it still can work as original. So, users
> don't need to update firmware or set module parameters.
>
> I have sent v3 with this idea that is friendly to users.

Sorry for the delay, I was not able to look at this in detail earlier.

Indeed v3 is much better approach and actually what we prefer in
upstream. iwlwifi, ath10k and ath11k do something similar. Forcing users
to update the firmware or fiddling with module parameters when updating
the kernel is bad from user's point of view.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

      reply	other threads:[~2022-09-02  8:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17  8:49 [PATCH 00/13] rtw89: support channel context Ping-Ke Shih
2022-06-17  8:49 ` [PATCH 01/13] rtw89: rewrite decision on channel by entity state Ping-Ke Shih
2022-06-17  8:49 ` [PATCH 02/13] rtw89: introduce rtw89_chan for channel stuffs Ping-Ke Shih
2022-06-17  8:49 ` [PATCH 03/13] rtw89: re-arrange channel related stuffs under HAL Ping-Ke Shih
2022-06-17  8:49 ` [PATCH 04/13] rtw89: create rtw89_chan centrally to avoid breakage Ping-Ke Shih
2022-06-17  8:49 ` [PATCH 05/13] rtw89: txpwr: concentrate channel related control to top Ping-Ke Shih
2022-06-17  8:49 ` [PATCH 06/13] rtw89: rfk: concentrate parameter control while set_channel() Ping-Ke Shih
2022-06-17  8:49 ` [PATCH 07/13] rtw89: concentrate parameter control for setting channel callback Ping-Ke Shih
2022-06-17  8:49 ` [PATCH 08/13] rtw89: concentrate chandef setting to stack callback Ping-Ke Shih
2022-06-17  8:49 ` [PATCH 09/13] rtw89: initialize entity and configure default chandef Ping-Ke Shih
2022-06-17  8:49 ` [PATCH 10/13] rtw89: introduce entity mode and its recalculated prototype Ping-Ke Shih
2022-06-17  8:49 ` [PATCH 11/13] rtw89: add skeleton of mac80211 chanctx ops support Ping-Ke Shih
2022-06-17  8:49 ` [PATCH 12/13] rtw89: support mac80211 chanctx ops by chip Ping-Ke Shih
2022-06-17  8:49 ` [PATCH 13/13] rtw89: prohibit mac80211 chanctx ops without HW scan Ping-Ke Shih
2022-06-20 10:09   ` Kalle Valo
2022-06-20 12:34     ` Ping-Ke Shih
2022-06-23  3:51       ` Ping-Ke Shih
2022-08-09 11:00         ` Ping-Ke Shih
2022-09-02  8:28           ` Kalle Valo [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=87ler2b2ol.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=kevin_yang@realtek.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.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