All of lore.kernel.org
 help / color / mirror / Atom feed
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,
	kernel@stlinux.com, patrice.chotard@st.com
Subject: [PATCH v2 0/3] remoteproc: st: add virtio_rpmsg support
Date: Fri, 6 Jan 2017 18:16:10 +0100	[thread overview]
Message-ID: <1483722973-21531-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

Loic Pallardy (3):
  remoteproc: st: add virtio communication support
  remoteproc: st: add da to va support
  remoteproc: core: don't allocate carveout if pa or da are defined

 drivers/remoteproc/Kconfig           |   3 +
 drivers/remoteproc/remoteproc_core.c |   5 ++
 drivers/remoteproc/st_remoteproc.c   | 160 +++++++++++++++++++++++++++++++++--
 3 files changed, 162 insertions(+), 6 deletions(-)

-- 
1.9.1

             reply	other threads:[~2017-01-06 17:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-06 17:16 Loic Pallardy [this message]
2017-01-06 17:16 ` [PATCH v2 1/3] remoteproc: st: add virtio communication support Loic Pallardy
2017-01-16  9:34   ` Lee Jones
2017-01-06 17:16 ` [PATCH v2 2/3] remoteproc: st: add da to va support Loic Pallardy
2017-01-06 17:16 ` [PATCH v2 3/3] remoteproc: core: don't allocate carveout if pa or da are defined Loic Pallardy
2017-01-11 10:19 ` [PATCH v2 0/3] remoteproc: st: add virtio_rpmsg support Patrice Chotard
2017-01-13 13:25   ` 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=1483722973-21531-1-git-send-email-loic.pallardy@st.com \
    --to=loic.pallardy@st.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=kernel@stlinux.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=ohad@wizery.com \
    --cc=patrice.chotard@st.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 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.