| /Zephyr-Core-3.5.0/tests/bsim/bluetooth/audio/src/ |
| D | tbs_client_test.c | 31 CREATE_FLAG(technology);
156 technology); in tbs_client_technology_cb()
158 SET_FLAG(technology); in tbs_client_technology_cb()
311 .technology = tbs_client_technology_cb,
410 UNSET_FLAG(technology); in test_technology()
420 WAIT_FOR_FLAG(technology); in test_technology()
|
| /Zephyr-Core-3.5.0/samples/net/sockets/dumb_http_server/src/ |
| D | response_big.html.bin | 27 …oject where silicon vendors, OEMs, ODMs, ISVs, and OSVs can contribute technology to reduce the co…
35 …technology known as Virtuoso. The RTOS has been used in several commercial applications including …
|
| /Zephyr-Core-3.5.0/samples/net/sockets/dumb_http_server_mt/src/ |
| D | response_big.html.bin | 27 …oject where silicon vendors, OEMs, ODMs, ISVs, and OSVs can contribute technology to reduce the co…
35 …technology known as Virtuoso. The RTOS has been used in several commercial applications including …
|
| D | response_100k.html.bin | 27 …oject where silicon vendors, OEMs, ODMs, ISVs, and OSVs can contribute technology to reduce the co…
35 …technology known as Virtuoso. The RTOS has been used in several commercial applications including …
|
| /Zephyr-Core-3.5.0/doc/connectivity/networking/conn_mgr/ |
| D | implementation.rst | 11 Connectivity implementations are technology-specific modules that allow specific Zephyr ifaces to s…
75 /* Cause your underlying technology to associate */
78 /* Cause your underlying technology to disassociate */
81 /* Perform any required initialization for your underlying technology */
193 …disable or enable these features, regardless of the inherent behavior of the underlying technology.
194 In other words, no matter how the underlying technology behaves, your implementation must make it a…
244 * If the technology also handles IP assignment, ensure those IP addresses are :ref:`assigned to the…
274 …should not prevent applications from interacting directly with associated technology-specific APIs.
276 In other words, it should be possible for an application to directly use your underlying technology…
284 …For instance, if an application directly instructs an underlying technology to dissassociate, it w…
[all …]
|
| /Zephyr-Core-3.5.0/subsys/bluetooth/audio/shell/ |
| D | tbs.c | 455 unsigned long technology; in cmd_tbs_set_bearer_technology() local
482 technology = shell_strtoul(argv[argc - 1], 0, &result); in cmd_tbs_set_bearer_technology()
489 if (technology > UINT8_MAX) { in cmd_tbs_set_bearer_technology()
490 shell_error(sh, "Invalid technology: %lu", technology); in cmd_tbs_set_bearer_technology()
496 (uint8_t)technology); in cmd_tbs_set_bearer_technology()
|
| /Zephyr-Core-3.5.0/doc/connectivity/networking/api/ |
| D | thread.rst | 12 Thread is a low-power mesh networking technology, designed specifically for home
14 technology over IEEE 802.15.4 protocol. IP connectivity lets you easily connect
|
| D | ethernet.rst | 20 Ethernet is a networking technology commonly used in local area networks (LAN).
|
| D | net_mgmt.rst | 137 technology as well. For instance, all IP layer management request code
139 of an L2 technology, let's say Ethernet, these would be found in
168 code, event code can be also found on specific L2 technology mgmt headers,
170 802.15.4 L2 is the technology one wants to listen to events.
|
| D | ieee802154.rst | 28 recent developments in UWB ranging technology, see IEEE 802.15.4z which is not
|
| /Zephyr-Core-3.5.0/subsys/bluetooth/audio/ |
| D | tbs_client.c | 365 uint8_t technology; in technology_notify_handler() local
369 if (length == sizeof(technology)) { in technology_notify_handler()
370 (void)memcpy(&technology, data, length); in technology_notify_handler()
371 LOG_DBG("%s (0x%02x)", bt_tbs_technology_str(technology), technology); in technology_notify_handler()
373 if (tbs_client_cbs != NULL && tbs_client_cbs->technology != NULL) { in technology_notify_handler()
374 tbs_client_cbs->technology(conn, 0, tbs_index(conn, tbs_inst), technology); in technology_notify_handler()
908 uint8_t technology = 0; in read_technology_cb() local
916 if (length == sizeof(technology)) { in read_technology_cb()
917 (void)memcpy(&technology, data, length); in read_technology_cb()
918 LOG_DBG("%s (0x%02x)", bt_tbs_technology_str(technology), technology); in read_technology_cb()
[all …]
|
| D | tbs.c | 39 uint8_t technology; member
70 uint8_t technology; member
553 uint8_t technology; in read_technology() local
556 technology = gtbs_inst.technology; in read_technology()
557 LOG_DBG("GTBS: Technology 0x%02X", technology); in read_technology()
561 technology = inst->technology; in read_technology()
562 LOG_DBG("Index %u: Technology 0x%02X", inst->index, technology); in read_technology()
566 &technology, sizeof(technology)); in read_technology()
1789 svc_insts[i].technology = CONFIG_BT_TBS_TECHNOLOGY; in bt_tbs_init()
2197 if (gtbs_inst.technology == new_technology) { in bt_tbs_set_bearer_technology()
[all …]
|
| /Zephyr-Core-3.5.0/drivers/interrupt_controller/ |
| D | Kconfig.intel_vtd | 14 technology. It's being used, currently, only for MSI/MSI-X
|
| /Zephyr-Core-3.5.0/arch/arm/core/ |
| D | Kconfig | 67 Thumb-2 technology is the instruction set underlying the ARM Cortex
72 Thumb-2 technology builds on the success of Thumb, the innovative
77 The technology is backwards compatible with existing ARM and Thumb
82 For performance optimized code Thumb-2 technology uses 31 percent
86 technology is featured in the processor, and in all ARMv7
101 the introduction of Thumb-2 technology.
|
| /Zephyr-Core-3.5.0/samples/net/zperf/ |
| D | README.rst | 45 Depending on the network technology chosen, extra steps may be required
|
| /Zephyr-Core-3.5.0/boards/x86/intel_adl/doc/ |
| D | index.rst | 9 technology process.
|
| /Zephyr-Core-3.5.0/cmake/ |
| D | target_toolchain_flags.cmake | 39 # Configure the toolchain flags based on what toolchain technology is used
|
| /Zephyr-Core-3.5.0/doc/connectivity/bluetooth/api/shell/ |
| D | ccp.rst | 59 read_technology :Read the bearer technology [<{instance_index,
195 set_bearer_technology :Set the bearer technology [<{instance_index,
196 gtbs}>] <technology>
|
| /Zephyr-Core-3.5.0/boards/riscv/longan_nano/doc/ |
| D | index.rst | 14 an GigaDevice GD32VF103 SoC that based on N200 RISC-V IP core by Nuclei system technology.
|
| /Zephyr-Core-3.5.0/boards/shields/x_nucleo_53l0a1/doc/ |
| D | index.rst | 10 detection sensor, based on ST’s FlightSense™, Time-of-Flight technology. It is
|
| /Zephyr-Core-3.5.0/cmake/modules/ |
| D | FindHostTools.cmake | 105 # Configure the toolchain based on what toolchain technology is used
|
| /Zephyr-Core-3.5.0/include/zephyr/bluetooth/audio/ |
| D | tbs.h | 482 bt_tbs_client_read_value_cb technology; member
|
| /Zephyr-Core-3.5.0/subsys/net/l2/ieee802154/ |
| D | Kconfig | 8 Add support for low rate WPAN IEEE 802.15.4 technology.
|
| /Zephyr-Core-3.5.0/boards/arm/hexiwear_kw40z/doc/ |
| D | index.rst | 179 https://www.segger.com/products/debug-probes/j-link/technology/about-real-time-transfer/
|
| /Zephyr-Core-3.5.0/boards/arm/msp_exp432p401r_launchxl/doc/ |
| D | index.rst | 23 * XDS110-ET, an open-source onboard debug probe featuring EnergyTrace+ technology and application
|
