:orphan: .. title:: MODEM_RECEIVER .. option:: CONFIG_MODEM_RECEIVER *Enable modem receiver helper driver* Type: ``bool`` Help ==== This driver allows modem drivers to communicate over UART with custom defined protocols. Driver doesn't inspect received data and all aspects of received protocol data are handled by application via work method provided. This driver differs from the pipe UART driver in that callbacks are executed in a different work queue and data is passed around in k_pipe structures. Direct dependencies =================== \ :option:`SERIAL_SUPPORT_INTERRUPT ` && \ :option:`MODEM ` *(Includes any dependencies from ifs and menus.)* Defaults ======== No defaults. Implicitly defaults to ``n``. Symbols selected by this symbol =============================== - \ :option:`UART_INTERRUPT_DRIVEN ` - \ :option:`RING_BUFFER ` Symbols that select this symbol =============================== - \ :option:`MODEM_WNCM14A2A ` - \ :option:`MODEM_HL7800 ` Kconfig definition ================== .. highlight:: kconfig At ``drivers/modem/Kconfig:17`` Included via ``Kconfig:8`` → ``Kconfig.zephyr:32`` → ``drivers/Kconfig:82`` Menu path: (Top) → Device Drivers → Modem Drivers .. parsed-literal:: config MODEM_RECEIVER bool "Enable modem receiver helper driver" select \ :option:`UART_INTERRUPT_DRIVEN ` select \ :option:`RING_BUFFER ` depends on \ :option:`SERIAL_SUPPORT_INTERRUPT ` && \ :option:`MODEM ` help This driver allows modem drivers to communicate over UART with custom defined protocols. Driver doesn't inspect received data and all aspects of received protocol data are handled by application via work method provided. This driver differs from the pipe UART driver in that callbacks are executed in a different work queue and data is passed around in k_pipe structures. *(The 'depends on' condition includes propagated dependencies from ifs and menus.)*