Home
last modified time | relevance | path

Searched full:features (Results 1 – 25 of 862) sorted by relevance

12345678910>>...35

/Zephyr-Core-3.5.0/doc/project/
Dproposals.rst6 For feature tracking we use Github labels to classify new features and
10 Changes to existing features that are not considered a bug and would not
21 implementation proposal and an owner. Features must go through an RFC process
34 The following workflow should be used to process features:.
44 - Label new features requests as ``feature-request``
46 Items are examined for similarity with existing features, how they fit with
69 plan is a tactical document designed to capture and track the features planned
97 is translated into an actionable plan built on specific features, enhancements,
100 The release plan communicates those features and enhancements slated for your
105 Items labeled as ``features`` are short or long term release items that shall
Drelease_process.rst11 balance of the latest technologies and features and excellent overall quality. A
13 the features that have actually been implemented, allowing the project to
15 features that are not ready yet.
69 new features has passed, and that the time to stabilize the next release of the
132 - Finalize target milestones for features in flight.
140 - No new features, ONLY stabilization and cosmetic changes, bug and doc fixes are allowed.
144 - No new features, ONLY stabilization and cosmetic changes, bug and doc fixes are allowed.
214 An LTS includes both mature and new features. API and feature maturity is
216 as we move from one LTS to the next giving users access to bleeding edge features
235 This guarantees that we release many of the highlighted and core features with
[all …]
Dcode_flow.rst16 of new features to be introduced into the main branch when ready. Creating a new
20 Zephyr, the introduction of fixes and new features, if approved by the TSC,
27 Development in collaboration branches before features go to mainline allows teams to
36 By dedicating an isolated branch to complex features, it's
/Zephyr-Core-3.5.0/dts/bindings/qspi/
Dst,stm32-qspi.yaml42 the channel number, the slot number, channel configuration and finally features.
43 (depending on the type of DMA: 'features' is optional)
46 (not dmamux channel). The request is given by the DMAMUX (no 'features' required).
48 For example with DMA 2 for TX/RX on QSPI like stm32l496 (no 'features')
51 For example with a DMAMUX for TX/RX on QSPI like stm32wb55 (no 'features')
/Zephyr-Core-3.5.0/doc/security/
Dhardening-tool.rst12 #. Disabling features and compilation flags that might lead to security vulnerabilities (ex. making
13 sure that no "experimental" features are being used, disabling features typically used for
15 #. Enabling optional features that can lead to improve security (ex. stack sentinel, hardware stack
16 protection, etc.). Some of these features might be hardware-dependent.
/Zephyr-Core-3.5.0/subsys/bluetooth/services/ots/
Dots.c69 /* OACP features supported by Kconfig */
84 /* OLCP features supported by Kconfig */
128 return bt_gatt_attr_read(conn, attr, buf, len, offset, &ots->features, in ots_feature_read()
129 sizeof(ots->features)); in ots_feature_read()
329 if (!ots_obj_validate_prop_against_oacp(created_desc.props, ots->features.oacp)) { in bt_ots_obj_add_internal()
331 created_desc.props, ots->features.oacp); in bt_ots_obj_add_internal()
457 !BT_OTS_OACP_GET_FEAT_CREATE(ots_init->features.oacp), in bt_ots_init()
464 !BT_OTS_OACP_GET_FEAT_READ(ots_init->features.oacp), in bt_ots_init()
467 !BT_OTS_OACP_GET_FEAT_WRITE(ots_init->features.oacp), in bt_ots_init()
473 /* Check OACP supported features against Kconfig. */ in bt_ots_init()
[all …]
/Zephyr-Core-3.5.0/modules/openthread/
DKconfig11 menu "OpenThread stack features"
12 rsource "Kconfig.features"
/Zephyr-Core-3.5.0/doc/connectivity/networking/api/
Dethernet.rst24 Zephyr supports following Ethernet features:
38 Not all Ethernet device drivers support all of these features. You can
40 currently supported Ethernet features.
/Zephyr-Core-3.5.0/doc/templates/
Dboard.tmpl8 [A short description about the board, its main features and availability]
22 Supported Features
24 [List of supported features and level of support in Zephyr]
/Zephyr-Core-3.5.0/samples/bluetooth/hap_ha/src/
Dhas_server.c78 static struct bt_has_features_param features = { variable
89 features.type = BT_HAS_HEARING_AID_TYPE_BINAURAL; in has_server_init()
91 features.type = BT_HAS_HEARING_AID_TYPE_BANDED; in has_server_init()
94 err = bt_has_register(&features); in has_server_init()
/Zephyr-Core-3.5.0/subsys/bluetooth/audio/
DKconfig15 features that are available may depend on other features
47 features are enabled.
Dhas.c37 !BITS_CHANGED(_new_value, (has.features & BT_HAS_FEAT_HEARING_AID_TYPE_MASK))
39 !BITS_CHANGED(_new_value, ((has.features & BT_HAS_FEAT_PRESET_SYNC_SUPP) != 0 ? 1 : 0))
41 !BITS_CHANGED(_new_value, ((has.features & BT_HAS_FEAT_INDEPENDENT_PRESETS) != 0 ? 1 : 0))
95 if (offset > sizeof(has.features)) { in read_features()
99 return bt_gatt_attr_read(conn, attr, buf, len, offset, &has.features, in read_features()
100 sizeof(has.features)); in read_features()
162 /* Features notification work */
994 if ((has.features & BT_HAS_FEAT_PRESET_SYNC_SUPP) != 0) { in handle_control_point_op()
1000 if ((has.features & BT_HAS_FEAT_PRESET_SYNC_SUPP) != 0) { in handle_control_point_op()
1006 if ((has.features & BT_HAS_FEAT_PRESET_SYNC_SUPP) != 0) { in handle_control_point_op()
[all …]
/Zephyr-Core-3.5.0/include/zephyr/drivers/dma/
Ddma_stm32.h46 DT_INST_DMAS_CELL_BY_NAME(id, dir, features)
75 /* macro for features (only for dma-v1) */
77 #define STM32_DMA_FEATURES_FIFO_THRESHOLD(features) (features & 0x3) argument
79 #define STM32_DMA_FEATURES_FIFO_THRESHOLD(features) 0 argument
/Zephyr-Core-3.5.0/boards/arm/lpcxpresso55s36/
Dlpcxpresso55s36-pinctrl.dtsi13 /* Configures pin routing and optionally pin electrical features. */
22 /* Configures pin routing and optionally pin electrical features. */
31 /* Configures pin routing and optionally pin electrical features. */
50 /* Configures pin routing and optionally pin electrical features. */
/Zephyr-Core-3.5.0/boards/arm/bcm958402m2_m7/doc/
Dindex.rst13 The bcm958402m2_m7 is a PCIe card with the following physical features:
19 Supported Features
22 hardware features:
32 Other hardware features have not been enabled yet for this board.
/Zephyr-Core-3.5.0/boards/arm/bcm958401m2/doc/
Dindex.rst13 The BCM958401M2 is a PCIe card with the following physical features:
19 Supported Features
22 features:
32 Other hardware features have not been enabled yet for this board.
/Zephyr-Core-3.5.0/boards/arm64/bcm958402m2_a72/doc/
Dindex.rst13 The bcm958402m2_a72 is a PCIe card with the following physical features:
19 Supported Features
22 hardware features:
32 Other hardware features have not been enabled yet for this board.
/Zephyr-Core-3.5.0/.github/ISSUE_TEMPLATE/
D002_enhancement.md3 about: Suggest enhancements to existing features
17 A clear and concise description of any alternative solutions or features you've considered.
/Zephyr-Core-3.5.0/share/sysbuild/
DKconfig26 features are enabled.
40 features are enabled.
/Zephyr-Core-3.5.0/include/zephyr/bluetooth/services/
Dots.h267 * @param feat OTS features.
274 * @param feat OTS features.
281 * @param feat OTS features.
288 * @param feat OTS features.
295 * @param feat OTS features.
302 * @param feat OTS features.
309 * @param feat OTS features.
316 * @param feat OTS features.
323 * @param feat OTS features.
330 * @param feat OTS features.
[all …]
/Zephyr-Core-3.5.0/dts/bindings/timer/
Dgd,gd32-timer.yaml37 Indicates if timer has advanced features. Such features include break
/Zephyr-Core-3.5.0/subsys/net/ip/
DKconfig.stack16 be bigger depending on what features are enabled.
25 be bigger depending on what features are enabled.
/Zephyr-Core-3.5.0/tests/bluetooth/controller/ctrl_feature_exchange/src/
Dmain.c102 sys_put_le64(set_featureset[feat_counter], local_feature_req.features); in ZTEST()
104 sys_put_le64(rsp_featureset[feat_counter], remote_feature_rsp.features); in ZTEST()
106 sys_put_le64(exp_rsp_featureset[feat_counter], exp_remote_feature_rsp.features); in ZTEST()
138 /* Add host feature bit to expected features bit mask */ in ZTEST()
141 sys_put_le64(set_featureset[0], local_feature_req.features); in ZTEST()
205 sys_put_le64(DEFAULT_FEATURE, local_feature_req.features); in ZTEST()
330 sys_put_le64(set_featureset[feat_count], remote_feature_req.features); in ZTEST()
331 sys_put_le64(exp_featureset[feat_count], local_feature_rsp.features); in ZTEST()
403 sys_put_le64(set_featureset[feat_count], remote_feature_req.features); in ZTEST()
404 sys_put_le64(exp_featureset[feat_count], local_feature_rsp.features); in ZTEST()
[all …]
/Zephyr-Core-3.5.0/boards/arc/qemu_arc/doc/
Dindex.rst12 The following features of ARC ISA cores are currently supported:
28 Supported Features
31 The following hardware features are supported:
43 The kernel currently does not support other hardware features on this platform.
61 The following platform features are unsupported:
/Zephyr-Core-3.5.0/subsys/bluetooth/host/
Dhfp_internal.h14 /* HFP AG Features */
28 /* HFP HF Features */
40 /* HFP HF Supported features */

12345678910>>...35