Searched +full:feature +full:- +full:specific (Results 1 – 25 of 194) sorted by relevance
12345678
| /Zephyr-Core-3.5.0/dts/bindings/usb/ |
| D | usb-audio-hp.yaml | 2 # SPDX-License-Identifier: Apache-2.0
4 # Specific fields for USB audio headphones.
6 description: USB Audio headphones specific fields.
8 compatible: "usb-audio-hp"
10 include: [usb-audio.yaml, usb-audio-feature-volume.yaml]
17 - 8
18 - 16
19 - 24
20 - 32
22 channel-l:
[all …]
|
| D | usb-audio-mic.yaml | 2 # SPDX-License-Identifier: Apache-2.0
4 # Specific fields for USB audio microphone.
6 description: USB Audio microphone specific fields.
8 compatible: "usb-audio-mic"
10 include: usb-audio.yaml
17 - 8
18 - 16
19 - 24
20 - 32
21 sync-type:
[all …]
|
| D | usb-audio-hs.yaml | 2 # SPDX-License-Identifier: Apache-2.0
4 # Specific fields for USB audio headset.
6 description: USB Audio headset specific fields.
8 compatible: "usb-audio-hs"
10 include: [usb-audio.yaml, usb-audio-feature-volume.yaml]
13 mic-resolution:
17 - 8
18 - 16
19 - 24
20 - 32
[all …]
|
| D | usb-audio-feature-volume.yaml | 2 # SPDX-License-Identifier: Apache-2.0
4 # Specific fields for USB volume control.
6 description: USB volume control specific fields.
8 compatible: "usb-audio-feature-volume"
13 volume-max:
19 The range from +127.9961 dB (0x7FFF) down to -127.9961 dB (0x8001).
20 Valid range: 0 - 0xFFFF
21 volume-min:
27 The range from +127.9961 dB (0x7FFF) down to -127.9961 dB (0x8001).
28 Valid range: 0 - 0xFFFF
[all …]
|
| /Zephyr-Core-3.5.0/doc/develop/api/ |
| D | design_guidelines.rst | 23 * The next parameter(s) should be additional information specific to the
35 specific to the code that also defines the callback function. In those
63 counter channel timed-out and the counter value at which the timeout
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.
92 the unsupported API will result in a link-time error.
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
[all …]
|
| /Zephyr-Core-3.5.0/doc/project/ |
| D | proposals.rst | 1 .. _feature-tracking:
3 Feature Tracking
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
14 Feature request
19 Feature
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
[all …]
|
| /Zephyr-Core-3.5.0/doc/build/snippets/ |
| D | design.rst | 4 This page documents design goals for the snippets feature.
7 .. _Issue #51834: https://github.com/zephyrproject-rtos/zephyr/issues/51834
9 - **extensible**: for example, it is possible to add board support for an
10 existing built-in snippet without modifying the zephyr repository
12 - **composable**: it is possible to use multiple snippets at once, for example
15 .. code-block:: console
17 west build -S <snippet1> -S <snippet2> ...
19 - **able to combine multiple types of configuration**: snippets make it possible
23 - **specializable**: for example, it is possible to customize a snippet's
26 - **future-proof and backwards-compatible**: arbitrary future changes to the
[all …]
|
| /Zephyr-Core-3.5.0/doc/connectivity/bluetooth/ |
| D | overview.rst | 1 .. _bluetooth-overview:
15 grown to be mature and feature-rich, as can be seen in the section below.
20 Zephyr comes integrated with a feature-rich and highly configurable
34 * Controller-only (HCI) over UART, SPI, USB and IPC physical transports
35 * Host-only over UART, SPI, and IPC (shared memory)
38 * Bluetooth-SIG qualified
47 * Concurrent multi-protocol support ready
52 real-time specifics so that they can be encapsulated in a hardware-specific
74 * Pairing support, including the Secure Connections feature from Bluetooth 4.2
76 * Non-volatile storage support for permanent storage of Bluetooth-specific
[all …]
|
| /Zephyr-Core-3.5.0/kernel/ |
| D | compiler_stack_protect.c | 2 * Copyright (c) 2012-2014 Wind River Systems, Inc.
4 * SPDX-License-Identifier: Apache-2.0
12 * using canaries. This feature is enabled with configuration
15 * When this feature is enabled, the compiler generated code refers to
19 #include <zephyr/toolchain.h> /* compiler specific configurations */
|
| /Zephyr-Core-3.5.0/subsys/bluetooth/controller/ |
| D | Kconfig.df | 4 # SPDX-License-Identifier: Apache-2.0
8 # It is required to enable it when Controller supports any DF related feature
73 # BT Core spec 5.1, Vol 6, Part B, sec. 4.6 Feature Support
76 bool "Antenna switching during CTE transmission (AoD) feature"
84 bool "Antenna switching during CTE reception (AoA) feature"
92 bool "Reception of Constant Tone Extension feature"
100 bool "Connection CTE Request feature"
103 Enable support for Bluetooth v5.1 Connection CTE Request feature
107 bool "Connection CTE Response feature"
110 Enable support for Bluetooth v5.1 Connection CTE Response feature
[all …]
|
| /Zephyr-Core-3.5.0/dts/bindings/gpio/ |
| D | richtek,rt1718s.yaml | 2 # SPDX-License-Identifier: Apache-2.0
9 address. Feature-specific(GPIO, TCPC) properties should be placed in a child
17 irq-gpios = <&gpioe 1 (GPIO_PULL_UP | GPIO_ACTIVE_LOW)>;
20 compatible = "richtek,rt1718s-gpio-port";
22 gpio-controller;
23 #gpio-cells = <2>;
31 include: [i2c-device.yaml]
34 irq-gpios:
35 type: phandle-array
|
| /Zephyr-Core-3.5.0/subsys/bluetooth/controller/ll_sw/ |
| D | ull_conn_types.h | 2 * Copyright (c) 2018-2019 Nordic Semiconductor ASA
4 * SPDX-License-Identifier: Apache-2.0
69 uint32_t ticks_at_expire; /* Vendor specific tick units */
70 uint32_t remainder; /* Vendor specific remainder fraction of a tick unit */
82 * As of today only 36 feature bits are in use,
93 * verified when feature exchange procedure has completed, valid member is set to 1.
97 * Stores features common for two connected devices. Before feature exchange
99 * supported by local device. After completion of the procedure, the feature set
|
| /Zephyr-Core-3.5.0/.github/ISSUE_TEMPLATE/ |
| D | 001_bug_report.md | 1 ---
8 ---
11 Github Discussions (https://github.com/zephyrproject-rtos/zephyr/discussions)
16 (https://github.com/zephyrproject-rtos/zephyr/). If the bug is for a project
17 fork (such as NCS) specific feature, please open an issue in the fork project
25 - What target platform are you using?
26 - What have you tried to diagnose or workaround this issue?
27 - Is this a regression? If yes, have you been able to "git bisect" it to a
28 specific commit?
29 - ...
[all …]
|
| /Zephyr-Core-3.5.0/include/zephyr/usb/class/ |
| D | usb_audio.h | 6 * SPDX-License-Identifier: Apache-2.0
14 * - USB Device Class Definition for Audio Devices (audio10.pdf)
17 * - USB Device Class Definition for Audio Data Formats (frmts10.pdf)
18 * - USB Device Class Definition for Terminal Types (termt10.pdf)
30 * Refer to Table A-2 from audio10.pdf
39 /** Audio Class-Specific AC Interface Descriptor Subtypes.
40 * Refer to Table A-5 from audio10.pdf
54 /** Audio Class-Specific AS Interface Descriptor Subtypes
55 * Refer to Table A-6 from audio10.pdf
64 /** Audio Class-Specific Request Codes
[all …]
|
| /Zephyr-Core-3.5.0/samples/bluetooth/periodic_adv_conn/ |
| D | README.rst | 1 .. _bluetooth-periodic-advertising-conn-sample:
3 Bluetooth: Periodic Advertising Connection Procedure - Initiator
13 is application specific. This sample will connect to any synced device
21 * A controller that supports the Periodic Advertising with Responses (PAwR) - Advertiser feature
32 See :ref:`bluetooth samples section <bluetooth-samples>` for details.
|
| /Zephyr-Core-3.5.0/samples/bluetooth/periodic_adv_rsp/ |
| D | README.rst | 1 .. _bluetooth-periodic-advertising-rsp-sample:
19 application specific. In this sample it is decided by the PAwR advertiser.
27 * A controller that supports the Periodic Advertising with Responses (PAwR) - Advertiser feature
38 See :ref:`bluetooth samples section <bluetooth-samples>` for details.
|
| /Zephyr-Core-3.5.0/include/zephyr/net/ |
| D | ieee802154_radio_openthread.h | 4 * SPDX-License-Identifier: Apache-2.0
18 * OpenThread specific capabilities of ieee802154 driver.
32 * 1 + max_extra_cca_attempts CCAs performed back-to-back.
34 * This mode is a non-standard experimental OpenThread feature. It allows transmission
53 * T_maxtxdelay = max_extra_cca_attempts * (aCcaTime + T_recca) - T_recca + T_ccatx
56 * See IEEE 802.15.4-2020, section 11.3, table 11-1 for the definition of aCcaTime.
60 * section 11.3, table 11-1.
63 * section 11.3, table 11-2).
71 * OpenThread specific configuration types of ieee802154 driver.
82 /** OpenThread specific configuration data of ieee802154 driver. */
[all …]
|
| /Zephyr-Core-3.5.0/doc/contribute/ |
| D | contributor_expectations.rst | 1 .. _contributor-expectations:
13 - Reviewed more quickly and reviewed more thoroughly. It's easier for reviewers
17 - Less wasted work if reviewers or maintainers reject the direction of the
20 - Easier to rebase and merge. Smaller PRs are less likely to conflict with other
23 - Easier to revert if the PR breaks functionality.
35 - Smaller PRs should encompass one self-contained logical change.
37 - When adding a new large feature or API, the PR should address only one part of
38 the feature. In this case create an :ref:`RFC proposal <rfcs>` to describe the
39 additional parts of the feature for reviewers.
41 - PRs should include tests or samples under the following conditions:
[all …]
|
| /Zephyr-Core-3.5.0/samples/bluetooth/periodic_sync_rsp/ |
| D | README.rst | 1 .. _bluetooth-periodic-advertising-sync-rsp-sample:
16 application specific. In this sample it is decided by the PAwR advertiser.
28 * A controller that supports the Periodic Advertising with Responses (PAwR) - Scanner feature
40 See :ref:`bluetooth samples section <bluetooth-samples>` for details.
|
| /Zephyr-Core-3.5.0/doc/kernel/ |
| D | code-relocation.rst | 8 This feature will allow relocating .text, .rodata, .data, and .bss sections from
13 This script provides a robust way to re-order the memory contents without
25 ``python3 gen_relocate_app.py -i input_string -o generated_linker -c generated_code``
50 **The procedure to invoke this feature is:**
74 .. code-block:: none
83 .. code-block:: none
92 expressions can be used to relocate a comma-separated list of files
94 .. code-block:: none
105 used when we want to move the content of a specific file (or set of files) to a
112 .. code-block:: none
[all …]
|
| /Zephyr-Core-3.5.0/modules/openthread/ |
| D | Kconfig.thread | 4 # SPDX-License-Identifier: Apache-2.0
48 bool "FTD - Full Thread Device"
50 bool "MTD - Minimal Thread Device"
54 bool "SED - Sleepy End Device"
74 string "The platform-specific string to insert into the OpenThread version string"
124 router, enable the Inform Previous Parent on Reattach feature.
131 to the network—enable the Periodic Parent Search feature.
145 default -65
181 range -40 20 if NRF_802154_RADIO_DRIVER
|
| /Zephyr-Core-3.5.0/arch/riscv/ |
| D | Kconfig | 1 # Copyright (c) 2016 Jean-Paul Etienne <fractalclone@gmail.com>
2 # SPDX-License-Identifier: Apache-2.0
13 bool "Hard-float calling convention"
17 This option enables the hard-float calling convention.
20 bool "RISC-V global pointer relative addressing"
27 Note: To support this feature, RISC-V SoC needs to initialize
37 This is for RISC-V implementations that require every mret to be
38 balanced with an ecall. This is not required by the RISC-V spec
54 Enable low-level SOC-specific hardware stacking / unstacking
56 if this feature is supported.
[all …]
|
| /Zephyr-Core-3.5.0/include/zephyr/bluetooth/mesh/ |
| D | cfg.h | 8 * SPDX-License-Identifier: Apache-2.0
29 /** Bluetooth mesh feature states */
31 /** Feature is supported, but disabled. */
33 /** Feature is supported and enabled. */
35 /** Feature is not supported, and cannot be enabled. */
45 /* Legacy feature defines */
80 * @returns Whether the Secure Network Beacon feature is enabled.
93 * @retval 0 Successfully changed the Mesh Private beacon feature state.
94 * @retval -ENOTSUP The Mesh Private beacon feature is not supported.
95 * @retval -EINVAL Invalid parameter.
[all …]
|
| /Zephyr-Core-3.5.0/subsys/bluetooth/host/ |
| D | Kconfig | 3 # Copyright (c) 2016-2020 Nordic Semiconductor ASA
4 # Copyright (c) 2015-2016 Intel Corporation
5 # SPDX-License-Identifier: Apache-2.0
8 bool "Dedicated workqueue for long-running tasks."
11 Adds an API for a workqueue dedicated to long-running tasks.
23 int "Long workqueue priority. Should be pre-emptible."
59 # the worst-case stack size if an out-of-tree controller is used.
71 # Hidden option for Co-Operative Tx thread priority
123 bool "Process low priority HCI packets in the bluetooth-specific work queue"
126 in the bluetooth-specific work queue. The HCI driver shall not call bt_recv_prio().
[all …]
|
| /Zephyr-Core-3.5.0/subsys/usb/device/class/audio/ |
| D | audio.c | 4 * SPDX-License-Identifier: Apache-2.0
50 /* Not applicable for not support volume feature device */
62 * This macro fills USB descriptor for specific type of device
65 * @note Feature unit has variable length and only 1st field of
101 * This macro fills USB descriptor for specific type of device.
105 * @note Feature units have variable length and only 1st field of
184 * feature unit descriptor.
188 return (fu->bLength - FU_FIXED_ELEMS_SIZE)/sizeof(uint16_t); in get_num_of_channels()
193 * the feature unit descriptor.
197 return sys_get_le16((uint8_t *)&fu->bmaControls[0]); in get_controls()
[all …]
|
12345678
