From: Arnaud POULIQUEN <arnaud.pouliquen@foss.st.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Russell King <linux@armlinux.org.uk>,
Arnd Bergmann <arnd@arndb.de>, Joel Stanley <joel@jms.id.au>,
Dmitry Osipenko <digetx@gmail.com>,
Thierry Reding <treding@nvidia.com>,
Manivannan Sadhasivam <mani@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] ARM: multi_v7_defconfig: Enable CONFIG_RPMSG_TTY
Date: Tue, 21 Dec 2021 10:05:56 +0100 [thread overview]
Message-ID: <214788db-6774-5501-bc12-67d3135b50ec@foss.st.com> (raw)
In-Reply-To: <YcC2M/QseKewXDGw@kroah.com>
On 12/20/21 5:58 PM, Greg Kroah-Hartman wrote:
> On Mon, Dec 20, 2021 at 05:11:55PM +0100, Arnaud Pouliquen wrote:
>> The RPMsg TTY implements an inter-processor communication with a standard
>> TTY interface on top of the RPMsg framework.
>> This driver is a generic RPMsg client that can run on different platforms.
>>
>> By enabling the RPMSG_TTY driver as module in multi_v7_defconfig, it makes
>> possible to automatically probe the rpmsg_tty driver by the RPMsg bus,
>> when the support of the RPMsg service is dynamically requested by the
>> co-processor firmware.
>>
>> Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>
>> ---
>> delta vs V1:
>> add
>> ---
>
> "add"? What does that mean?
Oops, sorry, part of my sentence has disappeared
"Add more description in commit message to detail the objective ".
>
> Do all v7 chips have this hardware?
I would say yes and no
No - As mainly used today for hardware system integrating a main and a
coprocessor in a single chip.
Yes - as that depends on the RPMsg back-end
The RPMsg is divided in 3 layers
- the service layer that implement a service on top of the RPmsg
A parallel could be done between this layer and the Virtio devices such
as the "Virtio-Console".
=> the rpmsg _tty is part of this layer
=> rpmsg_char is another one ( already enabled in some configs)
- the transport layer in charge of the RPmsg protocol
- the back-end layer that is the hardware abstraction layer
- The main back-end used is the RPMsg VirtIO back-end which implements
the RPMSg over VirtIO.
- There are also some platform specific backends (e.g. QCOM, MediaTek)
- We have also some demos that implement the RPMsg protocol on top of a
serial link back-end allowing communication with an external
processor. Not up-streamed yet.
Thanks,
Arnaud
>
> thanks,
>
> greg k-h
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-12-21 9:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 16:11 [PATCH v2] ARM: multi_v7_defconfig: Enable CONFIG_RPMSG_TTY Arnaud Pouliquen
2021-12-20 16:58 ` Greg Kroah-Hartman
2021-12-21 9:05 ` Arnaud POULIQUEN [this message]
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=214788db-6774-5501-bc12-67d3135b50ec@foss.st.com \
--to=arnaud.pouliquen@foss.st.com \
--cc=arnd@arndb.de \
--cc=digetx@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mani@kernel.org \
--cc=treding@nvidia.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).