-
Notifications
You must be signed in to change notification settings - Fork 687
[v3.7.99-ncs2-branch] TWT timeout duration configuration option(build time only) #3195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: v3.7.99-ncs2-branch
Are you sure you want to change the base?
Conversation
The following west manifest projects have been modified in this Pull Request:
Note: This message is automatically posted and updated by the Manifest GitHub Action. |
Build time configuration option to set TWT setup duration. If AP does not respond to TWT setup request for this period, STA will timeout and report setup failure. It's a v2.9.0 release branch update. Signed-off-by: Ajay Parida <[email protected]>
Pull TWT timeout changes. It's a v2.9.0 release branch manifest update, not intended for upstream. Signed-off-by: Ajay Parida <[email protected]>
9303ade
to
fe8aba3
Compare
@@ -807,4 +807,15 @@ config NRF70_PASSIVE_SCAN_ONLY | |||
help | |||
Enable this configuration to force passive scan on all channels. | |||
This will override application-specified scan type. | |||
|
|||
config NRF_WIFI_TWT_SETUP_TIMEOUT |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
config NRF_WIFI_TWT_SETUP_TIMEOUT | |
config NRF_WIFI_TWT_SETUP_TIMEOUT_MS |
The STA will transmit a TWT setup request every 100 milliseconds, | ||
continuing until this timeout value is reached. If no response is received | ||
before the timeout expires, the TWT setup is considered failed. | ||
Note: This is only build time parameter, runtime configuration not supported. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: This is only build time parameter, runtime configuration not supported. | |
@@ -807,4 +807,15 @@ config NRF70_PASSIVE_SCAN_ONLY | |||
help | |||
Enable this configuration to force passive scan on all channels. | |||
This will override application-specified scan type. | |||
|
|||
config NRF_WIFI_TWT_SETUP_TIMEOUT | |||
int "TWT setup request timeout in ms" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
int "TWT setup request timeout in ms" | |
int "TWT setup timeout (ms)" |
config NRF_WIFI_TWT_SETUP_TIMEOUT | ||
int "TWT setup request timeout in ms" | ||
range 100 10000 | ||
default 250 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why choose 250? If we are trying once every 100ms, this would be rounded off no? 250/100 =2, please make it 300.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
or to keep it simple should we just use TWT_SETUP_RETRY_COUNT
(default 3) instead? along with a separate Kconfig TWT_SETUP_TIMEOUT_MS
? (default 100ms).
TWT timeout duration configuration option(build time only)