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

[CSA-CP] Rename CLUSTER_MASK_ and ATTIBUTE_MASK defines to differentiate with … #342

Merged
merged 2 commits into from
Mar 14, 2025

Conversation

jmartinez-silabs
Copy link
Contributor

-- Cherry Pick of project-chip/connectedhomeip#37618 --
THIS fix multiple build warning for the cmp app due to redefinitions between Matter and Zigbee

…the Zigbee ones.
Clean up some scene defines and delete the now empty header att-storage.h.

CLUSTER_MASK_... -> MATTER_CLUSTER_FLAG_...
ATTRIBUTE_MASK_... -> MATTER_ATTRIBUTE_FLAG_...
Those defines are tightly coupled with the ZAP_CLUSTER_MASK and ZAP_ATTRIBUTE_MASK macros. Those public APIs are not easily modifiable to use more adequate bitflags. It would require some rework and zap changes.

Delete unused defines MATTER_DM_SCENE_TABLE_NULL_INDEX, MATTER_DM_SCENE_TABLE_UNUSED_ENDPOINT_ID and
ZCL_SCENES_CLUSTER_MAXIMUM_NAME_LENGTH

move ZCL_SCENES_GLOBAL_SCENE_GROUP_ID and ZCL_SCENES_GLOBAL_SCENE_SCENE_ID to be const members of the ScenesServer class

Testing
No behaviour change. Only a rename and/or move of defines or constants location.
Locally built for Silabs platform.
CI to validate other builds

…… (#37618)

* Rename CLUSTER_MASK_ and ATTIBUTE_MASK defines to differentiate with the zigbee ones. Cleanup some scene defines and delete the now empty head att-storage.h

* Address comment, replace _BITMAP_ by _FLAG_
@jmartinez-silabs jmartinez-silabs added the csa-cp This TAG indicates that this commit is a cherry-pick from a CSA commit. label Mar 13, 2025
@jmartinez-silabs jmartinez-silabs requested a review from a team as a code owner March 13, 2025 20:39
Copy link
Contributor

@mkardous-silabs mkardous-silabs left a comment

Choose a reason for hiding this comment

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

How do we manage CSA-CP and SL-ONLY combos?

When this trickles down to main we will need to do the same changes to our specific apps.

@jmartinez-silabs
Copy link
Contributor Author

@mkardous-silabs This PR does not have any changes to our specific apps. so it doesn't apply here.
But for a general answers, I would say the SL-ONLY trumps the CSA-CP

If you apply a SL-ONLY from a release branch to Main, which contained a CSA-CP, the CP application will lead to no diff/drop commits on the CSA-CP part

@mkardous-silabs mkardous-silabs merged commit 1f1eb53 into release_2.5-1.4 Mar 14, 2025
53 checks passed
@mkardous-silabs mkardous-silabs deleted the cmp_redefinition_fixes branch March 14, 2025 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
csa-cp This TAG indicates that this commit is a cherry-pick from a CSA commit.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants