Lines Matching full:from

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
66  * from any thread except TCPIP thread.
77  * Thread-safe, to be called from non-TCPIP threads only.\n
154  *    timer IRQ and ethernet IRQ from each other, assuming these may be nested.
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
168  * TCPIP thread. It is a common error to call these from other threads
169  * or from IRQ contexts. ​Ethernet RX needs to deliver incoming packets
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,
176  *    it is safe to call any @ref callbackstyle_api from there.
224  * Feed incoming packets to netif->input(pbuf, netif) function from mainloop,
225  * *not* *from* *interrupt* *context*. You can allocate a @ref pbuf in interrupt
226  * context and put them into a queue which is processed from mainloop.\n
293   DHCP and IPv6 discover benefit well from those events.
315  * environment, raw API functions MUST only be called from the core thread
316  * since raw API functions are not protected from concurrent access (aside
317  * from pbuf- and memory management functions). Application threads using
321  * As such, the list of functions that may be called from
323  * from these API header files are thread-safe:
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
373 routine from src/core/inet.c. You can override this standard
386 \#define LWIP_DONT_PROVIDE_BYTEORDER_FUNCTIONS to prevent lwIP from