From: Ohad Ben-Cohen <ohad@wizery.com>
To: Suman Anna <s-anna@ti.com>
Cc: Dave Gerlach <d-gerlach@ti.com>, Robert Tivy <rtivy@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 0/2] couple of generic remoteproc enhancements
Date: Thu, 5 Feb 2015 17:11:14 +0200 [thread overview]
Message-ID: <CAK=WgbYYi+kojNw=CQ0q3iKEkYE7QxUcinCF400OB9PUSXN-fA@mail.gmail.com> (raw)
In-Reply-To: <54D135C7.4040501@ti.com>
Hi Suman,
On Tue, Feb 3, 2015 at 10:55 PM, Suman Anna <s-anna@ti.com> wrote:
> > On 01/09/2015 03:21 PM, Suman Anna wrote:
> >> 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.
> >
> > Any comments on this series, or can I assume that this will make it to
> > v3.20?
>
> ping, want to make sure this has not fallen off your radar..
It has not. I'm a bit swamped so apologies for not taking care of this
faster. I believe I'll get to it next week.
Thanks,
Ohad.
prev parent reply other threads:[~2015-02-05 15:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 21:21 [PATCH v3 0/2] couple of generic remoteproc enhancements Suman Anna
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 [this message]
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='CAK=WgbYYi+kojNw=CQ0q3iKEkYE7QxUcinCF400OB9PUSXN-fA@mail.gmail.com' \
--to=ohad@wizery.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=rtivy@ti.com \
--cc=s-anna@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).