mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-12 17:41:57 +00:00
90e778d983
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>
79 lines
1.5 KiB
C
79 lines
1.5 KiB
C
/** @file
|
|
* @brief Modem pin setup for modem context driver
|
|
*
|
|
* GPIO-based pin handling for the modem context driver
|
|
*/
|
|
|
|
/*
|
|
* Copyright (c) 2019 Foundries.io
|
|
*
|
|
* SPDX-License-Identifier: Apache-2.0
|
|
*/
|
|
|
|
#include <zephyr/types.h>
|
|
#include <device.h>
|
|
#include <drivers/gpio.h>
|
|
|
|
#include "modem_context.h"
|
|
|
|
int modem_pin_read(struct modem_context *ctx, u32_t pin)
|
|
{
|
|
int ret = 0;
|
|
u32_t value = 0;
|
|
|
|
if (pin < 0 || pin >= ctx->pins_len) {
|
|
return -ENODEV;
|
|
}
|
|
|
|
ret = gpio_pin_read(ctx->pins[pin].gpio_port_dev, ctx->pins[pin].pin,
|
|
&value);
|
|
if (ret < 0) {
|
|
return ret;
|
|
}
|
|
|
|
return (int)value;
|
|
}
|
|
|
|
int modem_pin_write(struct modem_context *ctx, u32_t pin, u32_t value)
|
|
{
|
|
if (pin < 0 || pin >= ctx->pins_len) {
|
|
return -ENODEV;
|
|
}
|
|
|
|
return gpio_pin_write(ctx->pins[pin].gpio_port_dev, ctx->pins[pin].pin,
|
|
value);
|
|
}
|
|
|
|
int modem_pin_config(struct modem_context *ctx, u32_t pin, int flags)
|
|
{
|
|
if (pin < 0 || pin >= ctx->pins_len) {
|
|
return -ENODEV;
|
|
}
|
|
|
|
return gpio_pin_configure(ctx->pins[pin].gpio_port_dev,
|
|
ctx->pins[pin].pin, flags);
|
|
}
|
|
|
|
int modem_pin_init(struct modem_context *ctx)
|
|
{
|
|
int i, ret;
|
|
|
|
/* setup port devices and pin directions */
|
|
for (i = 0; i < ctx->pins_len; i++) {
|
|
ctx->pins[i].gpio_port_dev =
|
|
device_get_binding(ctx->pins[i].dev_name);
|
|
if (!ctx->pins[i].gpio_port_dev) {
|
|
return -ENODEV;
|
|
}
|
|
|
|
ret = gpio_pin_configure(ctx->pins[i].gpio_port_dev,
|
|
ctx->pins[i].pin,
|
|
ctx->pins[i].init_flags);
|
|
if (ret < 0) {
|
|
return ret;
|
|
}
|
|
}
|
|
|
|
return 0;
|
|
}
|