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 v4 0/2] remoteproc: st: add virtio_rpmsg support
Date: Wed, 15 Feb 2017 21:18:47 +0100 [thread overview]
Message-ID: <1487189929-24196-1-git-send-email-loic.pallardy@st.com> (raw)
Goal of this series is:
- to add vring based communication link (virtio_rpmsg)
- to add rproc_da_to_va translation function to allow firmware loading in
pre-reserved carveout memory region
V2:
Only changes in patch 1 to:
- fix typos
- fix mailbox allocation per coprocessor
V3:
- Integrate Bjorn's comments about mailbox support simplification
- Add missing Signed-of-by
- Move st_rproc_probe error management correction in a dedicated patch
- Fix warnings reported by checkpatch --strict
V4:
- Rebase on maintainer rproc-next branch on which patches 1 & 2 are present
- Remove check on device address (da) from patch 4
- Add Acked-by and Tested-by
Loic Pallardy (2):
remoteproc: st: add da to va support
remoteproc: core: don't allocate carveout if pa is defined
drivers/remoteproc/remoteproc_core.c | 5 +++++
drivers/remoteproc/st_remoteproc.c | 43 +++++++++++++++++++++++++++++++-----
2 files changed, 42 insertions(+), 6 deletions(-)
--
1.9.1
next reply other threads:[~2017-02-15 20:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 20:18 Loic Pallardy [this message]
2017-02-15 20:18 ` [PATCH v4 1/2] remoteproc: st: add da to va support Loic Pallardy
2017-02-15 20:18 ` [PATCH v4 2/2] remoteproc: core: don't allocate carveout if pa is defined Loic Pallardy
2017-05-03 15:29 ` [PATCH v4 0/2] remoteproc: st: add virtio_rpmsg support Loic Pallardy
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=1487189929-24196-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: 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
all inboxes | Powered by JetHome®