CONFIG_BT_DIS_PNP_VID

Vendor ID

Type: hex

Help

The Vendor ID field is intended to uniquely identify the vendor of the
device. This field is used in conjunction with Vendor ID Source field,
which determines which organization assigned the Vendor ID field value.
Note: The Bluetooth Special Interest Group assigns Device ID Vendor ID,
and the USB Implementers Forum assigns Vendor IDs,
either of which can be used for the Vendor ID field value.
Device providers should procure the Vendor ID from the USB Implementers
Forum or the Company Identifier from the Bluetooth SIG.

Help

The Vendor ID field is intended to uniquely identify the vendor of the
device. This field is used in conjunction with Vendor ID Source field,
which determines which organization assigned the Vendor ID field value.
Note: The Bluetooth Special Interest Group assigns Device ID Vendor ID,
and the USB Implementers Forum assigns Vendor IDs,
either of which can be used for the Vendor ID field value.
Device providers should procure the Vendor ID from the USB Implementers
Forum or the Company Identifier from the Bluetooth SIG.

Direct dependencies

(BT_DIS_PNP && BT_DIS && BT_CONN && BT_RPC_STACK) || (BT_DIS_PNP && BT_DIS && BT_CONN && BT_HCI && BT)

(Includes any dependencies from ifs and menus.)

Defaults

0
0

Kconfig definitions

At <Zephyr>/subsys/bluetooth/services/Kconfig.dis:57

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:194 → <Zephyr>/subsys/bluetooth/services/Kconfig:9

Menu path: (Top) → Modules → nrf (/home/runner/work/sdk-nrf/sdk-nrf/ncs/nrf) → Nordic nRF Connect → Bluetooth Low Energy → BLE over nRF RPC → GATT Services → Enable GATT Device Information service → Enable PnP_ID characteristic

config BT_DIS_PNP_VID
    hex "Vendor ID"
    range 0 0xFFFF
    default 0
    depends on BT_DIS_PNP && BT_DIS && BT_CONN && BT_RPC_STACK
    help
      The Vendor ID field is intended to uniquely identify the vendor of the
      device. This field is used in conjunction with Vendor ID Source field,
      which determines which organization assigned the Vendor ID field value.
      Note: The Bluetooth Special Interest Group assigns Device ID Vendor ID,
      and the USB Implementers Forum assigns Vendor IDs,
      either of which can be used for the Vendor ID field value.
      Device providers should procure the Vendor ID from the USB Implementers
      Forum or the Company Identifier from the Bluetooth SIG.

At <Zephyr>/subsys/bluetooth/services/Kconfig.dis:57

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

Menu path: (Top) → Sub Systems and OS Services → Bluetooth → GATT Services → Enable GATT Device Information service → Enable PnP_ID characteristic

config BT_DIS_PNP_VID
    hex "Vendor ID"
    range 0 0xFFFF
    default 0
    depends on BT_DIS_PNP && BT_DIS && BT_CONN && BT_HCI && BT
    help
      The Vendor ID field is intended to uniquely identify the vendor of the
      device. This field is used in conjunction with Vendor ID Source field,
      which determines which organization assigned the Vendor ID field value.
      Note: The Bluetooth Special Interest Group assigns Device ID Vendor ID,
      and the USB Implementers Forum assigns Vendor IDs,
      either of which can be used for the Vendor ID field value.
      Device providers should procure the Vendor ID from the USB Implementers
      Forum or the Company Identifier from the Bluetooth SIG.

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