:orphan:

.. title:: CONFIG_MODEM_CMD_HANDLER

.. kconfig:: CONFIG_MODEM_CMD_HANDLER

CONFIG_MODEM_CMD_HANDLER
########################

*Generic modem command handler*

Type: ``bool``

Help
====

.. code-block:: none

    This generic command handler uses a modem interface to process
    incoming data and hand it back to the modem driver via callbacks
    defined for:
    - modem responses
    - unsolicited messages
    - specified handlers for current operation
    To configure this layer for use, create a modem_cmd_handler_data
    object and pass it's reference to modem_cmd_handler_init() along with
    the modem_cmd_handler reference from your modem_context object.

Direct dependencies
===================

\ :kconfig:`MODEM_CONTEXT <CONFIG_MODEM_CONTEXT>` && \ :kconfig:`MODEM <CONFIG_MODEM>`

*(Includes any dependencies from ifs and menus.)*

Defaults
========

No defaults. Implicitly defaults to ``n``.

Symbols selected by this symbol
===============================

- \ :kconfig:`NET_BUF <CONFIG_NET_BUF>`

Symbols that select this symbol
===============================

- \ :kconfig:`WIFI_ESP_AT <CONFIG_WIFI_ESP_AT>`
- \ :kconfig:`MODEM_UBLOX_SARA <CONFIG_MODEM_UBLOX_SARA>`
- \ :kconfig:`MODEM_QUECTEL_BG9X <CONFIG_MODEM_QUECTEL_BG9X>`
- \ :kconfig:`MODEM_GSM_PPP <CONFIG_MODEM_GSM_PPP>`

Kconfig definition
==================



At ``<Zephyr Driver>/modem/Kconfig:75``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:42`` → ``<Zephyr Driver>/Kconfig:84``

Menu path: (Top) → Device Drivers → Modem Drivers → Modem context helper driver [EXPERIMENTAL]

.. code-block:: kconfig

    config MODEM_CMD_HANDLER
    	bool "Generic modem command handler"
    	select NET_BUF
    	depends on MODEM_CONTEXT && MODEM
    	help
    	  This generic command handler uses a modem interface to process
    	  incoming data and hand it back to the modem driver via callbacks
    	  defined for:
    	  - modem responses
    	  - unsolicited messages
    	  - specified handlers for current operation
    	  To configure this layer for use, create a modem_cmd_handler_data
    	  object and pass it's reference to modem_cmd_handler_init() along with
    	  the modem_cmd_handler reference from your modem_context object.

*(The 'depends on' condition includes propagated dependencies from ifs and menus.)*