OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/drivers/modem/CMakeLists.txt

43 lines
1.2 KiB
CMake
Raw Normal View History

license: cleanup: add SPDX Apache-2.0 license identifier Update the files which contain no license information with the 'Apache-2.0' SPDX license identifier. Many source files in the tree are missing licensing information, which makes it harder for compliance tools to determine the correct license. By default all files without license information are under the default license of Zephyr, which is Apache version 2. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2019-04-06 21:08:09 +08:00
# SPDX-License-Identifier: Apache-2.0
drivers: modem: build as static library Instead of putting object files inside libzephyr.a, simply build a separate static library as most other driver types are doing this already. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2021-08-05 05:49:12 +08:00
zephyr_library()
drivers/modem: Switch wncm14a2a driver to new net_pkt API It is a bit awkward that ip/proto headers have to be rebuilt (with fake data in it though). Let's see in future if that's really needed, offload device handles already ip/proto headers by themselves so we should not care. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2019-02-19 18:17:51 +08:00
drivers: modem: build as static library Instead of putting object files inside libzephyr.a, simply build a separate static library as most other driver types are doing this already. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2021-08-05 05:49:12 +08:00
zephyr_library_sources_ifdef(CONFIG_MODEM_RECEIVER modem_receiver.c)
zephyr_library_sources_ifdef(CONFIG_MODEM_SHELL modem_shell.c)
modem: remove 'modem_pin' abstraction All drivers using 'modem_pin' abstraction were converted already, so remove its implementation now. Signed-off-by: Marcin Niestroj <m.niestroj@emb.dev>
2022-05-14 01:22:13 +08:00
zephyr_library_sources_ifdef(CONFIG_MODEM_CONTEXT modem_context.c)
drivers: modem: context helper: introduce modem context helper driver Initial support for modems in Zephyr use the following driver model: - Main portions of code live in the modem specific driver. This includes internal socket management, command parsing, etc. - They leverage a UART-based modem receiver helper to gather data. - Interface with Zephyr networking via net_context offload APIs. This implementation was good enough to kick start interest in supporting modem usage in Zephyr, but lacks future scalability: - The net_context offload APIs don't allow for operations such as offloaded DNS, SSL/TLS and other HW specific features. - Since most of the code lives within the modem drivers, it's very hard for the Zephyr community to improve the driver layer over time. Bugs found in 1 driver probably affect others due to copy/paste method of development. - Lack of abstraction for different modem interfaces and command handlers makes it impossible to write a "dummy" layer which could be used for testing. - Lack of centralized processing makes implementing low power modes and other advanced topics more difficult. Introducing the modem context helper driver and sub-layers: - modem context helper acts as an umbrella for several configurable layers and exposes this data to externals such as the modem shell. Included in the helper is GPIO pin config functions which are currently duplicated in most drivers. - modem interface layer: this layer sits on the HW APIs for the peripheral which communicates with the modem. Users of the modem interface can handle data via read/write functions. Individual modem drivers can select from (potentially) several modem interfaces. - modem command parser layer: this layer communicates with the modem interface and processes the data for use by modem drivers. Fixes: https://github.com/zephyrproject-rtos/zephyr/issues/17922 Signed-off-by: Michael Scott <mike@foundries.io>
2019-08-07 23:01:00 +08:00
modem: choice symbol for UART backend Add a choice symbol that is used to select which UART backend to use. This allows backends that don't use the interrupt API to be implemented. Signed-off-by: Jordan Yates <jordan.yates@data61.csiro.au>
2022-04-05 14:13:52 +08:00
zephyr_library_sources_ifdef(CONFIG_MODEM_IFACE_UART_INTERRUPT modem_iface_uart_interrupt.c)
modem: modem_iface_uart_async: added Adds a communications backend based on the asynchronous UART API, instead of the interrupt-driven UART API. The primary advantage of this backend is an improved robustness to dropping bytes under high interrupt or critical section loads. Under all loads system efficiency is improved by: * Reducing the time spent writing out individual bytes. * Reducing the number of UART interrupts fired. * Waking up the RX thread much less often. When utilising this backend over `nordic,nrf-uarte` on a nRF52840, the baudrate of an esp-at modem could be pushed to at least 921600 without dropping bytes, compared to a maximum of 230400 with the interrupt API. Signed-off-by: Jordan Yates <jordan.yates@data61.csiro.au>
2022-04-05 18:12:56 +08:00
zephyr_library_sources_ifdef(CONFIG_MODEM_IFACE_UART_ASYNC modem_iface_uart_async.c)
drivers: modem: build as static library Instead of putting object files inside libzephyr.a, simply build a separate static library as most other driver types are doing this already. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2021-08-05 05:49:12 +08:00
zephyr_library_sources_ifdef(CONFIG_MODEM_CMD_HANDLER modem_cmd_handler.c)
zephyr_library_sources_ifdef(CONFIG_MODEM_SOCKET modem_socket.c)
drivers: modem: interface: introduce UART interface driver layer The UART-based modem interface layer implements the modem context interface for Zephyr's UART APIs. This driver closely resembles the existing modem receiver, but conforming to the modem interface agreements. Example modem driver setup code looks like this: /* create modem context object */ static struct modem_context mctx; /* create uart interface data object and buffers */ static struct modem_iface_uart_data iface_data; static u8_t iface_isr_buf[MDM_RECV_BUF_SIZE]; static u8_t iface_rb_buf[MDM_MAX_DATA_LENGTH]; iface_data.isr_buf = &iface_isr_buf[0]; iface_data.isr_buf_len = sizeof(iface_isr_buf); iface_data.rx_rb_buf = &iface_rb_buf[0]; iface_data.rx_rb_buf_len = sizeof(iface_rb_buf); ret = modem_iface_uart_init(&mctx.iface, &iface_data, UART_DEV_NAME); Signed-off-by: Michael Scott <mike@foundries.io>
2019-08-07 23:02:00 +08:00
drivers: modem: Fix include paths Set the include paths properly and unconditionally to needed networking directories. Signed-off-by: Jukka Rissanen <jukka.rissanen@nordicsemi.no>
2023-11-20 19:46:00 +08:00
zephyr_library_include_directories(${ZEPHYR_BASE}/subsys/net/ip)
zephyr_library_include_directories(${ZEPHYR_BASE}/subsys/net/lib/sockets)
drivers: modem: ublox-sara-r4: Support SARA-U2 modems, sense VINT This adds support for SARA-U2 modems. They have different timings on the PWR_ON pin, don't support AT+CESQ and require a manual GPRS connection setup. The VINT pin is used as a more reliable and faster way to power on the modem. Based on work by Göran Weinholt <goran.weinholt@endian.se> Signed-off-by: Michael Scott <mike@foundries.io>
2019-08-07 23:06:00 +08:00
if(CONFIG_MODEM_UBLOX_SARA)
drivers: modem: introduce u-blox SARA-R4 modem driver The u-blox SARA-R4 modem modules are Ultra-compact LTE Cat M1 / NB1 ready: - Configurable with a single hardware version - Flexible mode selection as LTE Cat M1, LTE Cat NB1, EGPRS - only/preferred - Low power consumption and longer battery life - Extended range in buildings, basements, and with NB1, underground This driver introduces support for basic AT commands to query modem information as well as socket connection for TCP/UDP communication. Signed-off-by: Michael Scott <mike@foundries.io>
2019-05-18 01:14:00 +08:00
zephyr_library_sources(ublox-sara-r4.c)
endif()
drivers: modem: Add support for quectel bg95 Adding support for Quectel BG95 Modem offloaded driver to zephyr. The driver currently implements only the client side functions of the "socket_op_vtable", and so cannot be used for cases where Zephyr acts as a server. Moreover the driver only supports TCP for now. Looking through the guides, the same driver should be usable for BG96 (and other modems) except for the modem boot-up sequence. Hence its named as "bg9x" instead of "bg95". Tested extensively with Zephyr acting as MQTT endpoint and publishing / subscribing data to / from an MQTT broker. Signed-off-by: Bilal Wasim <bilalwasim676@gmail.com>
2020-11-23 22:54:31 +08:00
if(CONFIG_MODEM_QUECTEL_BG9X)
zephyr_library_sources(quectel-bg9x.c)
endif()
drivers/modem: Switch wncm14a2a driver to new net_pkt API It is a bit awkward that ip/proto headers have to be rebuilt (with fake data in it though). Let's see in future if that's really needed, offload device handles already ip/proto headers by themselves so we should not care. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2019-02-19 18:17:51 +08:00
if(CONFIG_MODEM_WNCM14A2A)
zephyr_library_sources(wncm14a2a.c)
endif()
drivers: modem: Support GSM modems and PPP Create a driver for GSM modems that use a standard AT command set and enable Zephyr's own PPP stack for IP traffic. Signed-off-by: Patrik Flykt <patrik.flykt@intel.com>
2020-01-02 18:41:07 +08:00
if(CONFIG_MODEM_GSM_PPP)
zephyr_library_sources(gsm_ppp.c)
endif()
drivers: modem: add Sierra Wireless HL7800 Modem Driver The driver utilizes the CONFIG_NET_OFFLOAD setting to avoid the normal handling of IP packets, and instead uses a socket-like UART interface to handle incoming and outgoing data via AT commands. Signed-off-by: Ryan Erickson <ryan.erickson@lairdconnect.com>
2020-08-28 04:43:58 +08:00
if (CONFIG_MODEM_HL7800)
zephyr_library_sources(hl7800.c)
endif()
drivers: modem: Added simcom sim7080 modem driver. Implemented driver for the simcom sim7080 modem. This driver features Socket offloading, TCP, UDP, DNS, SMS, GPS and FTP. Signed-off-by: Lukas Gehreke <lk.gehreke@gmail.com>
2021-08-27 16:21:14 +08:00
if (CONFIG_MODEM_SIM7080)
zephyr_library_sources(simcom-sim7080.c)
endif()
drivers/modem: Add generic cellular modem driver The added cellular modem driver is a naive driver, which shall serve as a template for implementing tailored drivers for modems like the UBLOX-R4. It uses only generic at commands, described in 3gpp, and protocols, like CMUX and PPP. A binding for the BG95 has been added, which replaces the quectel,bg9x. This is neccesary since the BG95 does not have a usable reset pin, the reset and powerkey are internally connected to each other. Signed-off-by: Bjarki Arge Andreasen <baa@trackunit.com>
2023-04-11 00:24:56 +08:00
zephyr_library_sources_ifdef(CONFIG_MODEM_CELLULAR modem_cellular.c)