michaelh/zephyr
1
0
Fork 0
Code Releases Activity
42554 commits 87 branches 0 tags 617 MiB
Commit graph

3 commits

Author SHA1 Message Date
Jukka Rissanen 775dcb222e modem: gsm: Initialize the modem UART separately 
This is needed if muxing is enabled in which case we must
change the UART to muxing UART after the AT+CMUX command
has succeed.

Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
 2020-04-17 10:15:54 +03:00
Patrik Flykt 12f381888f drivers: modem: Document UART device name 
Document that the third argument is the UART device name.

Signed-off-by: Patrik Flykt <patrik.flykt@intel.com>
 2019-12-02 15:34:45 +01:00
Michael Scott d56a05f7a7 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-10 00:03:39 +02:00