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

bluetooth: fast_pair: fmdn: add restriction for fmdn tx power #20519

Merged
merged 1 commit into from
Feb 24, 2025

Conversation

kapi-no
Copy link
Contributor

@kapi-no kapi-no commented Feb 20, 2025

Added a restriction on the CONFIG_BT_FAST_PAIR_FMDN_TX_POWER Kconfig option in the Find My Device Network (FMDN) extension configuration. This Kconfig option should now be set to 0 at minimum as the Fast Pair specification now requires that the conducted Bluetooth transmit power for FMDN advertisements must not be lower than 0 dBm.

Ref: NCSDK-30857

@kapi-no kapi-no requested review from a team as code owners February 20, 2025 11:25
@github-actions github-actions bot added the doc-required PR must not be merged without tech writer approval. label Feb 20, 2025
Copy link

github-actions bot commented Feb 20, 2025

After documentation is built, you will find the preview for this PR here.

Preview links for modified nRF Connect SDK documents:

https://ncsdoc.z6.web.core.windows.net/PR-20519/nrf/external_comp/bt_fast_pair.html
https://ncsdoc.z6.web.core.windows.net/PR-20519/nrf/releases_and_maturity/releases/release-notes-changelog.html

@NordicBuilder
Copy link
Contributor

NordicBuilder commented Feb 20, 2025

CI Information

To view the history of this post, clich the 'edited' button above
Build number: 7

Inputs:

Sources:

sdk-nrf: PR head: 34565293d6fa36d8139399df3dc9a6c5a56c48f9

more details

sdk-nrf:

PR head: 34565293d6fa36d8139399df3dc9a6c5a56c48f9
merge base: ef49118310251ad3b04b8b9e3b5ba0a2693dbaf6
target head (main): 85bb3179eeda6d4c4aad9b7a3c745d072e38bf42
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 (3)
doc
│  ├── nrf
│  │  ├── external_comp
│  │  │  │ bt_fast_pair.rst
│  │  ├── releases_and_maturity
│  │  │  ├── releases
│  │  │  │  │ release-notes-changelog.rst
subsys
│  ├── bluetooth
│  │  ├── services
│  │  │  ├── fast_pair
│  │  │  │  ├── fmdn
│  │  │  │  │  │ Kconfig

Outputs:

Toolchain

Version: aedb4c0245
Build docker image: docker-dtr.nordicsemi.no/sw-production/ncs-build:aedb4c0245_bece0367df

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

  • ◻️ Toolchain - Skipped: existing toolchain is used
  • ✅ Build twister
    • sdk-nrf test count: 868
  • ✅ Integration tests
    • ✅ desktop52_verification
    • ✅ test_ble_nrf_config
    • ✅ test-fw-nrfconnect-ble_samples
    • ✅ test-sdk-find-my
Disabled integration tests
    • doc-internal
    • test-fw-nrfconnect-apps
    • test-fw-nrfconnect-ble_mesh
    • test-fw-nrfconnect-boot
    • test-fw-nrfconnect-chip
    • test-fw-nrfconnect-fem
    • test-fw-nrfconnect-nfc
    • test-fw-nrfconnect-nrf-iot_cloud
    • test-fw-nrfconnect-nrf-iot_libmodem-nrf
    • 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-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

@kapi-no kapi-no requested a review from MarekPieta February 21, 2025 09:43
@@ -580,6 +580,7 @@ For example, the "It's here" status message is displayed in the "Hot & Cold" exp

You can set the TX power for the FMDN advertising and connections using the :kconfig:option:`CONFIG_BT_FAST_PAIR_FMDN_TX_POWER` Kconfig option.
The configured value is directly used to set the TX power in the Bluetooth LE controller using an HCI command.
This Kconfig option should be set to 0 at minimum as the Fast Pair specification requires that the conducted Bluetooth transmit power for FMDN advertisements must not be lower than 0 dBm.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
This Kconfig option should be set to 0 at minimum as the Fast Pair specification requires that the conducted Bluetooth transmit power for FMDN advertisements must not be lower than 0 dBm.
This Kconfig option must be set to 0 at minimum as the Fast Pair specification requires that the conducted Bluetooth transmit power for FMDN advertisements must not be lower than 0 dBm.

* :ref:`bt_fast_pair_readme` library:

* Added a restriction on the :kconfig:option:`CONFIG_BT_FAST_PAIR_FMDN_TX_POWER` Kconfig option in the Find My Device Network (FMDN) extension configuration.
This Kconfig option should now be set to 0 at minimum as the Fast Pair specification now requires that the conducted Bluetooth transmit power for FMDN advertisements must not be lower than 0 dBm.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
This Kconfig option should now be set to 0 at minimum as the Fast Pair specification now requires that the conducted Bluetooth transmit power for FMDN advertisements must not be lower than 0 dBm.
This Kconfig option must now be set to 0 at minimum as the Fast Pair specification now requires that the conducted Bluetooth transmit power for FMDN advertisements must not be lower than 0 dBm.

@@ -26,6 +26,10 @@ config BT_FAST_PAIR_FMDN_TX_POWER
procedure of this library. The actual TX power value will be as close to
the desired configuration as possible.

This Kconfig should be set to zero at minimum. The Fast Pair specification
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
This Kconfig should be set to zero at minimum. The Fast Pair specification
This Kconfig must be set to zero at minimum. The Fast Pair specification

@@ -26,6 +26,10 @@ config BT_FAST_PAIR_FMDN_TX_POWER
procedure of this library. The actual TX power value will be as close to
the desired configuration as possible.

This Kconfig should be set to zero at minimum. The Fast Pair specification
requires that the conducted Bluetooth transmit power for FMDN advertisements
should be set to at least 0 dBm.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
should be set to at least 0 dBm.
must be set to at least 0 dBm.

@kapi-no kapi-no force-pushed the fp_fmdn_min_tx_power branch from aaa58fe to 96a3b4b Compare February 21, 2025 11:05
@kapi-no
Copy link
Contributor Author

kapi-no commented Feb 21, 2025

@MarekPieta , addressed your comments

@kapi-no kapi-no requested a review from MarekPieta February 21, 2025 11:05
@kapi-no kapi-no force-pushed the fp_fmdn_min_tx_power branch from 96a3b4b to f395682 Compare February 21, 2025 15:18
@kapi-no
Copy link
Contributor Author

kapi-no commented Feb 21, 2025

Simple rebase to resolve the conflicts

@kapi-no kapi-no force-pushed the fp_fmdn_min_tx_power branch from f395682 to 547fabd Compare February 24, 2025 08:19
@kapi-no kapi-no requested a review from nordicjm February 24, 2025 10:26
Added a restriction on the CONFIG_BT_FAST_PAIR_FMDN_TX_POWER Kconfig
option in the Find My Device Network (FMDN) extension configuration.
This Kconfig option should now be set to 0 at minimum as the Fast Pair
specification now requires that the conducted Bluetooth transmit power
for FMDN advertisements must not be lower than 0 dBm.

Ref: NCSDK-30857

Signed-off-by: Kamil Piszczek <Kamil.Piszczek@nordicsemi.no>
@kapi-no kapi-no force-pushed the fp_fmdn_min_tx_power branch from 547fabd to 3456529 Compare February 24, 2025 11:31
@kapi-no kapi-no merged commit 7669bb8 into nrfconnect:main Feb 24, 2025
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc-required PR must not be merged without tech writer approval.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants