From patchwork Wed Sep 4 13:09:53 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Arnaud POULIQUEN X-Patchwork-Id: 11130209 Return-Path: Received: from mail.kernel.org (pdx-korg-mail-1.web.codeaurora.org [172.30.200.123]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id 724021395 for ; Wed, 4 Sep 2019 13:15:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 3690A2168B for ; Wed, 4 Sep 2019 13:15:26 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=st.com header.i=@st.com header.b="mzs0Usqt" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727722AbfIDNPZ (ORCPT ); Wed, 4 Sep 2019 09:15:25 -0400 Received: from mx08-00178001.pphosted.com ([91.207.212.93]:47926 "EHLO mx07-00178001.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726304AbfIDNPZ (ORCPT ); Wed, 4 Sep 2019 09:15:25 -0400 Received: from pps.filterd (m0046661.ppops.net [127.0.0.1]) by mx08-00178001.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id x84DBDK4012924; Wed, 4 Sep 2019 15:15:11 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=st.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-type; s=STMicroelectronics; bh=CO5WI1jGjHG1YVlzIQ/9Wn98440C6VGwm+7gN346xUM=; b=mzs0UsqtqAEnTmyvumphQzzcaQtyDaqcuaDYqJWcnz1m7ZS5LzcethVTPM1lHMB3Bv6L pAUoYS+jluw6FymHjCeGIidnM+iI9EgNIa4LD0G1ddmJdWO6gtqwkDCSOw5qeE5oDRLS lRfAbvwjuwm7u237F5AuPAMjxjY5O9onqJrjyBdWl00AmZjRi83WDomn28bmXhh8UYpV 7taK/4iluXU8DMheFTjYhPDyI6s8DYuMQkazKOGE1XfVkehwiI54g5OrUAfjrrR7t98F 3Cxb/BL2PLAzGiGOCmboH9JX5Hc3zDaXFPiBSUoAX5TxtjdyKsvMIMXAc2pi1FbYiBSV 7w== Received: from beta.dmz-ap.st.com (beta.dmz-ap.st.com [138.198.100.35]) by mx08-00178001.pphosted.com with ESMTP id 2uqfsj1aw5-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 04 Sep 2019 15:15:11 +0200 Received: from euls16034.sgp.st.com (euls16034.sgp.st.com [10.75.44.20]) by beta.dmz-ap.st.com (STMicroelectronics) with ESMTP id 6382D4B; Wed, 4 Sep 2019 13:15:08 +0000 (GMT) Received: from Webmail-eu.st.com (Safex1hubcas23.st.com [10.75.90.46]) by euls16034.sgp.st.com (STMicroelectronics) with ESMTP id 0E2C82D5178; Wed, 4 Sep 2019 15:15:08 +0200 (CEST) Received: from SAFEX1HUBCAS21.st.com (10.75.90.45) by SAFEX1HUBCAS23.st.com (10.75.90.46) with Microsoft SMTP Server (TLS) id 14.3.439.0; Wed, 4 Sep 2019 15:15:07 +0200 Received: from localhost (10.48.0.131) by Webmail-ga.st.com (10.75.90.48) with Microsoft SMTP Server (TLS) id 14.3.439.0; Wed, 4 Sep 2019 15:15:07 +0200 From: Arnaud Pouliquen To: Ohad Ben-Cohen , Bjorn Andersson , Greg Kroah-Hartman , Jiri Slaby , xiang xiao , , CC: , Suman Anna , Fabien DESSENNE , , "Alan Cox" Subject: [PATCH v6 1/2] rpmsg: core: add API to get message length Date: Wed, 4 Sep 2019 15:09:53 +0200 Message-ID: <1567602594-2913-2-git-send-email-arnaud.pouliquen@st.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1567602594-2913-1-git-send-email-arnaud.pouliquen@st.com> References: <1567602594-2913-1-git-send-email-arnaud.pouliquen@st.com> MIME-Version: 1.0 X-Originating-IP: [10.48.0.131] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.70,1.0.8 definitions=2019-09-04_04:2019-09-03,2019-09-04 signatures=0 Sender: linux-remoteproc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-remoteproc@vger.kernel.org Return the rpmsg buffer size for sending message, so rpmsg users can split a long message in several sub rpmsg buffers. Signed-off-by: Arnaud Pouliquen --- drivers/rpmsg/rpmsg_core.c | 21 +++++++++++++++++++++ drivers/rpmsg/rpmsg_internal.h | 2 ++ drivers/rpmsg/virtio_rpmsg_bus.c | 10 ++++++++++ include/linux/rpmsg.h | 10 ++++++++++ 4 files changed, 43 insertions(+) diff --git a/drivers/rpmsg/rpmsg_core.c b/drivers/rpmsg/rpmsg_core.c index e330ec4dfc33..a6ef54c4779a 100644 --- a/drivers/rpmsg/rpmsg_core.c +++ b/drivers/rpmsg/rpmsg_core.c @@ -283,6 +283,27 @@ int rpmsg_trysend_offchannel(struct rpmsg_endpoint *ept, u32 src, u32 dst, } EXPORT_SYMBOL(rpmsg_trysend_offchannel); +/** + * rpmsg_get_mtu() - get maximum transmission buffer size for sending message. + * @ept: the rpmsg endpoint + * + * This function returns maximum buffer size available for a single message. + * + * Return: the maximum transmission size on success and an appropriate error + * value on failure. + */ + +ssize_t rpmsg_get_mtu(struct rpmsg_endpoint *ept) +{ + if (WARN_ON(!ept)) + return -EINVAL; + if (!ept->ops->get_mtu) + return -ENOTSUPP; + + return ept->ops->get_mtu(ept); +} +EXPORT_SYMBOL(rpmsg_get_mtu); + /* * match an rpmsg channel with a channel info struct. * this is used to make sure we're not creating rpmsg devices for channels diff --git a/drivers/rpmsg/rpmsg_internal.h b/drivers/rpmsg/rpmsg_internal.h index 3fc83cd50e98..12b9e72adc75 100644 --- a/drivers/rpmsg/rpmsg_internal.h +++ b/drivers/rpmsg/rpmsg_internal.h @@ -47,6 +47,7 @@ struct rpmsg_device_ops { * @trysendto: see @rpmsg_trysendto(), optional * @trysend_offchannel: see @rpmsg_trysend_offchannel(), optional * @poll: see @rpmsg_poll(), optional + * @get_mtu: see @get_mpu(), required * * Indirection table for the operations that a rpmsg backend should implement. * In addition to @destroy_ept, the backend must at least implement @send and @@ -66,6 +67,7 @@ struct rpmsg_endpoint_ops { void *data, int len); __poll_t (*poll)(struct rpmsg_endpoint *ept, struct file *filp, poll_table *wait); + ssize_t (*get_mtu)(struct rpmsg_endpoint *ept); }; int rpmsg_register_device(struct rpmsg_device *rpdev); diff --git a/drivers/rpmsg/virtio_rpmsg_bus.c b/drivers/rpmsg/virtio_rpmsg_bus.c index 376ebbf880d6..fab01b67a550 100644 --- a/drivers/rpmsg/virtio_rpmsg_bus.c +++ b/drivers/rpmsg/virtio_rpmsg_bus.c @@ -175,6 +175,7 @@ static int virtio_rpmsg_trysendto(struct rpmsg_endpoint *ept, void *data, int len, u32 dst); static int virtio_rpmsg_trysend_offchannel(struct rpmsg_endpoint *ept, u32 src, u32 dst, void *data, int len); +static ssize_t virtio_rpmsg_get_buf_mtu(struct rpmsg_endpoint *ept); static const struct rpmsg_endpoint_ops virtio_endpoint_ops = { .destroy_ept = virtio_rpmsg_destroy_ept, @@ -184,6 +185,7 @@ static const struct rpmsg_endpoint_ops virtio_endpoint_ops = { .trysend = virtio_rpmsg_trysend, .trysendto = virtio_rpmsg_trysendto, .trysend_offchannel = virtio_rpmsg_trysend_offchannel, + .get_mtu = virtio_rpmsg_get_buf_mtu, }; /** @@ -699,6 +701,14 @@ static int virtio_rpmsg_trysend_offchannel(struct rpmsg_endpoint *ept, u32 src, return rpmsg_send_offchannel_raw(rpdev, src, dst, data, len, false); } +static ssize_t virtio_rpmsg_get_buf_mtu(struct rpmsg_endpoint *ept) +{ + struct rpmsg_device *rpdev = ept->rpdev; + struct virtio_rpmsg_channel *vch = to_virtio_rpmsg_channel(rpdev); + + return vch->vrp->buf_size - sizeof(struct rpmsg_hdr); +} + static int rpmsg_recv_single(struct virtproc_info *vrp, struct device *dev, struct rpmsg_hdr *msg, unsigned int len) { diff --git a/include/linux/rpmsg.h b/include/linux/rpmsg.h index 9fe156d1c018..9d638bf2bdce 100644 --- a/include/linux/rpmsg.h +++ b/include/linux/rpmsg.h @@ -135,6 +135,8 @@ int rpmsg_trysend_offchannel(struct rpmsg_endpoint *ept, u32 src, u32 dst, __poll_t rpmsg_poll(struct rpmsg_endpoint *ept, struct file *filp, poll_table *wait); +ssize_t rpmsg_get_mtu(struct rpmsg_endpoint *ept); + #else static inline int register_rpmsg_device(struct rpmsg_device *dev) @@ -242,6 +244,14 @@ static inline __poll_t rpmsg_poll(struct rpmsg_endpoint *ept, return 0; } +static ssize_t rpmsg_get_mtu(struct rpmsg_endpoint *ept) +{ + /* This shouldn't be possible */ + WARN_ON(1); + + return -ENXIO; +} + #endif /* IS_ENABLED(CONFIG_RPMSG) */ /* use a macro to avoid include chaining to get THIS_MODULE */ From patchwork Wed Sep 4 13:09:54 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Arnaud POULIQUEN X-Patchwork-Id: 11130211 Return-Path: Received: from mail.kernel.org (pdx-korg-mail-1.web.codeaurora.org [172.30.200.123]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id A5C5113B1 for ; Wed, 4 Sep 2019 13:15:32 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 7423B2168B for ; Wed, 4 Sep 2019 13:15:31 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=st.com header.i=@st.com header.b="VA6a5LHc" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730214AbfIDNP2 (ORCPT ); Wed, 4 Sep 2019 09:15:28 -0400 Received: from mx07-00178001.pphosted.com ([62.209.51.94]:34802 "EHLO mx07-00178001.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727544AbfIDNP1 (ORCPT ); Wed, 4 Sep 2019 09:15:27 -0400 Received: from pps.filterd (m0046668.ppops.net [127.0.0.1]) by mx07-00178001.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id x84DB7Y5026206; Wed, 4 Sep 2019 15:15:13 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=st.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-type; s=STMicroelectronics; bh=rHs48U0CdGwdE77gLWPedU73gZMGyShIbzdKyGXhD/8=; b=VA6a5LHcTf9wxOqVl7kW8K/0vEvHGHUWI3lLtPC0eI44YKBtrNeL621u7Kl2pK5lClKW WZ56pzOEiVhlAb8Qrmlh52FYXQj+8bzZLTvn185prP6UZIZn7vQo5Hs0u3CRpp5qBvve /KhLWrrgeSYDe9HflUyKatiaU3PDVF56kU2SG0uMQrhyYlomU6fsDAmeFJ3biHv8EgsG b4Q0Rl4HL/m1dbXZ/WZo4ALJdVYgjlr67hvmeU8VscRWwQyDPnYwZXhGg6G/gvpMRuXh t8tqt4GlHznUQxFqbrLp9MtFoG9Lq/K3xlooqxpfdWdzJiokK/WI9bNo1eEFtnDP1w+a UQ== Received: from beta.dmz-ap.st.com (beta.dmz-ap.st.com [138.198.100.35]) by mx07-00178001.pphosted.com with ESMTP id 2uqec31j6a-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 04 Sep 2019 15:15:13 +0200 Received: from euls16034.sgp.st.com (euls16034.sgp.st.com [10.75.44.20]) by beta.dmz-ap.st.com (STMicroelectronics) with ESMTP id A0D674C; Wed, 4 Sep 2019 13:15:09 +0000 (GMT) Received: from Webmail-eu.st.com (Safex1hubcas24.st.com [10.75.90.94]) by euls16034.sgp.st.com (STMicroelectronics) with ESMTP id 56E0A2D5178; Wed, 4 Sep 2019 15:15:09 +0200 (CEST) Received: from SAFEX1HUBCAS21.st.com (10.75.90.45) by Safex1hubcas24.st.com (10.75.90.94) with Microsoft SMTP Server (TLS) id 14.3.439.0; Wed, 4 Sep 2019 15:15:09 +0200 Received: from localhost (10.48.0.131) by Webmail-ga.st.com (10.75.90.48) with Microsoft SMTP Server (TLS) id 14.3.439.0; Wed, 4 Sep 2019 15:15:08 +0200 From: Arnaud Pouliquen To: Ohad Ben-Cohen , Bjorn Andersson , Greg Kroah-Hartman , Jiri Slaby , xiang xiao , , CC: , Suman Anna , Fabien DESSENNE , , "Alan Cox" Subject: [PATCH v6 2/2] tty: add rpmsg driver Date: Wed, 4 Sep 2019 15:09:54 +0200 Message-ID: <1567602594-2913-3-git-send-email-arnaud.pouliquen@st.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1567602594-2913-1-git-send-email-arnaud.pouliquen@st.com> References: <1567602594-2913-1-git-send-email-arnaud.pouliquen@st.com> MIME-Version: 1.0 X-Originating-IP: [10.48.0.131] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.70,1.0.8 definitions=2019-09-04_04:2019-09-03,2019-09-04 signatures=0 Sender: linux-remoteproc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-remoteproc@vger.kernel.org This driver exposes a standard tty interface on top of the rpmsg framework through a rpmsg service. This driver supports multi-instances, offering a /dev/ttyRPMSGx entry per rpmsg endpoint. Signed-off-by: Arnaud Pouliquen Signed-off-by: Fabien Dessenne --- Documentation/serial/tty_rpmsg.rst | 45 ++++ drivers/tty/Kconfig | 9 + drivers/tty/Makefile | 1 + drivers/tty/rpmsg_tty.c | 418 +++++++++++++++++++++++++++++++++++++ 4 files changed, 473 insertions(+) create mode 100644 Documentation/serial/tty_rpmsg.rst create mode 100644 drivers/tty/rpmsg_tty.c diff --git a/Documentation/serial/tty_rpmsg.rst b/Documentation/serial/tty_rpmsg.rst new file mode 100644 index 000000000000..fc1d3fba73c5 --- /dev/null +++ b/Documentation/serial/tty_rpmsg.rst @@ -0,0 +1,45 @@ +.. SPDX-License-Identifier: GPL-2.0 + +============= +The rpmsg TTY +============= + +The rpmsg tty driver implements serial communication on the RPMsg bus to makes possible for user-space programs to send and receive rpmsg messages as a standard tty protocol. + +The remote processor can instantiate a new tty by requesting: +- a "rpmsg-tty-raw" RPMsg service, for TTY raw data support without flow control +- a "rpmsg-tty-ctrl" RPMSg service, for TTY support with flow control. + +Information related to the RPMsg and associated tty device is available in +/sys/bus/rpmsg/devices/. + +RPMsg TTY without control +--------------------- + +The default end point associated with the "rpmsg-tty-raw" service is directly +used for data exchange. No flow control is available. + +To be compliant with this driver, the remote firmware must create its data end point associated with the "rpmsg-tty-raw" service. + +RPMsg TTY with control +--------------------- + +The default end point associated with the "rpmsg-tty-ctrl" service is reserved for +the control. A second endpoint must be created for data exchange. + +The control channel is used to transmit to the remote processor the CTS status, +as well as the end point address for data transfer. + +To be compatible with this driver, the remote firmware must create or use its end point associated with "rpmsg-tty-ctrl" service, plus a second endpoint for the data flow. +On Linux rpmsg_tty probes, the data endpoint address and the CTS (set to disable) +is sent to the remote processor. +The remote processor has to respect following rules: +- It only transmits data when Linux remote cts is enable, otherwise message + could be lost. +- It can pause/resume reception by sending a control message (rely on CTS state). + +Control message structure: +struct rpmsg_tty_ctrl { + u8 cts; /* remote reception status */ + u16 d_ept_addr; /* data endpoint address */ +}; diff --git a/drivers/tty/Kconfig b/drivers/tty/Kconfig index c7623f99ac0f..1046bf4aa709 100644 --- a/drivers/tty/Kconfig +++ b/drivers/tty/Kconfig @@ -454,6 +454,15 @@ config VCC help Support for Sun logical domain consoles. +config RPMSG_TTY + tristate "RPMSG tty driver" + depends on RPMSG + help + Say y here to export rpmsg endpoints as tty devices, usually found + in /dev/ttyRPMSGx. + This makes it possible for user-space programs to send and receive + rpmsg messages as a standard tty protocol. + config LDISC_AUTOLOAD bool "Automatically load TTY Line Disciplines" default y diff --git a/drivers/tty/Makefile b/drivers/tty/Makefile index 020b1cd9294f..c2465e7ebc2a 100644 --- a/drivers/tty/Makefile +++ b/drivers/tty/Makefile @@ -34,5 +34,6 @@ obj-$(CONFIG_PPC_EPAPR_HV_BYTECHAN) += ehv_bytechan.o obj-$(CONFIG_GOLDFISH_TTY) += goldfish.o obj-$(CONFIG_MIPS_EJTAG_FDC_TTY) += mips_ejtag_fdc.o obj-$(CONFIG_VCC) += vcc.o +obj-$(CONFIG_RPMSG_TTY) += rpmsg_tty.o obj-y += ipwireless/ diff --git a/drivers/tty/rpmsg_tty.c b/drivers/tty/rpmsg_tty.c new file mode 100644 index 000000000000..3e4d0e1a6663 --- /dev/null +++ b/drivers/tty/rpmsg_tty.c @@ -0,0 +1,418 @@ +// SPDX-License-Identifier: GPL-2.0 +/* + * Copyright (C) STMicroelectronics 2019 - All Rights Reserved + * Authors: Arnaud Pouliquen for STMicroelectronics. + */ + +#include +#include +#include +#include +#include + +#define MAX_TTY_RPMSG 32 + +#define TTY_CH_NAME_RAW "rpmsg-tty-raw" +#define TTY_CH_NAME_WITH_CTS "rpmsg-tty-ctrl" + +static DEFINE_IDR(tty_idr); /* tty instance id */ +static DEFINE_MUTEX(idr_lock); /* protects tty_idr */ + +static struct tty_driver *rpmsg_tty_driver; + +struct rpmsg_tty_ctrl { + u8 cts; /* remote reception status */ + u16 d_ept_addr; /* data endpoint address */ +}; + +struct rpmsg_tty_port { + struct tty_port port; /* TTY port data */ + int id; /* TTY rpmsg index */ + bool cts; /* remote reception status */ + struct rpmsg_device *rpdev; /* rpmsg device */ + struct rpmsg_endpoint *cs_ept; /* channel control endpoint */ + struct rpmsg_endpoint *d_ept; /* data endpoint */ + u32 data_dst; /* data destination endpoint address */ +}; + +typedef void (*rpmsg_tty_rx_cb_t)(struct rpmsg_device *, void *, int, void *, + u32); + +static int rpmsg_tty_cb(struct rpmsg_device *rpdev, void *data, int len, + void *priv, u32 src) +{ + struct rpmsg_tty_port *cport = dev_get_drvdata(&rpdev->dev); + int copied; + + if (src == cport->data_dst) { + /* data message */ + if (!len) + return -EINVAL; + /* data message */ + copied = tty_insert_flip_string_fixed_flag(&cport->port, data, + TTY_NORMAL, len); + if (copied != len) + dev_dbg(&rpdev->dev, "trunc buffer: available space is %d\n", + copied); + tty_flip_buffer_push(&cport->port); + } else { + /* control message */ + struct rpmsg_tty_ctrl *msg = data; + + if (len != sizeof(*msg)) + return -EINVAL; + + cport->data_dst = msg->d_ept_addr; + + /* Update remote cts state */ + cport->cts = msg->cts ? 1 : 0; + + if (cport->cts) + tty_port_tty_wakeup(&cport->port); + } + + return 0; +} + +static void rpmsg_tty_send_term_ready(struct tty_struct *tty, u8 state) +{ + struct rpmsg_tty_port *cport = tty->driver_data; + struct rpmsg_tty_ctrl m_ctrl; + int ret; + + m_ctrl.cts = state; + m_ctrl.d_ept_addr = cport->d_ept->addr; + + ret = rpmsg_trysend(cport->cs_ept, &m_ctrl, sizeof(m_ctrl)); + if (ret < 0) + dev_dbg(tty->dev, "cannot send control (%d)\n", ret); +}; + +static void rpmsg_tty_throttle(struct tty_struct *tty) +{ + struct rpmsg_tty_port *cport = tty->driver_data; + + /* Disable remote transmission */ + if (cport->cs_ept) + rpmsg_tty_send_term_ready(tty, 0); +}; + +static void rpmsg_tty_unthrottle(struct tty_struct *tty) +{ + struct rpmsg_tty_port *cport = tty->driver_data; + + /* Enable remote transmission */ + if (cport->cs_ept) + rpmsg_tty_send_term_ready(tty, 1); +}; + +static int rpmsg_tty_install(struct tty_driver *driver, struct tty_struct *tty) +{ + struct rpmsg_tty_port *cport = idr_find(&tty_idr, tty->index); + + if (!cport) { + dev_err(tty->dev, "cannot get cport\n"); + return -ENODEV; + } + + tty->driver_data = cport; + + return tty_port_install(&cport->port, driver, tty); +} + +static int rpmsg_tty_open(struct tty_struct *tty, struct file *filp) +{ + return tty_port_open(tty->port, tty, filp); +} + +static void rpmsg_tty_close(struct tty_struct *tty, struct file *filp) +{ + return tty_port_close(tty->port, tty, filp); +} + +static int rpmsg_tty_write(struct tty_struct *tty, const u8 *buf, int len) +{ + struct rpmsg_tty_port *cport = tty->driver_data; + struct rpmsg_device *rpdev; + int msg_max_size, msg_size; + int ret; + u8 *tmpbuf; + + /* If cts not set, the message is not sent*/ + if (!cport->cts) + return 0; + + rpdev = cport->rpdev; + + dev_dbg(&rpdev->dev, "%s: send msg from tty->index = %d, len = %d\n", + __func__, tty->index, len); + + msg_max_size = rpmsg_get_mtu(rpdev->ept); + + msg_size = min(len, msg_max_size); + tmpbuf = kzalloc(msg_size, GFP_KERNEL); + if (!tmpbuf) + return -ENOMEM; + + memcpy(tmpbuf, buf, msg_size); + + /* + * Try to send the message to remote processor, if failed return 0 as + * no data sent + */ + ret = rpmsg_trysendto(cport->d_ept, tmpbuf, msg_size, cport->data_dst); + kfree(tmpbuf); + if (ret) { + dev_dbg(&rpdev->dev, "rpmsg_send failed: %d\n", ret); + return 0; + } + + return msg_size; +} + +static int rpmsg_tty_write_room(struct tty_struct *tty) +{ + struct rpmsg_tty_port *cport = tty->driver_data; + + return cport->cts ? rpmsg_get_mtu(cport->rpdev->ept) : 0; +} + +static const struct tty_operations rpmsg_tty_ops = { + .install = rpmsg_tty_install, + .open = rpmsg_tty_open, + .close = rpmsg_tty_close, + .write = rpmsg_tty_write, + .write_room = rpmsg_tty_write_room, + .throttle = rpmsg_tty_throttle, + .unthrottle = rpmsg_tty_unthrottle, +}; + +static struct rpmsg_tty_port *rpmsg_tty_alloc_cport(void) +{ + struct rpmsg_tty_port *cport; + + cport = kzalloc(sizeof(*cport), GFP_KERNEL); + if (!cport) + return ERR_PTR(-ENOMEM); + + mutex_lock(&idr_lock); + cport->id = idr_alloc(&tty_idr, cport, 0, MAX_TTY_RPMSG, GFP_KERNEL); + mutex_unlock(&idr_lock); + + if (cport->id < 0) { + kfree(cport); + return ERR_PTR(-ENOSPC); + } + + return cport; +} + +static void rpmsg_tty_release_cport(struct rpmsg_tty_port *cport) +{ + mutex_lock(&idr_lock); + idr_remove(&tty_idr, cport->id); + mutex_unlock(&idr_lock); + + kfree(cport); +} + +static int rpmsg_tty_port_activate(struct tty_port *p, struct tty_struct *tty) +{ + p->low_latency = (p->flags & ASYNC_LOW_LATENCY) ? 1 : 0; + + /* Allocate the buffer we use for writing data */ + return tty_port_alloc_xmit_buf(p); +} + +static void rpmsg_tty_port_shutdown(struct tty_port *p) +{ + /* Free the write buffer */ + tty_port_free_xmit_buf(p); +} + +static void rpmsg_tty_dtr_rts(struct tty_port *port, int raise) +{ + dev_dbg(port->tty->dev, "%s: dtr_rts state %d\n", __func__, raise); + + if (raise) + rpmsg_tty_unthrottle(port->tty); + else + rpmsg_tty_throttle(port->tty); +} + +static const struct tty_port_operations rpmsg_tty_port_ops = { + .activate = rpmsg_tty_port_activate, + .shutdown = rpmsg_tty_port_shutdown, + .dtr_rts = rpmsg_tty_dtr_rts, +}; + +static int rpmsg_tty_probe(struct rpmsg_device *rpdev) +{ + struct rpmsg_tty_port *cport; + struct device *dev = &rpdev->dev; + struct rpmsg_channel_info chinfo; + struct device *tty_dev; + int ret; + + cport = rpmsg_tty_alloc_cport(); + if (IS_ERR(cport)) { + dev_err(dev, "failed to alloc tty port\n"); + return PTR_ERR(cport); + } + + if (!strncmp(rpdev->id.name, TTY_CH_NAME_WITH_CTS, + sizeof(TTY_CH_NAME_WITH_CTS))) { + /* + * the default endpoint is used for control. Create a second + * endpoint for the data that would be exchanges trough control + * endpoint. address of the data endpoint will be provided with + * the cts state + */ + cport->cs_ept = rpdev->ept; + cport->data_dst = RPMSG_ADDR_ANY; + + strscpy(chinfo.name, TTY_CH_NAME_WITH_CTS, sizeof(chinfo.name)); + chinfo.src = RPMSG_ADDR_ANY; + chinfo.dst = RPMSG_ADDR_ANY; + + cport->d_ept = rpmsg_create_ept(rpdev, rpmsg_tty_cb, cport, + chinfo); + if (!cport->d_ept) { + dev_err(dev, "failed to create tty control channel\n"); + ret = -ENOMEM; + goto err_r_cport; + } + dev_dbg(dev, "%s: creating data endpoint with address %#x\n", + __func__, cport->d_ept->addr); + } else { + /* + * TTY over rpmsg without CTS management the default endpoint + * is use for raw data transmission. + */ + cport->cs_ept = NULL; + cport->cts = 1; + cport->d_ept = rpdev->ept; + cport->data_dst = rpdev->dst; + } + + tty_port_init(&cport->port); + cport->port.ops = &rpmsg_tty_port_ops; + + tty_dev = tty_port_register_device(&cport->port, rpmsg_tty_driver, + cport->id, dev); + if (IS_ERR(tty_dev)) { + dev_err(dev, "failed to register tty port\n"); + ret = PTR_ERR(tty_dev); + goto err_destroy; + } + + cport->rpdev = rpdev; + + dev_set_drvdata(dev, cport); + + dev_dbg(dev, "new channel: 0x%x -> 0x%x : ttyRPMSG%d\n", + rpdev->src, rpdev->dst, cport->id); + + return 0; + +err_destroy: + tty_port_destroy(&cport->port); + if (cport->cs_ept) + rpmsg_destroy_ept(cport->d_ept); +err_r_cport: + rpmsg_tty_release_cport(cport); + + return ret; +} + +static void rpmsg_tty_remove(struct rpmsg_device *rpdev) +{ + struct rpmsg_tty_port *cport = dev_get_drvdata(&rpdev->dev); + + dev_dbg(&rpdev->dev, "removing rpmsg tty device %d\n", cport->id); + + /* User hang up to release the tty */ + if (tty_port_initialized(&cport->port)) + tty_port_tty_hangup(&cport->port, false); + + tty_unregister_device(rpmsg_tty_driver, cport->id); + + tty_port_destroy(&cport->port); + if (cport->cs_ept) + rpmsg_destroy_ept(cport->d_ept); + rpmsg_tty_release_cport(cport); +} + +static struct rpmsg_device_id rpmsg_driver_tty_id_table[] = { + { .name = TTY_CH_NAME_RAW }, + { .name = TTY_CH_NAME_WITH_CTS}, + { }, +}; +MODULE_DEVICE_TABLE(rpmsg, rpmsg_driver_tty_id_table); + +static struct rpmsg_driver rpmsg_tty_rpmsg_drv = { + .drv.name = KBUILD_MODNAME, + .id_table = rpmsg_driver_tty_id_table, + .probe = rpmsg_tty_probe, + .callback = rpmsg_tty_cb, + .remove = rpmsg_tty_remove, +}; + +static int __init rpmsg_tty_init(void) +{ + int err; + + rpmsg_tty_driver = tty_alloc_driver(MAX_TTY_RPMSG, TTY_DRIVER_REAL_RAW | + TTY_DRIVER_DYNAMIC_DEV); + if (IS_ERR(rpmsg_tty_driver)) + return PTR_ERR(rpmsg_tty_driver); + + rpmsg_tty_driver->driver_name = "rpmsg_tty"; + rpmsg_tty_driver->name = "ttyRPMSG"; + rpmsg_tty_driver->major = 0; + rpmsg_tty_driver->type = TTY_DRIVER_TYPE_CONSOLE; + + /* Disable unused mode by default */ + rpmsg_tty_driver->init_termios = tty_std_termios; + rpmsg_tty_driver->init_termios.c_lflag &= ~(ECHO | ICANON); + rpmsg_tty_driver->init_termios.c_oflag &= ~(OPOST | ONLCR); + + tty_set_operations(rpmsg_tty_driver, &rpmsg_tty_ops); + + err = tty_register_driver(rpmsg_tty_driver); + if (err < 0) { + pr_err("Couldn't install rpmsg tty driver: err %d\n", err); + goto error_put; + } + + err = register_rpmsg_driver(&rpmsg_tty_rpmsg_drv); + if (err < 0) { + pr_err("Couldn't register rpmsg tty driver: err %d\n", err); + goto error_unregister; + } + + return 0; + +error_unregister: + tty_unregister_driver(rpmsg_tty_driver); + +error_put: + put_tty_driver(rpmsg_tty_driver); + + return err; +} + +static void __exit rpmsg_tty_exit(void) +{ + unregister_rpmsg_driver(&rpmsg_tty_rpmsg_drv); + tty_unregister_driver(rpmsg_tty_driver); + put_tty_driver(rpmsg_tty_driver); + idr_destroy(&tty_idr); +} + +module_init(rpmsg_tty_init); +module_exit(rpmsg_tty_exit); + +MODULE_AUTHOR("Arnaud Pouliquen "); +MODULE_DESCRIPTION("remote processor messaging tty driver"); +MODULE_LICENSE("GPL v2");