| /Zephyr-latest/subsys/bluetooth/controller/ll_sw/ |
| D | ll_feat.c | 38 uint64_t feature; in ll_set_host_feature() local
41 feature = BIT64(bit_number); in ll_set_host_feature()
42 if (!(feature & LL_FEAT_HOST_BIT_MASK)) { in ll_set_host_feature()
65 host_features |= feature; in ll_set_host_feature()
67 host_features &= ~feature; in ll_set_host_feature()
|
| /Zephyr-latest/samples/subsys/usb/audio/headphones_microphone/ |
| D | app.overlay | 10 feature-mute;
14 feature-volume;
21 feature-mute;
|
| /Zephyr-latest/samples/subsys/usb/audio/headset/ |
| D | app.overlay | 10 mic-feature-mute;
14 hp-feature-mute;
18 hp-feature-volume;
|
| /Zephyr-latest/doc/project/ |
| D | proposals.rst | 6 For feature tracking we use Github labels to classify new features and
11 block a release. This is an incremental enhancement to a feature that already
25 A request or plan to port an existing feature or enhancement to a particular
31 A label to group other GitHub issues that are part of a single feature or unit
36 This is the formal way for asking for a new feature in Zephyr and indicating its
38 willingness to drive implementation of the feature in an upcoming release, and
41 A feature request can also have a companion RFC with more details on the feature
44 - Label new features requests as ``feature-request``
45 - The TSC discusses new ``feature-request`` items regularly and triages them.
55 ``feature-request`` to ``feature`` with the target milestone and an assignee.
[all …]
|
| /Zephyr-latest/samples/bluetooth/bap_broadcast_sink/boards/ |
| D | nrf52833dk_nrf52833.overlay | 7 mic-feature-mute;
11 hp-feature-mute;
|
| D | nrf52840dongle_nrf52840.overlay | 7 mic-feature-mute;
11 hp-feature-mute;
|
| D | nrf5340dk_nrf5340_cpuapp.overlay | 7 mic-feature-mute;
11 hp-feature-mute;
|
| /Zephyr-latest/samples/bluetooth/bap_broadcast_source/boards/ |
| D | nrf52833dk_nrf52833.overlay | 7 mic-feature-mute;
11 hp-feature-mute;
|
| D | nrf52840dongle_nrf52840.overlay | 7 mic-feature-mute;
11 hp-feature-mute;
|
| D | nrf5340dk_nrf5340_cpuapp.overlay | 7 mic-feature-mute;
11 hp-feature-mute;
|
| /Zephyr-latest/tests/bluetooth/shell/boards/ |
| D | nrf5340dk_nrf5340_cpuapp.overlay | 7 mic-feature-mute;
11 hp-feature-mute;
|
| /Zephyr-latest/tests/bsim/bluetooth/mesh/src/ |
| D | test_heartbeat.c | 69 uint16_t feature = 0; in sub_hb_recv_cb() local
72 feature |= BT_MESH_FEAT_RELAY; in sub_hb_recv_cb()
76 feature |= BT_MESH_FEAT_PROXY; in sub_hb_recv_cb()
80 feature |= BT_MESH_FEAT_FRIEND; in sub_hb_recv_cb()
84 feature |= BT_MESH_FEAT_LOW_POWER; in sub_hb_recv_cb()
87 ASSERT_EQUAL(feature, feat); in sub_hb_recv_cb()
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | brg_cfg.rst | 6 With Bluetooth Mesh Protocol Specification version 1.1, the Bluetooth Mesh Subnet Bridge feature was
8 This feature allows mesh networks to use subnets for area isolation, but to also allow communication
11 The Bluetooth Mesh Subnet Bridge feature makes it possible for selected nodes in the network to act
15 The Subnet Bridge feature includes two models:
20 The Bridge Configuration Server model is mandatory for supporting the Subnet Bridge feature.
24 Subnet Bridge feature.
26 The configuration and management of the Subnet Bridge feature are handled using the Bridge
29 the Subnet Bridge feature.
34 To get a better understanding of the Subnet Bridge feature and its capabilities, an overview of a
67 Enabling or disabling the Subnet Bridge feature
[all …]
|
| D | proxy.rst | 6 The Proxy feature allows legacy devices like phones to access the Bluetooth Mesh network through
7 GATT. The Proxy feature is only compiled in if the :kconfig:option:`CONFIG_BT_MESH_GATT_PROXY`
8 option is set. The Proxy feature state is controlled by the :ref:`bluetooth_mesh_models_cfg_srv`,
11 Nodes with the Proxy feature enabled can advertise with Network Identity and Node Identity,
14 The GATT Proxy state indicates if the Proxy feature is supported.
19 A node supporting the Proxy feature and the :ref:`bluetooth_mesh_models_priv_beacon_srv` model can
34 :func:`bt_mesh_proxy_solicit` function. To enable this feature, the device must to be compiled with
|
| D | heartbeat.rst | 6 The Heartbeat feature provides functionality for monitoring Bluetooth Mesh nodes
9 The Heartbeat feature is configured through the :ref:`bluetooth_mesh_models_cfg_srv` model.
21 Available Heartbeat feature flags:
40 The node publishes a new Heartbeat message every time a feature changes. The
|
| /Zephyr-latest/samples/boards/nxp/mimxrt1170_evk_cm7/magic_addr/ |
| D | README.rst | 11 Magic Addr is a feature of FlexRAM that allows user to configure an interrupt
13 API for the flexram in zephyr to use this unique feature.
|
| /Zephyr-latest/tests/bsim/bluetooth/host/privacy/device/ |
| D | README.rst | 3 Privacy feature test
9 The tests check the following aspects of the Bluetooth privacy feature:
|
| /Zephyr-latest/samples/subsys/debug/debugmon/ |
| D | README.rst | 4 Configure the Debug Monitor feature on a Cortex-M processor.
9 The Debug Monitor sample shows a basic configuration of debug monitor feature.
24 #. Support Debug Monitor feature (available on Cortex-M processors with the exception of Cortex-M0)
|
| /Zephyr-latest/drivers/counter/ |
| D | Kconfig.nrfx | 12 # Internal flag which detects if PPI wrap feature is enabled for any instance
21 # Internal flag which detects if fixed top feature is enabled for any instance
|
| /Zephyr-latest/.github/ISSUE_TEMPLATE/ |
| D | 004_feature_request.md | 10 **Is your feature request related to a problem? Please describe.**
27 Add any other context or graphics (drag-and-drop an image) about the feature request here.
|
| /Zephyr-latest/scripts/footprint/ |
| D | upload_data.py | 27 def create_event(data, board, feature, commit, current_time, typ, application): argument
39 "feature": feature
118 feature = file_data[3]
134 create_event(data, board, feature, commit, current_time, typ, app)
|
| /Zephyr-latest/scripts/dts/python-devicetree/tests/test-bindings-include/ |
| D | README.rst | 1 This directory contains bindings used to test the 'include:' feature.
|
| /Zephyr-latest/doc/build/snippets/ |
| D | design.rst | 4 This page documents design goals for the snippets feature.
27 snippets feature will be possible without breaking backwards compatibility
30 - **applicable to purely "software" changes**: unlike the shields feature,
|
| /Zephyr-latest/doc/develop/api/ |
| D | design_guidelines.rst | 73 implemented without them. Examples of such feature include
79 In the case where a feature is determined to be optional the following
82 * Any data that is accessed only when the feature is enabled should be
89 feature is enabled, referencing the required Kconfig symbol by name.
93 * Where code specific to the feature is isolated in a source file that
98 * Where code specific to the feature is part of a source file that has
99 other content the feature-specific code should be conditionally
102 The Kconfig flag used to enable the feature should be added to the
|
| /Zephyr-latest/drivers/serial/ |
| D | Kconfig.altera | 13 bool "ALTERA UART end of packet feature"
16 Use driver command CMD_ENABLE_EOP and CMD_DISABLE_EOP to use the feature.
|
