-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Update example network-manager-app and integrate it with ubus #33968
base: master
Are you sure you want to change the base?
Conversation
ksperling-apple
commented
Jun 18, 2024
- Add the ability for EventLoopHandlers to participate in the event loop
- Update network-manager-app with correct device type and integrate ubus
PR #33968: Size comparison from 8ba371a to 4f5e46f Full report (52 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, mbed, nrfconnect, nxp, psoc6, stm32, tizen)
|
72ed829
to
c6f4692
Compare
PR #33968: Size comparison from 4cdce52 to c6f4692 Full report (46 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, linux, mbed, nxp, psoc6, qpg, stm32, tizen)
|
Add ubus integration Fix device type id Prefix binary name with "matter-"
c6f4692
to
92ee347
Compare
PR #33968: Size comparison from 4cdce52 to 92ee347 Full report (85 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, mbed, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
Could we split this into separate PRs? Support for event loop handlers seem reasonably independent from the network manager changes. Can we add some unit tests that validates that EventLoopHandlers work as expected? |
@@ -685,16 +695,21 @@ void LayerImplSelect::HandleEvents() | |||
|
|||
for (auto & w : mSocketWatchPool) | |||
{ | |||
if (w.mFD != kInvalidFd) | |||
if (w.mFD != kInvalidFd && w.mCallback != nullptr) |
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.
Hmm. Wouldn't we want to drain the events even if there is no callback?
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.
SocketEventsFromFDs
doesn't drain anything, it just sets a bit mask based on which of the socket sets the given FD appears in. So this just avoids a bit of unnecessary work.
@@ -15,7 +15,11 @@ | |||
import("//build_overrides/build.gni") | |||
import("//build_overrides/chip.gni") | |||
|
|||
executable("network-manager-app") { | |||
declare_args() { | |||
matter_enable_ubus = false |
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.
Please document what this arg means.
UloopHandler::Register(); | ||
|
||
int status; | ||
if ((status = ubus_connect_ctx(&mContext, nullptr))) |
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.
My knowledge of ubus is nonexistent, so I am just rubber-stamping the ubus bits. If you need me to actually go read up on these APIs and do a proper review, please let me know.
PR #33968: Size comparison from a39c62e to d751d2c Full report (85 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, mbed, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
I will split it out into a separate PR |
@ksperling-apple this is quite an old PR and has approvals, but also merge conflicts. Could you review if it is appropriate to update or if it should be closed if not applicable anymore? |