From: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
Ohad Ben-Cohen <ohad@wizery.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: <linux-remoteproc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<arnaud.pouliquen@foss.st.com>
Subject: [PATCH v2 0/1] rpmsg: ctrl: Add ability to instantiate rpmsg device locally
Date: Mon, 21 Jun 2021 14:57:59 +0200 [thread overview]
Message-ID: <20210621125800.27696-1-arnaud.pouliquen@foss.st.com> (raw)
Purpose:
Allow the user space application to create and release an rpmsg device by adding
rpmsg ioctrl to the /dev/rpmsg_ctrl interface
Aim:
The current implementation is based on the enumeration of services by the
remote processor to create a new channel and instantiate associated rpmsg device.
There is no solution to create a rpmsg channel on user application request.
If the rpmsg char driver allows adding a new endpoint over an existing channel, it
does not offer the ability to create a new one.
Adding the IOCTRL to instantiate rpmsg channels from the user application will allow
to dynamically create and destroy rpmsg devices. Some examples of use are:
- activate the service at the initiative of the application,
- remove the communication on a specific channel before entering the suspend mode,
- creating a temporary channel for debugging purposes.
Delta vs V1 [1]
- Squah patches 1/4(rpmsg: ctrl: Introduce RPMSG_CREATE_DEV_IOCTL) and
2/4 (rpmsg: ctrl: Introduce RPMSG_RELEASE_DEV_IOCTL).
- Remove the rpmsg device attribue to check if a rpmg device can be released, choose to trust
the application (a similar trust already exists for the bind/unbind interface).
[1] https://patchwork.kernel.org/project/linux-remoteproc/list/?series=494021
How to test it:
- This series can be applied on git/andersson/remoteproc.git for-next branch (dc0e14fa833b)
+ the "Restructure the rpmsg char to decorrelate the control part" series[2]
- to test the ioctrl, a rpmsgexportdev tool is available here:
https://github.com/arnopo/rpmsgexport
[2]https://patchwork.kernel.org/project/linux-remoteproc/list/?series=483793
Arnaud Pouliquen (1):
rpmsg: ctrl: Introduce new RPMSG_CREATE/RELEASE_DEV_IOCTL controls
drivers/rpmsg/rpmsg_ctrl.c | 37 +++++++++++++++++++++++++++++++++----
include/uapi/linux/rpmsg.h | 10 ++++++++++
2 files changed, 43 insertions(+), 4 deletions(-)
--
2.17.1
next reply other threads:[~2021-06-21 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 12:57 Arnaud Pouliquen [this message]
2021-06-21 12:58 ` [PATCH v2 1/1] rpmsg: ctrl: Introduce new RPMSG_CREATE/RELEASE_DEV_IOCTL controls Arnaud Pouliquen
2021-06-21 23:16 ` Mathieu Poirier
2021-06-22 7:43 ` Arnaud POULIQUEN
2021-06-22 19:56 ` Mathieu Poirier
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=20210621125800.27696-1-arnaud.pouliquen@foss.st.com \
--to=arnaud.pouliquen@foss.st.com \
--cc=bjorn.andersson@linaro.org \
--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 \
/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).