[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1547128251-44137-1-git-send-email-loic.pallardy@st.com>
Date: Thu, 10 Jan 2019 14:50:48 +0100
From: Loic Pallardy <loic.pallardy@...com>
To: <bjorn.andersson@...aro.org>, <ohad@...ery.com>
CC: <linux-remoteproc@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<arnaud.pouliquen@...com>, <benjamin.gaignard@...aro.org>,
<s-anna@...com>, Loic Pallardy <loic.pallardy@...com>
Subject: [PATCH v2 0/3] remoteproc: complete fixed memory region support
This new series corresponds to the remaining patches from [1]
addressing fixed memory region support for remote processor.
The three remaining patches allow to:
- assign a specific memory region to vdev sub device. As all virtio based
services are using virtio device parent for memory allocation, I propose to
keep a dedicated vdev device per virtio link for memory allocation. A second
step will be to used virtio device itself.
- migrate ST driver on new memory carveout management
- allocate virtio rpmsg buffer from parent device
Regards,
Loic
[1] https://lkml.org/lkml/2018/7/27/612
---
Changes from V1:
- rebase on kernel v5.0-rc0
- correct error management for device registering
Loic Pallardy (3):
remoteproc: create vdev subdevice with specific dma memory pool
remoteproc: st: add reserved memory support
rpmsg: virtio: allocate buffer from parent
drivers/remoteproc/remoteproc_core.c | 47 +++++++++++++++--
drivers/remoteproc/remoteproc_internal.h | 1 +
drivers/remoteproc/remoteproc_virtio.c | 42 ++++++++++++++-
drivers/remoteproc/st_remoteproc.c | 91 ++++++++++++++++++++++++++++----
drivers/rpmsg/virtio_rpmsg_bus.c | 6 +--
include/linux/remoteproc.h | 1 +
6 files changed, 170 insertions(+), 18 deletions(-)
--
2.7.4
Powered by blists - more mailing lists