mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Suman Anna <s-anna@ti.com>
To: Wendy Liang <wendy.liang@xilinx.com>, <bjorn.andersson@linaro.org>
Cc: <linux-remoteproc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, Wendy Liang <jliang@xilinx.com>
Subject: Re: [RFC LINUX PATCH 0/3] Allow remote to specify shared memory
Date: Mon, 27 Mar 2017 10:54:44 -0500	[thread overview]
Message-ID: <df420852-6b5a-a2fc-4c4c-8556b9985e29@ti.com> (raw)
In-Reply-To: <1490383336-23117-1-git-send-email-jliang@xilinx.com>

Hi Wendy,

On 03/24/2017 02:22 PM, Wendy Liang wrote:
> This patch enables the remoteproc to specify the shared memory.
> Remoteproc declared this memory as DMA memory.
> It can be used for virtio, or shared buffers.

You should be able to achieve this without any remoteproc core changes.
You can do this by defining a reserved-memory node in your DTS file (can
be a CMA pool or a DMA pool), assigning the node using memory-region in
your remoteproc DT node and using the function,
of_reserved_mem_device_init() in your remoteproc driver.

regards
Suman

> 
> Wendy Liang (3):
>   remoteproc: add rproc mem resource entry
>   remoteproc: add rproc_mem resource entry handler
>   remoteproc: Release DMA declare mem when cleanup rsc
> 
>  drivers/remoteproc/remoteproc_core.c | 40 ++++++++++++++++++++++++++++++++++++
>  include/linux/remoteproc.h           | 23 ++++++++++++++++++++-
>  2 files changed, 62 insertions(+), 1 deletion(-)
> 

  parent reply	other threads:[~2017-03-27 16:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-24 19:22 Wendy Liang
2017-03-24 19:22 ` [RFC LINUX PATCH 1/3] remoteproc: add rproc mem resource entry Wendy Liang
2017-03-24 19:22 ` [RFC LINUX PATCH 2/3] remoteproc: add rproc_mem resource entry handler Wendy Liang
2017-03-24 19:22 ` [RFC LINUX PATCH 3/3] remoteproc: Release DMA declare mem when cleanup rsc Wendy Liang
2017-03-27 15:54 ` Suman Anna [this message]
2017-03-28 18:52   ` [RFC LINUX PATCH 0/3] Allow remote to specify shared memory Wendy Liang
2017-03-28 23:24     ` Suman Anna
2017-03-29 16:41       ` Jiaying Liang
2017-03-29 18:56         ` Loic PALLARDY
2017-03-30 17:39           ` Jiaying Liang

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=df420852-6b5a-a2fc-4c4c-8556b9985e29@ti.com \
    --to=s-anna@ti.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=jliang@xilinx.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=wendy.liang@xilinx.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

all inboxes | Powered by JetHome®