Home
last modified time | relevance | path

Searched full:included (Results 1 – 25 of 530) sorted by relevance

12345678910>>...22

/Zephyr-Core-3.5.0/include/zephyr/bluetooth/audio/
Dmicp.h59 * @brief Microphone Control Profile included services
61 * Used for to represent the Microphone Control Profile included service
86 * @brief Get Microphone Device included services
89 * Microphone Device included Audio Input Control Service instances.
93 * @param included Pointer to store the result in.
97 int bt_micp_mic_dev_included_get(struct bt_micp_included *included);
191 * @brief Get Microphone Control Profile included services
194 * Microphone Control Profile included services instances, such as
200 * @param[out] included Pointer to store the result in.
205 struct bt_micp_included *included);
Dvcp.h72 * @brief Volume Control Service included services
74 * Used for to represent the Volume Control Service included service instances,
91 * @brief Get Volume Control Service included services.
94 * Volume Control Service included service instances, such as pointers to the
98 * @param[out] included Pointer to store the result in.
102 int bt_vcp_vol_rend_included_get(struct bt_vcp_included *included);
368 * @brief Discover Volume Control Service and included services.
401 * @brief Get Volume Control Service included services.
404 * Volume Control Service included service instances, such as pointers to the
409 * @param[out] included Pointer to store the result in.
[all …]
/Zephyr-Core-3.5.0/include/zephyr/drivers/ieee802154/
Dcc1200.h15 * address 0x04 to 0x2D included.
17 * extended address 0x00 to 0x39 included
/Zephyr-Core-3.5.0/doc/develop/toolchains/
Dcustom_cmake.rst50 based, for example ``llvm`` which then gets the :file:`toolchain/llvm.h` included.
51 This included file may though not be right for the custom toolchain. In order
52 to solve this, and thus to get the :file:`include/other.h` included instead,
63 To get the toolchain header included in zephyr's build, the
/Zephyr-Core-3.5.0/include/zephyr/net/
Dcoap_link_format.h27 * included in the responses of the .well-known/core resource.
38 * In case you want to add attributes to the resources included in the
/Zephyr-Core-3.5.0/scripts/build/
Dgen_image_info.py10 This script creates a image information header which can be included by a
15 Information included in the image information header:
68 Create header file with extracted image information which can be included
/Zephyr-Core-3.5.0/modules/hal_rpi_pico/pico/
Dconfig_autogen.h11 * Since this file ends up included in all pico-sdk code, it's
22 * BUILD_ASSERT is included through toolchain.h.
/Zephyr-Core-3.5.0/share/sysbuild/images/
DCMakeLists.txt13 # This allows for MCUboot to be included.
35 # This allows for board specific images to be included.
/Zephyr-Core-3.5.0/include/zephyr/arch/
Dstructs.h9 * specific structure definitions to be included in generic kernel
18 * kernel.h is included.
/Zephyr-Core-3.5.0/doc/services/device_mgmt/
Dota.rst47 There is a :zephyr:code-sample:`hawkbit-api` sample included in the
58 There is an :zephyr:code-sample:`updatehub-fota` sample included in the Zephyr
69 There is an :zephyr:code-sample:`smp-svr` sample included in the Zephyr :ref:`mgmt-samples`
/Zephyr-Core-3.5.0/arch/x86/include/ia32/
Dkernel_arch_data.h18 * This file is also included by assembly language files which must #define
24 /* this file is only meant to be included by kernel_structs.h */
/Zephyr-Core-3.5.0/dts/bindings/reset/
Dreset-device.yaml4 description: This file needs to be included by devices that need a reset controller.
/Zephyr-Core-3.5.0/
D.gitattributes10 # Tell linguist that generated test pattern files should not be included in the
/Zephyr-Core-3.5.0/arch/common/
Drom_start_address.ld8 * To provide correct value, this file must be the first file included in
/Zephyr-Core-3.5.0/samples/application_development/sysbuild/with_mcuboot/
DCMakeLists.txt9 # automatically included and that sample specific MCUboot configurations are
/Zephyr-Core-3.5.0/subsys/bluetooth/controller/coex/
DKconfig16 When enabled Coexistence device implementation is included in
/Zephyr-Core-3.5.0/doc/services/crypto/
Dindex.rst10 The following crypto libraries have been included:
/Zephyr-Core-3.5.0/samples/tfm_integration/tfm_regression_test/
Dprj.conf14 # Regression tests are included if a related secure partition is enabled.
/Zephyr-Core-3.5.0/soc/xtensa/espressif_esp32/common/include/gdbstub/
Dsoc.h13 #error "Must be included after arch/xtensa/gdbstub.h"
/Zephyr-Core-3.5.0/soc/xtensa/espressif_esp32/esp32_net/include/gdbstub/
Dsoc.h13 #error "Must be included after arch/xtensa/gdbstub.h"
/Zephyr-Core-3.5.0/include/zephyr/arch/riscv/riscv-privileged/
Dasm_inline_gcc.h11 * The file must not be included directly
/Zephyr-Core-3.5.0/submanifests/
DREADME.txt2 in this directory will be included in the main west.yml file sorted by
/Zephyr-Core-3.5.0/scripts/dts/python-devicetree/tests/test-bindings/
Dparent.yaml16 # child.yaml included at child-binding level
/Zephyr-Core-3.5.0/samples/bluetooth/hci_uart_async/
Dsample.yaml4 This sample is a batteries-included example of a Bluetooth HCI UART
/Zephyr-Core-3.5.0/subsys/net/ip/
Dnet_shell.h4 * This is not to be included by the application.

12345678910>>...22