Searched refs:Call (Results 1 – 25 of 42) sorted by relevance
12
1 # Bluetooth Audio - Call Control Profile (CCP) configuration options11 bool "Call Control Profile Client Support"16 This option enables support for the Call Control Profile Client which uses the Telephone27 The number of supported telephone bearers on the CCP Call Control Client30 module-str = "Call Control Profile Client"36 bool "Call Control Profile Call Control Server Support"41 This option enables support for the Call Control Profile Call Control Server which uses51 The number of supported telephone bearers on the CCP Call Control Server54 module-str = "Call Control Profile Call Control Server"
1 # Bluetooth Audio - Call control configuration options66 ##################### Call Control Client #####################75 This option enables support for the GTBS-oriented Call Control client.84 This option enables support for the TBS-oriented Call Control client.170 bool "Support reading Incoming Call Target Bearer URI"173 This option enables support for reading Incoming Call Target Bearer197 bool "Support Accept Call"203 bool "Support Terminate Call"209 bool "Support Hold Call"215 bool "Support Retrieve Call"[all …]
71 [Check 1] Call get API for UID 6 which is not set72 [Check 2] Call get_info API for UID 6 which is not set73 [Check 3] Call remove API for UID 6 which is not set74 [Check 4] Call get API for UID 6 which is removed75 [Check 5] Call get_info API for UID 6 which is removed76 [Check 6] Call remove API for UID 6 which is removed78 [Check 7] Call get API for different UID 579 [Check 8] Call get_info API for different UID 580 [Check 9] Call remove API for different UID 583 [Check 1] Call get API for UID 6 which is not set[all …]
1 Bluetooth: Call Control Profile Shell4 Call Control Server6 The Call Control Server is a role that typically resides on devices that can make calls,10 Using the Call Control Server19 ccp_call_control_server - Bluetooth CCP Call Control Server shell commands21 init : Initialize CCP Call Control Server37 Call Control Client39 The Call Control Client is a role that typically resides on resource constrained devices such as42 Using the Call Control Client50 ccp_call_control_client - Bluetooth CCP Call Control Client shell commands
110 …<dbg> bt_tbs_client.current_calls_notify_handler: Call 0x01 is in the dialing state with URI tel:1…113 …<dbg> bt_tbs_client.current_calls_notify_handler: Call 0x01 is in the alerting state with URI tel:…116 …<dbg> bt_tbs_client.current_calls_notify_handler: Call 0x01 is in the active state with URI tel:123124 …<dbg> bt_tbs_client.current_calls_notify_handler: Call 0x01 is in the dialing state with URI tel:1…127 …<dbg> bt_tbs_client.current_calls_notify_handler: Call 0x01 is in the alerting state with URI tel:…130 …<dbg> bt_tbs_client.current_calls_notify_handler: Call 0x01 is in the active state with URI tel:123141 …<dbg> bt_tbs_client.current_calls_notify_handler: Call 0x05 is in the incoming state with URI tel:…144 <dbg> bt_tbs_client.current_calls_notify_handler: Call 0x05 is in the active state with URI tel
24 1. Call :c:func:`timing_init` to initialize the timer.26 2. Call :c:func:`timing_start` to signal the start of gathering of29 3. Call :c:func:`timing_counter_get` to mark the start of code32 4. Call :c:func:`timing_counter_get` to mark the end of code35 5. Call :c:func:`timing_cycles_get` to get the number of timer cycles38 6. Call :c:func:`timing_cycles_to_ns` with total number of cycles44 8. Call :c:func:`timing_stop` to signal the end of gathering of
2 :name: Call Control Profile (CCP) Call Control Server5 CCP Call Control Server sample that registers one or more TBS bearers and advertises the11 Application demonstrating the CCP Call Control Client functionality.12 Starts by scanning for a CCP Call Control Server to connect and set up calls.
2 :name: Call Control Profile (CCP) Call Control Server5 CCP Call Control Server sample that registers one or more TBS bearers and advertises the11 Application demonstrating the CCP Call Control Server functionality.12 Starts by advertising for CCP Call Control Clients to connect and set up calls.
43 - Call :c:func:`fcb_append` to get the location where data can be written. If48 - Call :c:func:`fcb_append_finish` when done. This completes the writing of the53 - Call :c:func:`fcb_walk` with a pointer to your callback function.61 - Call :c:func:`fcb_getnext` with 0 in entry offset to get the pointer to64 - Call :c:func:`fcb_getnext` with pointer to current entry to get the next one.
29 def visit_call(self, node: nodes.Call) -> None: argument
5 Implement the TMAP Call Gateway (CG) and Unicast Media Sender (UMS) roles.
5 Implement the TMAP Call Terminal (CT) and Unicast Media Receiver (UMR) roles.
7 # @Intent: Call a script to get userspace wordsize for comparison with CONFIG_64BIT
56 * Call :c:func:`sys_cache_data_disable()` to globally disable the data cache.168 * Call :c:func:`sys_cache_data_flush_range()` to flush a memory region.170 * Call :c:func:`sys_cache_data_invd_range()` to invalidate a memory region.172 * Call :c:func:`sys_cache_data_flush_and_invd_range()` to flush and invalidate.
56 Call an application specific hook after the driver specific
419 | | Call Control Server | Call Control Client |502 | CCP Call Control Server | | O | |504 | CCP Call Control Client | O | | C.6 |614 …| CCP Call Control Client | O | | …616 …| CCP Call Control Server | | O | …633 * C.5 If CCP Call Control Server is supported656 …| | Call Gateway | Call Terminal | Unicast Media Sender | Unicas…682 …| CCP Call Control Server | M | | | …725 …| CCP | Call Control Server | 1.0 | 3.0 | - Feature complete | - …729 …| | Call Control Client | 1.0 | 3.0 | - Feature complete | - …[all …]
92 * Call the :c:func:`mqtt_sn_add_gw` function to manually define a Gateway address.94 * Call the :c:func:`mqtt_sn_search` function and wait for an :c:enumerator:`MQTT_SN_EVT_GWINFO` cal…107 connect to the gateway. Call the :c:func:`mqtt_sn_connect` function, which will send a
105 3. Procedure Call Standard for the ARM Architecture (ARM IHI 0042E, current
5 Call a function in a loadable extension module,
119 int "Call outgoing timeout value for HFP AG [EXPERIMENTAL]"137 int "Call alerting/ringing timeout value for HFP AG [EXPERIMENTAL]"
76 :ref:`System Call <syscalls>` is needed as part of the implementation, the declaration and the
65 #. Call :c:func:`mspi_dev_config` with device specific hardware settings obtained79 #. Call API for additional setups if supported by hardware
119 3. Procedure Call Standard for the ARM Architecture (ARM IHI 0042E, current
85 Include support for the Secure Monitor Call (SMC) and Hypervisor86 Call (HVC) instructions on Armv7 and above architectures.
44 Call network event handlers when the event is emitted.
