-
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
Add support for the AttributeList attribute. #12660
Add support for the AttributeList attribute. #12660
Conversation
eedead2
to
6d63a6e
Compare
PR #12660: Size comparison from 21392ef to 6d63a6e Increases above 0.2%:
Increases (25 builds for efr32, esp32, k32w, linux, mbed, p6, qpg, telink)
Full report (29 builds for efr32, esp32, k32w, linux, mbed, p6, qpg, telink)
|
6d63a6e
to
e22c4e8
Compare
The size increase seems to largely be from emberAfAttributeValueListSize and emberAfCopyList. I'll see what I can do to make those smaller. |
PR #12660: Size comparison from f647393 to e22c4e8 Increases above 0.2%:
Increases (20 builds for efr32, k32w, linux, p6, qpg, telink)
Full report (22 builds for efr32, k32w, linux, p6, qpg, telink)
|
e22c4e8
to
a726b8d
Compare
PR #12660: Size comparison from f647393 to a726b8d Increases above 0.2%:
Increases (32 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
Full report (39 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, 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.
I was hoping that adding this global attribute to
<global> |
Just curious, what were the missing parts for adding it there and fixing the places where you want to handle it as external
?
Hmm. So adding it there does let me get rid of the manual changes to cluster-objects.zapt and Attributes.zapt, since those just look at the attribute's existence, not whether it's enabled. What it does not do on its own is enable the controller cluster codegen we actually need, but maybe I can figure out a better workaround for that. |
a726b8d
to
231e343
Compare
231e343
to
b6fb909
Compare
PR #12660: Size comparison from 051685b to b6fb909 Increases above 0.2%:
Increases (32 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
Full report (39 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
b6fb909
to
f46762b
Compare
PR #12660: Size comparison from 7ce81e5 to f46762b Increases above 0.2%:
Increases (32 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
Full report (39 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
Getting this into the ZAP database as things stand involves modifying every single cluster XML and every single cluster definition in every single .zap file. Instead of that, we just enable it for the controller codegen and manually work around it not being present in endpoint_config.
f46762b
to
aaa209a
Compare
PR #12660: Size comparison from 6f89b9b to aaa209a Increases above 0.2%:
Increases (32 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
Full report (39 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
fast track: change made by domain owner, has been up sufficiently for cross timezone review, unit test contained in the change |
@mrjerryjohns @yufengwangca @erjiaqing could one of you take a look at this? Would really like a non-rubberstamp review here. |
PR project-chip#12660 seems to have refactored ReadSingleClusterData in such a way that the access control check may be skipped. (Possibly due to merge?) Fix this by refactoring the function to a sensible flow of checks. Progress towards project-chip#10239
* Fix and refactor ReadSingleClusterData PR #12660 seems to have refactored ReadSingleClusterData in such a way that the access control check may be skipped. (Possibly due to merge?) Fix this by refactoring the function to a sensible flow of checks. Progress towards #10239 * Apply review comment. Co-authored-by: Boris Zbarsky <[email protected]>
* Fix and refactor ReadSingleClusterData PR project-chip#12660 seems to have refactored ReadSingleClusterData in such a way that the access control check may be skipped. (Possibly due to merge?) Fix this by refactoring the function to a sensible flow of checks. Progress towards project-chip#10239 * Apply review comment. Co-authored-by: Boris Zbarsky <[email protected]>
* Fix and refactor ReadSingleClusterData PR project-chip#12660 seems to have refactored ReadSingleClusterData in such a way that the access control check may be skipped. (Possibly due to merge?) Fix this by refactoring the function to a sensible flow of checks. Progress towards project-chip#10239 * Apply review comment. Co-authored-by: Boris Zbarsky <[email protected]>
Getting this into the ZAP database as things stand involves modifying
every single cluster XML and every single cluster definition in every
single .zap file. Instead of that, we just enable it for the
controller codegen and manually work around it not being present in
endpoint_config.
Problem
No support for global AttributeList attribute.
Change overview
Add support.
Testing
Added YAML test with a cluster we already had a test file for.
Fixes #12055