-
Notifications
You must be signed in to change notification settings - Fork 2.2k
[Cameras] Add Alchemy generated XML for all Camera device types #39891
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
Conversation
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.
Code Review
This pull request introduces new camera device types and updates existing ones, generated via the Alchemy tool. The changes also include extensive XML formatting updates for consistency. The new device definitions and formatting changes are mostly sound, but I've identified one critical issue where a new device type is missing a required element, which could lead to processing failures.
PR #39891: Size comparison from 961f1c3 to 3ecf51e Full report (3 builds for cc32xx, stm32)
|
PR #39891: Size comparison from 961f1c3 to 1f6a844 Full report (3 builds for cc32xx, stm32)
|
PR #39891: Size comparison from 961f1c3 to 5208bc0 Full report (3 builds for cc32xx, stm32)
|
PR #39891: Size comparison from 4a0a8cf to 6efe3c1 Full report (3 builds for cc32xx, stm32)
|
PR #39891: Size comparison from 4a0a8cf to 1a348d1 Full report (71 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
…ect-chip#39891) * Add Alchemy generated XML for all Camera device types * Undo inadvertant back out of other in-progress work * Add results of Zap regen * Rerun regen after matter-devices update * Add omitted Zap generated file
Summary
Via Alchemy, generate new XML for all Camera defined device types that is present in matter-devices.xml
Testing
Run Zap re-gen
Clean CI
Readability checklist
The checklist below will help the reviewer finish PR review in time and keep the
code readable:
descriptive
“When in Rome…”
rule (coding style)
See: Pull Request Guidelines