Lines Matching full:called

15  * having callback functions being called from within the TCP/IP
52  * C function that is called from within the TCP/IP code. Every callback
55  * the callback functions are called with a program specified argument
57  * The raw API (sometimes called native API) is an event-driven API designed
65  * Sequential-style APIs, blocking functions. More overhead, but can be called
77  * Thread-safe, to be called from non-TCPIP threads only.\n
149  *    callback functions are called in IRQ context, which may cause further
157  *    lwIP is _ONLY_ called from mainloop callstacks here. The ethernet IRQ
159  *    mainloop. Ensure lwIP is _NEVER_ called from an interrupt, e.g.
165  * @ref sequential_api are designed to be called from threads other than
167  * But @ref callbackstyle_api functions must _ONLY_ be called from
172  * Again, ensure lwIP is _NEVER_ called from an interrupt, e.g.
175  * 1) tcpip_callback() can be used get called back from TCPIP thread,
179  *    functions can be called when lwIP core lock is aquired, see
291   Ethernet interface. This function must be called even if you don't know
297   netif is fully configured this function must be called.
315  * environment, raw API functions MUST only be called from the core thread
321  * As such, the list of functions that may be called from
333  * called from multiple threads (not ISR!) with NO_SYS=0
344  * pbuf_free() may also be called from another thread or
346  * be called from an ISR: otherwise, the HEAP is only