-
Notifications
You must be signed in to change notification settings - Fork 8.4k
soc: silabs: silabs_siwx91x: Increasing the mutex count #91113
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: main
Are you sure you want to change the base?
soc: silabs: silabs_siwx91x: Increasing the mutex count #91113
Conversation
|
Hello @swamidas1998, and thank you very much for your first pull request to the Zephyr project! |
| config CMSIS_V2_THREAD_MAX_STACK_SIZE | ||
| default 2048 | ||
|
|
||
| config CMSIS_V2_MUTEX_MAX_COUNT |
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.
These should use configdefault instead of config to override the default value of the existing symbol instead of shadowing it with a new symbol. See https://docs.zephyrproject.org/latest/build/kconfig/extensions.html
6a60aff to
54333c2
Compare
Increasing the mutex counts and event flag in order to avoid mutex failures in netoffload mode Signed-off-by: SwamiDas Nampalli <swami.das@silabs.com>
Socket state is not moved to connected in the siwx91x_sock_accept, hence the subsequent socket calls(recv(), send()) fails since socket state is not updated. Signed-off-by: SwamiDas Nampalli <swami.das@silabs.com>
54333c2 to
cf948a5
Compare
|
jerome-pouiller
left a comment
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.
For the first commit, the prefix should be soc: silabs: siwx91x: . Otherwise LGFM.
|
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
|
@swamidas1998 is this patch still relevant? |
|
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
|
I believe this PR is relevant. I am going to take it over. |



Increasing the mutex counts and event flag in order to avoid mutex failures in netoffload mode