Hi Roger,
On 12/4/18 4:03 AM, Roger Quadros wrote:
> On 29/11/18 18:12, David Lechner wrote:
>> On 11/29/18 4:29 AM, Roger Quadros wrote:
>>> Bjorn, Suman,
>>>
>>> On 26/11/18 23:29, David Lechner wrote:
On 11/26/18 1:52 AM, Roger Quadros wrote:
> From: Suman Anna
>
> The rproc_d
On 29/11/18 18:12, David Lechner wrote:
> On 11/29/18 4:29 AM, Roger Quadros wrote:
>> Bjorn, Suman,
>>
>> On 26/11/18 23:29, David Lechner wrote:
>>> On 11/26/18 1:52 AM, Roger Quadros wrote:
From: Suman Anna
The rproc_da_to_va() API is currently used to perform any device
to
On 11/29/18 4:29 AM, Roger Quadros wrote:
Bjorn, Suman,
On 26/11/18 23:29, David Lechner wrote:
On 11/26/18 1:52 AM, Roger Quadros wrote:
From: Suman Anna
The rproc_da_to_va() API is currently used to perform any device
to kernel address translations to meet the different needs of the
remote
Bjorn, Suman,
On 26/11/18 23:29, David Lechner wrote:
> On 11/26/18 1:52 AM, Roger Quadros wrote:
>> From: Suman Anna
>>
>> The rproc_da_to_va() API is currently used to perform any device
>> to kernel address translations to meet the different needs of the
>> remoteproc core/platform drivers (eg
On 11/26/18 1:52 AM, Roger Quadros wrote:
From: Suman Anna
The rproc_da_to_va() API is currently used to perform any device
to kernel address translations to meet the different needs of the
remoteproc core/platform drivers (eg: loading). The function also
invokes the da_to_va ops, if present, t
5 matches
Mail list logo