Skip to content
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

Commad status check phase1 #1239

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

ajayparida
Copy link
Contributor

First PR from a series or PR to handle command status check for all the commands.
In this PR, only those commands for which no information is passed either to supplicant/user space is handled.
On sending the command, host will wait for the command status to be returned by the firmare.
Depending upon the status/timeout it will return the result to userspace/supplicant.

@ajayparida ajayparida force-pushed the cmd_status_check_phase1 branch 7 times, most recently from 594c89a to 026f6f8 Compare March 13, 2024 07:30
@ajayparida ajayparida marked this pull request as draft April 17, 2024 12:27
@ajayparida ajayparida marked this pull request as ready for review May 15, 2024 07:26
@ajayparida ajayparida force-pushed the cmd_status_check_phase1 branch 2 times, most recently from c581edb to 13b5bd9 Compare May 15, 2024 11:45
@ajayparida ajayparida force-pushed the cmd_status_check_phase1 branch 3 times, most recently from e7d4b06 to 4af396b Compare May 17, 2024 07:18
@ajayparida ajayparida marked this pull request as draft July 18, 2024 09:59
@ajayparida ajayparida force-pushed the cmd_status_check_phase1 branch 2 times, most recently from b781d78 to 921e956 Compare July 31, 2024 06:08
@ajayparida ajayparida marked this pull request as ready for review July 31, 2024 06:14
@ajayparida ajayparida force-pushed the cmd_status_check_phase1 branch 2 times, most recently from 5b842cd to ba03d8b Compare July 31, 2024 08:03
@rakeswar2001 rakeswar2001 force-pushed the cmd_status_check_phase1 branch 3 times, most recently from e7c4abe to 4d5c23d Compare August 1, 2024 11:55
@ajayparida ajayparida force-pushed the cmd_status_check_phase1 branch 2 times, most recently from eb6b417 to 6ee198d Compare August 5, 2024 10:35
@rakeswar2001 rakeswar2001 force-pushed the cmd_status_check_phase1 branch 6 times, most recently from 41c4d21 to ff8f41f Compare August 14, 2024 07:04
ajayparida and others added 6 commits August 21, 2024 15:09
Validate input parameters passed to API before using them.

Signed-off-by: Ajay Parida <ajay.parida@nordicsemi.no>
Added  NRF_WIFI_UMAC_CMD_MAX to represent maximum command supported.

Signed-off-by: Ajay Parida <ajay.parida@nordicsemi.no>
Structure to store per vif command state information.

Signed-off-by: Ajay Parida <ajay.parida@nordicsemi.no>
Check for command pending state for the vif before processing.

Signed-off-by: Ajay Parida <ajay.parida@nordicsemi.no>
After sending the command, wait for command status event from firmware.
There are two scenarios. Either firmware sends a specific event for the
command or a generic event (NRF_WIFI_UMAC_EVENT_CMD_STATUS) where it
states about the command failure/success.

This commit is related to wait for NRF_WIFI_UMAC_EVENT_CMD_STATUS and
it's handling.

For commands expecting specific events will be added later.

Signed-off-by: Ajay Parida <ajay.parida@nordicsemi.no>
UMAC:
    [SHEL-2504]:UMAC commands are providing status as failure.

Signed-off-by: Rakeswara Kummetha <rakeswara.kummetha@nordicsemi.no>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants