From: Loic Pallardy <loic.pallardy@st.com> To: bjorn.andersson@linaro.org, ohad@wizery.com, lee.jones@linaro.org Cc: loic.pallardy@st.com, linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org, kernel@stlinux.com, patrice.chotard@st.com, hugues.fruchet@st.com, peter.griffin@linaro.org Subject: [PATCH v2 0/6] virtio_rpmsg: make rpmsg channel configurable Date: Tue, 31 Jan 2017 13:51:31 +0100 [thread overview] Message-ID: <1485867097-6960-1-git-send-email-loic.pallardy@st.com> (raw) This goal of this series is to offer more flexibility for virtio_rpmsg communication link configuration. It should be possible to tune rpmsg buffer size per Rpmsg link, to provide selected configuration to coprocessor, to take into account coprocessor specificities like memory region. This series introduces an optional virtio rpmsg configuration structure, which will be managed as an extension of struct fw_rsc_vdev present in coprocessor firmware resource table. Structure access is possible thanks to virtio get and set API. This structure contains the different information to tune the link between the host and the coprocessor. Patch "rpmsg: virtio_rpmsg_bus: fix sg_set_buf() when addr is not a valid kernel address" has the same goal as Wendy's RFC [1]. I don't have tested Wendy's series with level driver buffer allocation. Last patch "rpmsg: virtio_rpmsg: set buffer configuration to virtio" has a dependency with remoteproc subdevice boot sequence as coprocessor resource table must be updated before coprocessor start. See [2] [1] http://www.spinics.net/lists/linux-remoteproc/msg00852.html [2] http://www.spinics.net/lists/linux-remoteproc/msg00826.html --- Changes from v1: - No more dependency with [2]. Coprocessor firmware should wait for first kick indicating virtio rpmsg link ready before accessing resource table information. - Correct issues reported by Suman - Fix warnings found by checkpatch with --strict option Loic Pallardy (6): rpmsg: virtio_rpmsg: set rpmsg_buf_size customizable rpmsg: virtio_rpmsg_bus: fix sg_set_buf() when addr is not a valid kernel address include: virtio_rpmsg: add virtio rpmsg configuration structure rpmsg: virtio_rpmsg: get buffer configuration from virtio rpmsg: virtio_rpmsg: don't allocate buffer if provided by low level driver rpmsg: virtio_rpmsg: set buffer configuration to virtio drivers/rpmsg/virtio_rpmsg_bus.c | 176 +++++++++++++++++++++++++++++++------ include/linux/rpmsg/virtio_rpmsg.h | 32 +++++++ 2 files changed, 179 insertions(+), 29 deletions(-) create mode 100644 include/linux/rpmsg/virtio_rpmsg.h -- 1.9.1
WARNING: multiple messages have this Message-ID (diff)
From: Loic Pallardy <loic.pallardy@st.com> To: <bjorn.andersson@linaro.org>, <ohad@wizery.com>, <lee.jones@linaro.org> Cc: <loic.pallardy@st.com>, <linux-remoteproc@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <kernel@stlinux.com>, <patrice.chotard@st.com>, <hugues.fruchet@st.com>, <peter.griffin@linaro.org> Subject: [PATCH v2 0/6] virtio_rpmsg: make rpmsg channel configurable Date: Tue, 31 Jan 2017 13:51:31 +0100 [thread overview] Message-ID: <1485867097-6960-1-git-send-email-loic.pallardy@st.com> (raw) This goal of this series is to offer more flexibility for virtio_rpmsg communication link configuration. It should be possible to tune rpmsg buffer size per Rpmsg link, to provide selected configuration to coprocessor, to take into account coprocessor specificities like memory region. This series introduces an optional virtio rpmsg configuration structure, which will be managed as an extension of struct fw_rsc_vdev present in coprocessor firmware resource table. Structure access is possible thanks to virtio get and set API. This structure contains the different information to tune the link between the host and the coprocessor. Patch "rpmsg: virtio_rpmsg_bus: fix sg_set_buf() when addr is not a valid kernel address" has the same goal as Wendy's RFC [1]. I don't have tested Wendy's series with level driver buffer allocation. Last patch "rpmsg: virtio_rpmsg: set buffer configuration to virtio" has a dependency with remoteproc subdevice boot sequence as coprocessor resource table must be updated before coprocessor start. See [2] [1] http://www.spinics.net/lists/linux-remoteproc/msg00852.html [2] http://www.spinics.net/lists/linux-remoteproc/msg00826.html --- Changes from v1: - No more dependency with [2]. Coprocessor firmware should wait for first kick indicating virtio rpmsg link ready before accessing resource table information. - Correct issues reported by Suman - Fix warnings found by checkpatch with --strict option Loic Pallardy (6): rpmsg: virtio_rpmsg: set rpmsg_buf_size customizable rpmsg: virtio_rpmsg_bus: fix sg_set_buf() when addr is not a valid kernel address include: virtio_rpmsg: add virtio rpmsg configuration structure rpmsg: virtio_rpmsg: get buffer configuration from virtio rpmsg: virtio_rpmsg: don't allocate buffer if provided by low level driver rpmsg: virtio_rpmsg: set buffer configuration to virtio drivers/rpmsg/virtio_rpmsg_bus.c | 176 +++++++++++++++++++++++++++++++------ include/linux/rpmsg/virtio_rpmsg.h | 32 +++++++ 2 files changed, 179 insertions(+), 29 deletions(-) create mode 100644 include/linux/rpmsg/virtio_rpmsg.h -- 1.9.1
next reply other threads:[~2017-01-31 12:51 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-01-31 12:51 Loic Pallardy [this message] 2017-01-31 12:51 ` [PATCH v2 0/6] virtio_rpmsg: make rpmsg channel configurable Loic Pallardy 2017-01-31 12:51 ` [PATCH v2 1/6] rpmsg: virtio_rpmsg: set rpmsg_buf_size customizable Loic Pallardy 2017-01-31 12:51 ` Loic Pallardy 2017-01-31 12:51 ` [PATCH v2 2/6] rpmsg: virtio_rpmsg_bus: fix sg_set_buf() when addr is not a valid kernel address Loic Pallardy 2017-01-31 12:51 ` Loic Pallardy 2017-01-31 12:51 ` [PATCH v2 3/6] include: virtio_rpmsg: add virtio rpmsg configuration structure Loic Pallardy 2017-01-31 12:51 ` Loic Pallardy 2017-01-31 12:51 ` [PATCH v2 4/6] rpmsg: virtio_rpmsg: get buffer configuration from virtio Loic Pallardy 2017-01-31 12:51 ` Loic Pallardy 2017-01-31 12:51 ` [PATCH v2 5/6] rpmsg: virtio_rpmsg: don't allocate buffer if provided by low level driver Loic Pallardy 2017-01-31 12:51 ` Loic Pallardy 2017-01-31 18:29 ` kbuild test robot 2017-01-31 18:29 ` kbuild test robot 2017-01-31 12:51 ` [PATCH v2 6/6] rpmsg: virtio_rpmsg: set buffer configuration to virtio Loic Pallardy 2017-01-31 12:51 ` Loic Pallardy 2017-02-08 10:21 ` [PATCH v2 0/6] virtio_rpmsg: make rpmsg channel configurable Hugues FRUCHET
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=1485867097-6960-1-git-send-email-loic.pallardy@st.com \ --to=loic.pallardy@st.com \ --cc=bjorn.andersson@linaro.org \ --cc=hugues.fruchet@st.com \ --cc=kernel@stlinux.com \ --cc=lee.jones@linaro.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-remoteproc@vger.kernel.org \ --cc=ohad@wizery.com \ --cc=patrice.chotard@st.com \ --cc=peter.griffin@linaro.org \ /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.