Re: [PATCH v3 0/2] couple of generic remoteproc enhancements

From: Suman Anna
Date: Tue Feb 03 2015 - 15:56:07 EST


Ohad,

> 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..

>
> 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(-)
>>
>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/