samples: matter: Optimized LIT configuration

[kkasperczyk-no]

The LIT configuration in Matter samples can be slightly changed to achieve lower power consumption.

Additionally, added piece of documentation explaining how to configure the radio driver calibration period.

[NordicBuilder]

CI Information

^{To view the history of this post, clich the 'edited' button above}
Build number: 9

Inputs:

Sources:

sdk-nrf: PR head: 6af29dbffb81702ce73a7135abd90fcf90dcd8c1

more details

sdk-nrf:

PR head: 6af29dbffb81702ce73a7135abd90fcf90dcd8c1
merge base: 1aed4564bcee2393536df83365b474800166ccf9
target head (main): 0a56342ad66c274e2b9d3ca6bed5dfc8d8793bd0
Diff

Github labels

Enabled	Name	Description
	ci-disabled	Disable the ci execution
	ci-all-test	Run all of ci, no test spec filtering will be done
	ci-force-downstream	Force execution of downstream even if twister fails
	ci-run-twister	Force run twister
	ci-run-zephyr-twister	Force run zephyr twister

List of changed files detected by CI (4)

doc
│  ├── nrf
│  │  ├── protocols
│  │  │  ├── matter
│  │  │  │  ├── getting_started
│  │  │  │  │  │ low_power_configuration.rst
│  │  ├── releases_and_maturity
│  │  │  ├── releases
│  │  │  │  │ release-notes-changelog.rst
samples
│  ├── matter
│  │  ├── light_switch
│  │  │  ├── snippets
│  │  │  │  ├── lit_icd
│  │  │  │  │  │ lit_icd.conf
│  │  ├── smoke_co_alarm
│  │  │  │ Kconfig

Outputs:

Toolchain

Version: 4cff34261a
Build docker image: docker-dtr.nordicsemi.no/sw-production/ncs-build:4cff34261a_bece0367df

Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped; ⚠️ Quarantine

• ◻️ Toolchain - Skipped: existing toolchain is used
• ✅ Build twister
  • sdk-nrf test count: 92
• ✅ Integration tests
  • ✅ test-fw-nrfconnect-chip

Disabled integration tests

• • desktop52_verification
  • doc-internal
  • test_ble_nrf_config
  • test-fw-nrfconnect-apps
  • test-fw-nrfconnect-ble_mesh
  • test-fw-nrfconnect-ble_samples
  • test-fw-nrfconnect-boot
  • test-fw-nrfconnect-fem
  • test-fw-nrfconnect-nfc
  • test-fw-nrfconnect-nrf-iot_cloud
  • test-fw-nrfconnect-nrf-iot_lwm2m
  • test-fw-nrfconnect-nrf-iot_mosh
  • test-fw-nrfconnect-nrf-iot_positioning
  • test-fw-nrfconnect-nrf-iot_samples
  • test-fw-nrfconnect-nrf-iot_serial_lte_modem
  • test-fw-nrfconnect-nrf-iot_thingy91
  • test-fw-nrfconnect-nrf-iot_zephyr_lwm2m
  • test-fw-nrfconnect-nrf_crypto
  • test-fw-nrfconnect-proprietary_esb
  • test-fw-nrfconnect-ps
  • test-fw-nrfconnect-rpc
  • test-fw-nrfconnect-rs
  • test-fw-nrfconnect-tfm
  • test-fw-nrfconnect-thread
  • test-fw-nrfconnect-zigbee
  • test-low-level
  • test-sdk-audio
  • test-sdk-dfu
  • test-sdk-find-my
  • test-sdk-mcuboot
  • test-sdk-pmic-samples
  • test-sdk-sidewalk
  • test-sdk-wifi
  • test-secdom-samples-public

Note: This message is automatically posted and updated by the CI

[NordicBuilder]

You can find the documentation preview for this PR at this link.

Note: This comment is automatically posted by the Documentation Publish GitHub Action.

[peknis]

Approved with a nit.

[kkasperczyk-no]

@nrfconnect/ncs-co-build-system please review

[nordicjm]

why are you setting defaults in a Kconfig file? These should be in a prj.conf file...

[kkasperczyk-no]

The overall idea was to keep the configs common to all variants (in case of having multiple prj.confs) in Kconfig, to avoid copying it across multiple files. I can move this one now, but please note that there are already other configs configured in the same way, so it will result in inconsistency and I would not like to refactor all samples in scope of this PR.

[kkasperczyk-no]

Please request changing the way how Matter samples are configured in a separate ticket, if you find it necessary. This PR only changes two values, so I don't want to bring the inconsistency or increase the scope.