CONFIG_BT_USER_PHY_UPDATE

User control of PHY Update Procedure

Type: bool

Help

Enable application access to initiate the PHY Update Procedure.
The application can also register a callback to be notified about PHY
changes on the connection. The current PHY info is available in the
connection info.

Help

Enable application access to initiate the PHY Update Procedure.
The application can also register a callback to be notified about PHY
changes on the connection. The current PHY info is available in the
connection info.

Direct dependencies

(BT_PHY_UPDATE && BT_CONN && BT_HCI_HOST && BT_RPC_STACK) || (BT_PHY_UPDATE && BT_CONN && BT_HCI_HOST && BT_HCI && BT)

(Includes any dependencies from ifs and menus.)

Defaults

No defaults. Implicitly defaults to n.

Kconfig definitions

At <Zephyr>/subsys/bluetooth/host/Kconfig:205

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:33 → <Zephyr>/modules/Kconfig:6 → <nRF>/doc/_build/kconfig/Kconfig.modules:2 → <nRF>/Kconfig.nrf:92 → <nRF>/subsys/Kconfig:10 → <nRF>/subsys/bluetooth/Kconfig:38 → <nRF>/subsys/bluetooth/rpc/Kconfig:196

Menu path: (Top) → Modules → nrf (/home/runner/work/sdk-nrf/sdk-nrf/ncs/nrf) → Nordic nRF Connect → Bluetooth Low Energy → BLE over nRF RPC

config BT_USER_PHY_UPDATE
    bool "User control of PHY Update Procedure"
    depends on BT_PHY_UPDATE && BT_CONN && BT_HCI_HOST && BT_RPC_STACK
    help
      Enable application access to initiate the PHY Update Procedure.
      The application can also register a callback to be notified about PHY
      changes on the connection. The current PHY info is available in the
      connection info.

At <Zephyr>/subsys/bluetooth/host/Kconfig:205

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:44 → <Zephyr>/subsys/Kconfig:9 → <Zephyr>/subsys/bluetooth/Kconfig:180

Menu path: (Top) → Sub Systems and OS Services → Bluetooth

config BT_USER_PHY_UPDATE
    bool "User control of PHY Update Procedure"
    depends on BT_PHY_UPDATE && BT_CONN && BT_HCI_HOST && BT_HCI && BT
    help
      Enable application access to initiate the PHY Update Procedure.
      The application can also register a callback to be notified about PHY
      changes on the connection. The current PHY info is available in the
      connection info.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)