| /hal_espressif-3.6.0/components/hal/ |
| D | twai_hal_iram.c | 34 uint32_t events = 0; local
45 TWAI_HAL_SET_BITS(events, TWAI_HAL_EVENT_BUS_OFF);
51 TWAI_HAL_SET_BITS(events, TWAI_HAL_EVENT_BUS_RECOV_PROGRESS);
55 TWAI_HAL_SET_BITS(events, TWAI_HAL_EVENT_ABOVE_EWL);
59 TWAI_HAL_SET_BITS(events, TWAI_HAL_EVENT_BUS_RECOV_CPLT);
62 TWAI_HAL_SET_BITS(events, TWAI_HAL_EVENT_BELOW_EWL);
69 TWAI_HAL_SET_BITS(events, TWAI_HAL_EVENT_RX_BUFF_FRAME);
77 TWAI_HAL_SET_BITS(events, TWAI_HAL_EVENT_TX_BUFF_FREE);
83 TWAI_HAL_SET_BITS(events, TWAI_HAL_EVENT_ERROR_PASSIVE);
86 TWAI_HAL_SET_BITS(events, TWAI_HAL_EVENT_ERROR_ACTIVE);
[all …]
|
| /hal_espressif-3.6.0/components/bt/host/bluedroid/stack/rfcomm/ |
| D | port_rfc.c | 151 UINT32 events = 0; in port_start_close() local
159 events |= port_get_signal_changes (p_port, old_signals, p_port->peer_ctrl.modem_signal); in port_start_close()
162 events |= PORT_EV_CONNECT_ERR; in port_start_close()
166 events |= PORT_EV_ERR; in port_start_close()
169 if ((p_port->p_callback != NULL) && events) { in port_start_close()
170 p_port->p_callback (events, p_port->inx); in port_start_close()
830 UINT32 events = 0; in PORT_DataInd() local
881 events |= PORT_EV_RXFLAG; in PORT_DataInd()
899 if (events & PORT_EV_RXFLAG) { in PORT_DataInd()
906 events |= PORT_EV_RXCHAR; in PORT_DataInd()
[all …]
|
| D | port_api.c | 777 UINT32 events; in PORT_FlowControl() local
816 events = PORT_EV_RXCHAR; in PORT_FlowControl()
819 events |= PORT_EV_RXFLAG; in PORT_FlowControl()
822 events &= p_port->ev_mask; in PORT_FlowControl()
823 if (p_port->p_callback && events) { in PORT_FlowControl()
824 p_port->p_callback (events, p_port->inx); in PORT_FlowControl()
848 UINT32 events;
887 events = PORT_EV_RXCHAR;
890 events |= PORT_EV_RXFLAG;
893 events &= p_port->ev_mask;
[all …]
|
| D | port_utils.c | 448 UINT32 events = 0; in port_get_signal_changes() local
451 events |= PORT_EV_DSR; in port_get_signal_changes()
454 events |= PORT_EV_DSRS; in port_get_signal_changes()
459 events |= PORT_EV_CTS; in port_get_signal_changes()
462 events |= PORT_EV_CTSS; in port_get_signal_changes()
467 events |= PORT_EV_RING; in port_get_signal_changes()
471 events |= PORT_EV_RLSD; in port_get_signal_changes()
474 events |= PORT_EV_RLSDS; in port_get_signal_changes()
478 return (p_port->ev_mask & events); in port_get_signal_changes()
|
| /hal_espressif-3.6.0/examples/bluetooth/esp_ble_mesh/ble_mesh_console/main/ |
| D | transaction.c | 46 esp_err_t transaction_set_events(transaction_t *trans, EventBits_t events) in transaction_set_events() argument
58 trans->current_bits |= events; in transaction_set_events()
59 xEventGroupSetBits(trans->event_group, events); in transaction_set_events()
61 …set events: %x, %x, %x, %x; ret: %x", (uint32_t) trans, trans->type, trans->sub_type, events, ret); in transaction_set_events()
69 esp_err_t transaction_test_events(transaction_t *trans, EventBits_t events) in transaction_test_events() argument
78 if ((trans->current_bits & events) == events) { in transaction_test_events()
82 ESP_LOGV(TAG, "transactions test events: %x, %x; ret: %x", (uint32_t) trans, events, ret); in transaction_test_events()
90 esp_err_t transaction_clear_events(transaction_t *trans, EventBits_t events) in transaction_clear_events() argument
98 trans->current_bits &= ~events; in transaction_clear_events()
99 xEventGroupClearBits(trans->event_group, events); in transaction_clear_events()
[all …]
|
| D | transaction.h | 67 esp_err_t transaction_set_events(transaction_t *trans, EventBits_t events);
68 esp_err_t transaction_test_events(transaction_t *trans, EventBits_t events);
69 esp_err_t transaction_clear_events(transaction_t *trans, EventBits_t events);
|
| /hal_espressif-3.6.0/components/esp_event/ |
| D | Kconfig | 7 … Enables collections of statistics in the event loop library such as the number of events posted
8 …to/recieved by an event loop, number of callbacks involved, number of events dropped to to a full …
12 bool "Support posting events from ISRs"
15 Enable posting events from interrupt handlers.
18 bool "Support posting events from ISRs placed in IRAM"
22 …Enable posting events from interrupt handlers placed in IRAM. Enabling this option places API func…
|
| D | event_send_compat.inc | 26 * function, which is used to forward legacy events (system_event_t) sent using
29 * For each of the events in system_event_id_t, we extract the event data from
68 /* Wi-Fi common events */
75 /* STA events */
80 /* WPS events */
87 /* AP events */
94 /* Ethernet events */
106 /* IP events */
|
| /hal_espressif-3.6.0/docs/en/api-reference/system/ |
| D | esp_event.rst | 7 The event loop library allows components to declare events to which other components can register h…
8 execute when those events occur. This allows loosely coupled components to attach desired behavior …
9 …nvolvement. For instance, a high level connection handling library may subscribe to events produced
10 by the wifi subsystem directly and act on those events. This also simplifies event processing by se…
16 There are two objects of concern for users of this library: events and event loops.
19 …g a two part identifier which are discussed more :ref:`here <esp-event-declaring-defining-events>`.
20 Event loops are the vehicle by which events get posted by event sources and handled by event handle…
65 … // 4. Post events to the loop. This queues the event on the event loop. At some point in time
82 .. _esp-event-declaring-defining-events:
84 Declaring and defining events
[all …]
|
| /hal_espressif-3.6.0/docs/en/api-guides/ |
| D | event-handling.rst | 4 Several ESP-IDF components use *events* to inform application about state changes, such as connecti…
9 Before the introduction of :doc:`esp_event library<../api-reference/system/esp_event>`, events from…
14 …events to the event loop, and use the event loop for other kinds of events (e.g. Mesh). Legacy eve…
16 …` for general information on using this library. Wi-Fi, Ethernet, and IP events are sent to the :r…
33 …n event handler will typically use ``switch(event->event_id)`` to handle different kinds of events.
133 … similar to the :ref:`legacy-event-loop` to deliver events to the application. See :ref:`mesh-even…
138 Various modules of the Bluetooth stack deliver events to applications via dedicated callback functi…
|
| /hal_espressif-3.6.0/components/driver/ |
| D | twai.c | 204 uint32_t events; in twai_intr_handler_main() local
210 events = twai_hal_get_events(&twai_context); //Get the events that triggered the interrupt in twai_intr_handler_main()
213 if (events & TWAI_HAL_EVENT_NEED_PERIPH_RESET) { in twai_intr_handler_main()
221 if (events & TWAI_HAL_EVENT_RX_BUFF_FRAME) { in twai_intr_handler_main()
225 if (events & TWAI_HAL_EVENT_TX_BUFF_FREE) { in twai_intr_handler_main()
230 if (events & TWAI_HAL_EVENT_BUS_OFF) { in twai_intr_handler_main()
234 if (events & TWAI_HAL_EVENT_BUS_RECOV_CPLT) { in twai_intr_handler_main()
238 if (events & TWAI_HAL_EVENT_BUS_ERR) { in twai_intr_handler_main()
242 if (events & TWAI_HAL_EVENT_ARB_LOST) { in twai_intr_handler_main()
246 if (events & TWAI_HAL_EVENT_BUS_RECOV_PROGRESS) { in twai_intr_handler_main()
[all …]
|
| D | sdio_slave.c | 133 SemaphoreHandle_t events[9]; // 0-7 for gp intr member
154 .events = {}, \
201 if (context.events[i] != NULL) { in deinit_context()
202 vSemaphoreDelete(context.events[i]); in deinit_context()
203 context.events[i] = NULL; in deinit_context()
251 context.events[i] = xSemaphoreCreateBinary(); in init_context()
253 if (context.events[i] == NULL) { in init_context()
467 xSemaphoreGiveFromISR(context.events[i], &yield); in sdio_intr_host()
478 return xSemaphoreTake(context.events[pos], wait); in sdio_slave_wait_int()
|
| /hal_espressif-3.6.0/examples/system/sysview_tracing/ |
| D | README.md | 14 There can be a problem which causes the task to lose some events.
68 …events transfer. Task needs some time to process an event before waiting for the next one. In this…
70 …ow is the output of example compiled in single core mode. It shows that task misses several events:
89 …. It implies extending SystemView with user module having its own set of events with any number of…
103 …checking `(X) SystemView Tracing Enable`. Also ensure that all SystemView events are enabled there.
105 4. If you are going to use custom events enable them by checking `Example Configuration > Use cust…
145 - `Show APIs only` if you compiled example to use custom events.
147 10. Now you can navigate over user-defined messages and see when timer `TG1_T0_LEVEL` sends events…
148 …If you compiled example to use custom events you will also be able to see the values sent by timer…
|
| /hal_espressif-3.6.0/examples/system/esp_event/default_event_loop/ |
| D | README.md | 7 …ence/system/esp_event.html#) the system uses to post and handle events (e.g. Wi-Fi events). This e…
23 …e default event loop using `esp_event_handler_register` for (1) specific events, (2) **any** event…
109 All of the events mentioned above have their own specific handler, however there are the following …
125 At this stage the default event loop is created, and the handlers for the different events are regi…
135 The two event sources are started. The respective events are posted to the default event loop.
149 The handlers are executed for the events that were posted in **(2)**. Note how `timer_started_handl…
152 …r event. It can be seen executing for the timer expiry and timer stopped events in the subsequent …
156 For both the timer and task events, notice that the handlers are executed in the same order they ar…
195 The task containing the loop that posts iteration events also gets deleted. The example ends at thi…
|
| /hal_espressif-3.6.0/components/vfs/test/ |
| D | test_vfs_select.c | 220 .events = POLLIN,
249 poll_fds[1].events = POLLIN;
326 .events = POLLIN,
330 .events = POLLIN,
334 .events = POLLIN,
407 .events = POLLIN,
411 .events = POLLIN,
|
| /hal_espressif-3.6.0/components/usb/ |
| D | maintainers.md | 55 …- Port can detect various events such as connection, disconnection, enabled (i.e., connected devic…
92 - The various host port events are represented in the `hcd_port_event_t` enumeration
93 - When the following port events occur, the port will be put into the HCD_PORT_STATE_RECOVERY state…
115 …events entirely through callbacks and polling/handling functions. The client can choose what type …
116 …o be treated as completely separate entities (with their own handles and events). This allows clie…
124 …events to the client of the HCD, the HCD does not attempt to allocate any queues to store events t…
131 The client of the HCD can also forego callbacks entirely and simply poll for port and pipe events u…
140 - Likewise, it is the client's responsibility to ensure that events and pipes are cleared before ca…
|
| /hal_espressif-3.6.0/examples/bluetooth/bluedroid/classic_bt/a2dp_sink/tutorial/ |
| D | Example_A2DP_Sink.md | 81 …events, event handlers, callbacks and state machines. Most APIs are implemented by posting specifi…
147 …task_start_up()` creates a work queue and a FreeRTOS task to process the events(messages) posted i…
|
| /hal_espressif-3.6.0/examples/peripherals/usb/host/msc/components/msc/ |
| D | README.md | 10 - USB Host Library events have to be handled by invoking `usb_host_lib_handle_events` periodically.
11 In general, an application should spawn a dedicated task handle USB Host Library events.
15 and optional parameters for creating background task handling MSC related events.
|
| /hal_espressif-3.6.0/docs/en/api-reference/network/ |
| D | esp-wifi-mesh.rst | 42 .. _mesh-events:
49 .. figure:: ../../../_static/mesh-events-delivery.png
56 …sible ESP-WIFI-MESH events and can indicate events such as the connection/disconnection of parent/…
58 Typical use cases of mesh events include using events such as :cpp:enumerator:`MESH_EVENT_PARENT_CO…
61 …om the application (including calls from callbacks and handlers of Wi-Fi events) may interfere wit…
118 /* register IP events handler */
140 /* register mesh events handler */
209 After starting ESP-WIFI-MESH, the application should check for ESP-WIFI-MESH events to determine wh…
|
| /hal_espressif-3.6.0/docs/en/api-reference/peripherals/ |
| D | usb_host.rst | 77 …ients, the Host Library can delegate the handling of all client events (i.e., the events specific …
82 …ary delegates the handling of client events to the clients themselves, there are still Library eve…
86 - Forwarding events to clients
88 …ry also requires a task (usually the Host Library Daemon Task) to handle all of the library events.
101 …the claimed interface. The client's task is responsible for handling its own processing and events.
117 The Host Library API provides :cpp:func:`usb_host_lib_handle_events` to handle library events. This…
200 …cpp:func:`usb_host_client_handle_events` to handle a particular client's events. This function sho…
205 …n :cpp:func:`usb_host_client_handle_events` thus allowing the client task to be notified of events.
207 …vers client event messages to the client. Client event messages indicate events such as the additi…
211 …ndle_events` being blocked as well, thus preventing other pending client events from being handled.
|
| D | touch_element.rst | 208 4. To subscribe events by calling :cpp:func:`touch_xxxx_subscribe_event`
244 //Subscribe the specified events by using the event mask
271 …events by calling :cpp:func:`touch_xxxx_subscribe_event`, there several events in Touch Element li…
285 In code, the events handle procedure may look like as follows:
|
| /hal_espressif-3.6.0/components/newlib/ |
| D | poll.c | 58 if (fds[i].events & (POLLIN | POLLRDNORM | POLLRDBAND | POLLPRI)) { in poll()
64 if (fds[i].events & (POLLOUT | POLLWRNORM | POLLWRBAND)) { in poll()
|
| /hal_espressif-3.6.0/components/app_trace/ |
| D | Kconfig | 80 Size of the buffer for events in bytes. It is useful for buffering events from
82 events will be discarded when main HW buffer is full.
142 Set to -1 to wait forever and avoid lost events.
|
| /hal_espressif-3.6.0/docs/en/api-reference/protocols/ |
| D | esp_serial_slave_link.rst | 63 1. Tohost Interrupts: The slave can inform the master about certain events by the interrupt line. (…
65 2. Frhost Interrupts: The master can inform the slave about certain events.
135 1. Call :cpp:func:`essl_get_intr_ena` to know which events will trigger the interrupts to the maste…
137 2. Call :cpp:func:`essl_set_intr_ena` to set the events that will trigger interrupts to the master.
141 4. When interrupt is triggered, call :cpp:func:`essl_get_intr` to know which events are active,
|
| /hal_espressif-3.6.0/components/esp_netif/ |
| D | README.md | 5 .............| init settings events |
46 - register handlers for app related events (such as IP lost/acquired)
|
