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

Update 2.5-branch with relevant 2.4-branch cherry-picks #344

Merged

Conversation

markaj-nordic
Copy link
Contributor

List of cherry-picked commits:
5841923
66a5f33
e89b123

Reason: these should have been ported to the master branch prior to the v2.5.0 tag.
The master will be populated with these patches as a result of upcoming upmerge.

markaj-nordic and others added 3 commits November 2, 2023 11:35
…odel.* (#27886)

zap_cluster_list.py raises an error when the ZAP file
enables a cluster that is not implemented in the SDK. This
forces users to patch the SDK in order to use custom,
vendor-specific clusters.

Add EXTERNAL_CLUSTERS argument to chip_configure_data_model()
CMake function that takes a list of external cluster names
for which the default implementation should not included nor
required.

Usage example:
chip_configure_data_model(app
    INCLUDE_SERVER
    ZAP_FILE lock-app.zap
    EXTERNAL_CLUSTERS BASIC_INFORMATION_CLUSTER MY_CUSTOM_CLUSTER
)

Replace the existing zap_clusters_with_custom_implementation
argument of chip_data_model() GN template with new one:
external_clusters. The previous argument took a list of
cluster implementation directories to be skipped, so it was
only useful for bypassing the default implementations, but
could not be used for custom, vendor-specific clusters.
The new argument addresses both scenarios.

Usage example:
chip_data_model("lock-common") {
  zap_file = "lock-app.zap"
  ...
  external_clusters = [
    "BASIC_INFORMATION_CLUSTER",
    "MY_CUSTOM_CLUSTER",
  ]
}
…-server (#29857)

The current implementation of the door-lock server supports emitting
the LockOperationEvent only if the credential has been provided remotely.
In case we use a custom handling lock credential in the application
code the event is emitted only on the correct credential, but we also
need a mechanism that allows the door lock server to handle a lock
operation error when the wrong credential has been provided.

Added handling local lock operation error to emit LockOperationEvent
and call HandleWrongCodeEntry.

cherry-picked from b9d525e
@markaj-nordic markaj-nordic merged commit a764227 into nrfconnect:v2.5-branch Nov 3, 2023
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants