From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Andy Gross <agross@kernel.org>,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 0/6] rpmsg: enable the use of the rpmsg_char device for the Virtio backend
Date: Thu, 11 Mar 2021 17:38:01 -0600 [thread overview]
Message-ID: <YEqp2US8OykaUAa/@builder.lan> (raw)
In-Reply-To: <20210311140413.31725-1-arnaud.pouliquen@foss.st.com>
On Thu 11 Mar 08:04 CST 2021, Arnaud Pouliquen wrote:
> This series is the first step in the division of the series:
> "Introduce a generic IOCTL interface for RPMsg channels management"[1]
>
> The main goal here is to enable the RPMsg char interface for
> the virtio RPMsg backend.
>
> In addition some patches have been includes in order to document the
> interface and rename the rpmsg_char_init function.
>
> It also includes Mathieu Poirier's comments made on [1]
>
> Patchsets that should be the next steps:
> - Extract the control part of the char dev and create the rpmsg_ctrl.c
> file
> - Introduce the RPMSG_CREATE_DEV_IOCTL IOCTL to instantiate RPMsg devices
>
>
> [1]: https://patchwork.kernel.org/project/linux-remoteproc/list/?series=435523
>
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Regards,
Bjorn
> Arnaud Pouliquen (6):
> rpmsg: char: Rename rpmsg_char_init to rpmsg_chrdev_init
> rpmsg: Move RPMSG_ADDR_ANY in user API
> rpmsg: Add short description of the IOCTL defined in UAPI.
> rpmsg: char: Use rpmsg_sendto to specify the message destination
> address
> rpmsg: virtio: Register the rpmsg_char device
> rpmsg: char: Return an error if device already open
>
> drivers/rpmsg/qcom_glink_native.c | 16 ++++++++
> drivers/rpmsg/qcom_smd.c | 16 ++++++++
> drivers/rpmsg/rpmsg_char.c | 11 ++++--
> drivers/rpmsg/virtio_rpmsg_bus.c | 62 ++++++++++++++++++++++++++++---
> include/linux/rpmsg.h | 3 +-
> include/uapi/linux/rpmsg.h | 13 ++++++-
> 6 files changed, 108 insertions(+), 13 deletions(-)
>
> --
> 2.17.1
>
next prev parent reply other threads:[~2021-03-11 23:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 14:04 [PATCH 0/6] rpmsg: enable the use of the rpmsg_char device for the Virtio backend Arnaud Pouliquen
2021-03-11 14:04 ` [PATCH 1/6] rpmsg: char: Rename rpmsg_char_init to rpmsg_chrdev_init Arnaud Pouliquen
2021-03-11 14:04 ` [PATCH 2/6] rpmsg: Move RPMSG_ADDR_ANY in user API Arnaud Pouliquen
2021-03-11 14:04 ` [PATCH 3/6] rpmsg: Add short description of the IOCTL defined in UAPI Arnaud Pouliquen
2021-03-11 14:04 ` [PATCH 4/6] rpmsg: char: Use rpmsg_sendto to specify the message destination address Arnaud Pouliquen
2021-03-11 14:04 ` [PATCH 5/6] rpmsg: virtio: Register the rpmsg_char device Arnaud Pouliquen
2021-03-11 14:04 ` [PATCH 6/6] rpmsg: char: Return an error if device already open Arnaud Pouliquen
2021-03-11 23:38 ` Bjorn Andersson [this message]
2021-03-15 16:16 ` [PATCH 0/6] rpmsg: enable the use of the rpmsg_char device for the Virtio backend Mathieu Poirier
2021-03-18 13:10 ` patchwork-bot+linux-remoteproc
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=YEqp2US8OykaUAa/@builder.lan \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=arnaud.pouliquen@foss.st.com \
--cc=linux-arm-msm@vger.kernel.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