From: Suman Anna <s-anna@ti.com>
To: Ohad Ben-Cohen <ohad@wizery.com>
Cc: Dave Gerlach <d-gerlach@ti.com>, Robert Tivy <rtivy@ti.com>,
<linux-kernel@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Suman Anna <s-anna@ti.com>
Subject: [PATCH v3 0/2] couple of generic remoteproc enhancements
Date: Fri, 9 Jan 2015 15:21:57 -0600 [thread overview]
Message-ID: <1420838519-15669-1-git-send-email-s-anna@ti.com> (raw)
Hi Ohad,
The following is an updated patchset addressing the previous pending comments
from v1 & v2, and are rebased onto the latest 3.19-rc3 (are rc independent
actually).
The patches are mainly developed to support the WkupM3 remote processor driver
on TI AM335x/AM437x SoCs, and I have verified the loading using the latest
version of Dave's WkupM3 remoteproc work [1]
The only change in v3 is on the second patch, it mainly leverages the
memcpy_toio and memset_io functions for copying/loading code into the
internal memory sections. An additional argument has to be added to the
rproc_da_to_va function to make this distinction.
regards
Suman
[1] http://marc.info/?l=linux-omap&m=142022842323885&w=2
v2:
http://marc.info/?l=linux-omap&m=141089879412807&w=2
- Add explicit setting of the .has_iommu field in each of the existing
remoteproc platform drivers
- Update patch description to add the usecase details for the change
summary
- Fixed a minor checkpatch warning.
v1:
http://marc.info/?l=linux-omap&m=140483657604924&w=2
Suman Anna (2):
remoteproc: use a flag to detect the presence of IOMMU
remoteproc: add support to handle internal memories
drivers/remoteproc/da8xx_remoteproc.c | 1 +
drivers/remoteproc/omap_remoteproc.c | 5 ++
drivers/remoteproc/remoteproc_core.c | 104 ++++++++++++++++++++++++-----
drivers/remoteproc/remoteproc_elf_loader.c | 23 +++++--
drivers/remoteproc/remoteproc_internal.h | 6 +-
drivers/remoteproc/ste_modem_rproc.c | 1 +
include/linux/remoteproc.h | 45 ++++++++++++-
7 files changed, 161 insertions(+), 24 deletions(-)
--
2.2.1
next reply other threads:[~2015-01-09 21:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 21:21 Suman Anna [this message]
2015-01-09 21:21 ` [PATCH v3 1/2] remoteproc: use a flag to detect the presence of IOMMU Suman Anna
2015-03-12 9:04 ` Ohad Ben-Cohen
2015-03-13 23:35 ` Suman Anna
2015-01-09 21:21 ` [PATCH v3 2/2] remoteproc: add support to handle internal memories Suman Anna
2015-02-10 10:10 ` Ohad Ben-Cohen
2015-02-11 20:57 ` Tony Lindgren
2015-02-11 22:28 ` Suman Anna
2015-02-11 22:48 ` Tony Lindgren
2015-02-12 0:01 ` Suman Anna
2015-02-12 0:18 ` Tony Lindgren
2015-02-12 1:07 ` Suman Anna
2015-02-12 9:09 ` Ohad Ben-Cohen
2015-02-12 20:54 ` Suman Anna
2015-02-13 5:20 ` Ohad Ben-Cohen
2015-02-13 16:13 ` Suman Anna
2015-02-13 18:35 ` Tony Lindgren
2015-01-22 21:52 ` [PATCH v3 0/2] couple of generic remoteproc enhancements Suman Anna
2015-02-03 20:55 ` Suman Anna
2015-02-05 15:11 ` Ohad Ben-Cohen
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=1420838519-15669-1-git-send-email-s-anna@ti.com \
--to=s-anna@ti.com \
--cc=d-gerlach@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=rtivy@ti.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;
as well as URLs for NNTP newsgroup(s).