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

[SL-UP] Removing the IP polling from the Matter code #288

Open
wants to merge 3 commits into
base: release_2.5-1.4
Choose a base branch
from

Conversation

chirag-silabs
Copy link
Contributor

The IP polling and assignment is already a part of the wifi SDK code, so removing the code from the matter layer.

Keeping the notify code which is used for the notify the application about the connectivity

Testing

Multiple smoke runs were done to validate the change.
Tested on the 917 SoC

@chirag-silabs chirag-silabs requested a review from a team as a code owner February 17, 2025 15:33
@jmartinez-silabs
Copy link
Contributor

This can be done on CSA now. We are also not in a release cycle so it would be preferable to do it on CSA first.

@@ -724,14 +657,9 @@ void sl_matter_wifi_post_event(WifiEvent event)
/// and emits a WifiEvent::kStationDoDhcp event to trigger DHCP polling checks. Helper function for ProcessEvent.
void ResetDHCPNotificationFlags(void)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if DHCP related process is missing do we need this API? if yes, then it should be renamed.

void NotifyConnectivity(void)
{
VerifyOrReturn(!hasNotifiedWifiConnectivity);
#if (CHIP_DEVICE_CONFIG_ENABLE_IPV4)
Copy link
Contributor

@rosahay-silabs rosahay-silabs Feb 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

according to existing logic, we used to trigger these based on the relevant IPv4 and IPv6 events, this gives me the impression that no matter which among the two IPv4 IPv6 has been acquired we notify, is that understanding correct?
If yes, then do we need to keep track of the hasNotifiedWifiConnectivity event at all?

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.

3 participants