From: Arnaud Pouliquen <arnaud.pouliquen@st.com> To: Ohad Ben-Cohen <ohad@wizery.com>, Bjorn Andersson <bjorn.andersson@linaro.org>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Jiri Slaby <jslaby@suse.com>, linux-kernel@vger.kernel.org, linux-remoteproc@vger.kernel.org, Mathieu Poirier <mathieu.poirier@linaro.org> Cc: arnaud.pouliquen@st.com, Suman Anna <s-anna@ti.com>, Fabien DESSENNE <fabien.dessenne@st.com>, linux-stm32@st-md-mailman.stormreply.com, Alan Cox <gnomes@lxorguk.ukuu.org.uk>, xiang xiao <xiaoxiang781216@gmail.com> Subject: [PATCH v7 0/2] Add rpmsg tty driver Date: Tue, 24 Mar 2020 18:04:05 +0100 [thread overview] Message-ID: <20200324170407.16470-1-arnaud.pouliquen@st.com> (raw) This patch set introduces a TTY console on top of the RPMsg framework which enables the following use cases: - Provide a console to communicate easily with the remote processor application. - Provide an interface to get the remote processor log traces without ring buffer limitation. - Ease the migration from MPU + MCU processors to multi core processors (MPU and MCU integrated in one processor) by offering a virtual serial link. An alternative of this proposed solution would consist in using the virtio console: The drawback with that solution is that it requires a specific virtio buffer (in addition to the one already used for RPMsg) which does not fit with remote processors with little memory. The proposed solution allows to multiplex the console with the other rpmsg services, optimizing the memory. The first patch adds an API to the rpmsg framework ('get max transmission unit') and the second one is the rpmsg tty driver itself. Previous revision: - the patch 1/2 ("rpmsg: core: add API to get MTU) has been discussed in a separate thread on remoteproc mailing list: https://patchwork.kernel.org/patch/11333509/ - Previous version of the patch 2/2 (tty: add rpmsg driver) available here: https://patchwork.kernel.org/cover/11130213/ Main delta vs v6: - Pack the rpmsg_tty_ctrl struct. - MTU API acked by Suman Anna from Texas Intruments company. Arnaud Pouliquen (2): rpmsg: core: add API to get MTU tty: add rpmsg driver Documentation/serial/tty_rpmsg.rst | 45 ++++ drivers/rpmsg/rpmsg_core.c | 21 ++ drivers/rpmsg/rpmsg_internal.h | 2 + drivers/rpmsg/virtio_rpmsg_bus.c | 10 + drivers/tty/Kconfig | 9 + drivers/tty/Makefile | 1 + drivers/tty/rpmsg_tty.c | 417 +++++++++++++++++++++++++++++ include/linux/rpmsg.h | 10 + 8 files changed, 515 insertions(+) create mode 100644 Documentation/serial/tty_rpmsg.rst create mode 100644 drivers/tty/rpmsg_tty.c -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Arnaud Pouliquen <arnaud.pouliquen@st.com> To: Ohad Ben-Cohen <ohad@wizery.com>, Bjorn Andersson <bjorn.andersson@linaro.org>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Jiri Slaby <jslaby@suse.com>, <linux-kernel@vger.kernel.org>, <linux-remoteproc@vger.kernel.org>, Mathieu Poirier <mathieu.poirier@linaro.org> Cc: <arnaud.pouliquen@st.com>, Suman Anna <s-anna@ti.com>, Fabien DESSENNE <fabien.dessenne@st.com>, <linux-stm32@st-md-mailman.stormreply.com>, Alan Cox <gnomes@lxorguk.ukuu.org.uk>, xiang xiao <xiaoxiang781216@gmail.com> Subject: [PATCH v7 0/2] Add rpmsg tty driver Date: Tue, 24 Mar 2020 18:04:05 +0100 [thread overview] Message-ID: <20200324170407.16470-1-arnaud.pouliquen@st.com> (raw) This patch set introduces a TTY console on top of the RPMsg framework which enables the following use cases: - Provide a console to communicate easily with the remote processor application. - Provide an interface to get the remote processor log traces without ring buffer limitation. - Ease the migration from MPU + MCU processors to multi core processors (MPU and MCU integrated in one processor) by offering a virtual serial link. An alternative of this proposed solution would consist in using the virtio console: The drawback with that solution is that it requires a specific virtio buffer (in addition to the one already used for RPMsg) which does not fit with remote processors with little memory. The proposed solution allows to multiplex the console with the other rpmsg services, optimizing the memory. The first patch adds an API to the rpmsg framework ('get max transmission unit') and the second one is the rpmsg tty driver itself. Previous revision: - the patch 1/2 ("rpmsg: core: add API to get MTU) has been discussed in a separate thread on remoteproc mailing list: https://patchwork.kernel.org/patch/11333509/ - Previous version of the patch 2/2 (tty: add rpmsg driver) available here: https://patchwork.kernel.org/cover/11130213/ Main delta vs v6: - Pack the rpmsg_tty_ctrl struct. - MTU API acked by Suman Anna from Texas Intruments company. Arnaud Pouliquen (2): rpmsg: core: add API to get MTU tty: add rpmsg driver Documentation/serial/tty_rpmsg.rst | 45 ++++ drivers/rpmsg/rpmsg_core.c | 21 ++ drivers/rpmsg/rpmsg_internal.h | 2 + drivers/rpmsg/virtio_rpmsg_bus.c | 10 + drivers/tty/Kconfig | 9 + drivers/tty/Makefile | 1 + drivers/tty/rpmsg_tty.c | 417 +++++++++++++++++++++++++++++ include/linux/rpmsg.h | 10 + 8 files changed, 515 insertions(+) create mode 100644 Documentation/serial/tty_rpmsg.rst create mode 100644 drivers/tty/rpmsg_tty.c -- 2.17.1
next reply other threads:[~2020-03-24 17:04 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-24 17:04 Arnaud Pouliquen [this message] 2020-03-24 17:04 ` [PATCH v7 0/2] Add rpmsg tty driver Arnaud Pouliquen 2020-03-24 17:04 ` [PATCH v7 1/2] rpmsg: core: add API to get MTU Arnaud Pouliquen 2020-03-24 17:04 ` Arnaud Pouliquen 2020-03-31 17:36 ` Mathieu Poirier 2020-04-01 6:28 ` Jiri Slaby 2020-04-01 6:29 ` Jiri Slaby 2020-04-01 11:34 ` Arnaud POULIQUEN 2020-04-01 11:34 ` Arnaud POULIQUEN 2020-03-24 17:04 ` [PATCH v7 2/2] tty: add rpmsg driver Arnaud Pouliquen 2020-03-24 17:04 ` Arnaud Pouliquen 2020-03-24 17:18 ` Greg Kroah-Hartman 2020-03-25 11:34 ` Arnaud POULIQUEN 2020-03-25 11:34 ` Arnaud POULIQUEN 2020-03-24 17:23 ` Joe Perches 2020-03-25 11:36 ` Arnaud POULIQUEN 2020-03-25 11:36 ` Arnaud POULIQUEN 2020-03-24 17:44 ` Randy Dunlap 2020-03-25 8:10 ` Jiri Slaby 2020-03-25 11:39 ` Arnaud POULIQUEN 2020-03-25 11:39 ` Arnaud POULIQUEN 2020-03-24 20:52 ` Bjorn Andersson 2020-03-24 20:52 ` Bjorn Andersson 2020-03-25 16:57 ` Arnaud POULIQUEN 2020-03-25 16:57 ` Arnaud POULIQUEN 2020-04-06 14:18 ` Arnaud POULIQUEN 2020-04-06 14:18 ` Arnaud POULIQUEN 2020-05-06 2:54 ` Bjorn Andersson 2020-05-06 10:21 ` Arnaud POULIQUEN 2020-03-25 8:45 ` Jiri Slaby 2020-03-25 13:15 ` Arnaud POULIQUEN 2020-03-25 13:15 ` Arnaud POULIQUEN 2020-03-25 13:31 ` Jiri Slaby 2020-03-26 0:01 ` Joe Perches 2020-03-26 6:38 ` Jiri Slaby 2020-03-26 10:59 ` Arnaud POULIQUEN 2020-03-26 10:59 ` Arnaud POULIQUEN 2020-03-26 12:31 ` Jiri Slaby 2020-03-26 11:40 ` Arnaud POULIQUEN 2020-03-26 11:40 ` Arnaud POULIQUEN 2020-03-26 11:45 ` Jiri Slaby 2020-04-01 18:06 ` Mathieu Poirier 2020-04-02 15:25 ` Arnaud POULIQUEN 2020-04-02 15:25 ` Arnaud POULIQUEN 2020-04-03 20:18 ` Mathieu Poirier 2020-07-15 16:06 ` [PATCH v7 0/2] Add rpmsg tty driver Arnaud POULIQUEN
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20200324170407.16470-1-arnaud.pouliquen@st.com \ --to=arnaud.pouliquen@st.com \ --cc=bjorn.andersson@linaro.org \ --cc=fabien.dessenne@st.com \ --cc=gnomes@lxorguk.ukuu.org.uk \ --cc=gregkh@linuxfoundation.org \ --cc=jslaby@suse.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-remoteproc@vger.kernel.org \ --cc=linux-stm32@st-md-mailman.stormreply.com \ --cc=mathieu.poirier@linaro.org \ --cc=ohad@wizery.com \ --cc=s-anna@ti.com \ --cc=xiaoxiang781216@gmail.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.