:orphan:

.. title:: MODEM_SOCKET

.. option:: CONFIG_MODEM_SOCKET

*Generic modem socket support layer*

Type: ``bool``

Help
====

This layer provides much of the groundwork for keeping track of
modem "sockets" throughout their lifecycle (from the initial offload
API calls through the command handler call back layers).
To configure this layer for use, create a modem_socket_config
object with your socket data and pass it's reference to
modem_socket_init().

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

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

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

Defaults
========

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

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

- \ :option:`MODEM_UBLOX_SARA <CONFIG_MODEM_UBLOX_SARA>`
- \ :option:`MODEM_QUECTEL_BG9X <CONFIG_MODEM_QUECTEL_BG9X>`

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

.. highlight:: kconfig

At ``drivers/modem/Kconfig:99``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:32`` → ``drivers/Kconfig:82``

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

.. parsed-literal::

    config MODEM_SOCKET
    	bool "Generic modem socket support layer"
    	depends on \ :option:`MODEM_CONTEXT <CONFIG_MODEM_CONTEXT>` && \ :option:`MODEM <CONFIG_MODEM>`
    	help
    	  This layer provides much of the groundwork for keeping track of
    	  modem "sockets" throughout their lifecycle (from the initial offload
    	  API calls through the command handler call back layers).
    	  To configure this layer for use, create a modem_socket_config
    	  object with your socket data and pass it's reference to
    	  modem_socket_init().

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