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

[cherrypick][v1.1-branch] Cherry picking lwip related fixes #32370

Merged
merged 3 commits into from
Mar 12, 2024

Conversation

shubhamdp
Copy link
Contributor

Cherry-picking #28655, #28798, and #29057 on v1.1-branch

shubhamdp and others added 3 commits February 29, 2024 14:43
…laces (project-chip#28655)

* inet: scoped lwip locks for better safety and add at few more places

* Do not static assert if LWIP_TCPIP_CORE_LOCKING is disabled

* Add scope for locks

* move out the error variable definition to the top
…sert for the same (project-chip#28798)

* [ESP32] Enable LWIP_TCPIP_CORE_LOCKING by default and acquire lwip locks
when initializing route_hook

* inet: static assert if LWIP_TCPIP_CORE_LOCKING is disabled

Static assert is disabled for ASR and bouffalolab platforms

* typo
…29057)

Wrap calls to LwIP APIs in `tcpip_api_call()`, as required.
When `LWIP_TCPIP_CORE_LOCKING` is enabled, this internally becomes `LOCK_TCPIP_CORE/UNLOCK_TCPIP_CORE`
and when it isn't, it posts a message to the TCPIP task to run the function.

Added CHIP stack locking to the UDP receive function.
@shripad621git
Copy link
Contributor

Checked for the lwip related changes and tested it on ESP32 side.

@chshu chshu merged commit 8956bbb into project-chip:v1.1-branch Mar 12, 2024
41 of 52 checks passed
@shubhamdp shubhamdp deleted the v-1-1-lwip-fixes branch March 12, 2024 05:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants