-
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
Repost "[esp32]: Do not setup DeviceInfoProvider within PlatformMgr" #21109
Repost "[esp32]: Do not setup DeviceInfoProvider within PlatformMgr" #21109
Conversation
PR #21109: Size comparison from 27fc7b7 to 3081d4b Increases (3 builds for cc13x2_26x2, cyw30739, nrfconnect)
Decreases (5 builds for esp32, k32w, nrfconnect, telink)
Full report (43 builds for bl602, cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, p6, telink)
|
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.
@dhrishi Can you please review?
This is a temporary state, per #18236 (comment), and the ESP32 implementation is meant to be modified to use factory data. Please make sure that @dhrishi or @wqx6 approves this before merging it, since in the past they have explicitly asked for this change to not be made. |
As discussed, @wqx6 may be unavailable due to SVE, we can merge this PR as this uses the generic DeviceInfoProvider. We will add a follow-on PR with any platform specific required changes required on top (cc @shubhamdp). Will approve this now. |
Sorry for the later replying due to sve. I have discussed with @shubhamdp and he will add the device info(Fixed label, SupportedLocales and SupportedCalendarTypes) in generate_esp32_chip_factory_bin.py and then we will add the DeviceInfoProviderImpl for ESP32 platform. |
Had a discussion with @wqx6 offline and we can merge this PR. We'll add a PR for ESP32 for this along with the support for reading this configurations from the factory partition. |
…21164) Co-authored-by: Yufeng Wang <[email protected]>
Use common example for DeviceInfoProvider implementation. Also see this PR: project-chip#21109 Signed-off-by: Marius Tache <[email protected]>
Use common example for DeviceInfoProvider implementation. Also see this PR: project-chip#21109 Signed-off-by: Marius Tache <[email protected]>
Use common example for DeviceInfoProvider implementation. Also see this PR: project-chip#21109 Signed-off-by: Marius Tache <[email protected]>
Use common example for DeviceInfoProvider implementation. Also see this PR: project-chip#21109 Signed-off-by: Marius Tache <[email protected]>
Use common example for DeviceInfoProvider implementation. Also see this PR: project-chip#21109 Signed-off-by: Marius Tache <[email protected]>
Problem
What is being fixed? Examples:
Currently, we call SetDiagnosticDataProvider within PaltformMgr separately on ESP32 platform. And this will cause call DiagnosticDataProvider get set up on both client and server side.
Change overview
Use common DeviceInfoProvider implementation instead of platform specific version
Please note, currently, some functions of DeviceInfoProvider does not work since storage delegate has not been setup for DeviceInfoProvider. This PR does not solve this issue either, it will be addressed in a separate PR.
Testing
How was this tested? (at least one bullet point required)