On Fri, Feb 3, 2017 at 5:35 PM, Jassi Brar wrote:
> On Thu, Feb 2, 2017 at 10:17 AM, Anup Patel wrote:
>> The remote processor can have DMAENGINE capabilities and client
>> can pass data to be processed via main memory. In such cases,
>> the
On Fri, Feb 3, 2017 at 5:35 PM, Jassi Brar wrote:
> On Thu, Feb 2, 2017 at 10:17 AM, Anup Patel wrote:
>> The remote processor can have DMAENGINE capabilities and client
>> can pass data to be processed via main memory. In such cases,
>> the client will require DMAble memory for remote
On Thu, Feb 2, 2017 at 10:17 AM, Anup Patel wrote:
> The remote processor can have DMAENGINE capabilities and client
> can pass data to be processed via main memory. In such cases,
> the client will require DMAble memory for remote processor.
>
> This patch adds new API
On Thu, Feb 2, 2017 at 10:17 AM, Anup Patel wrote:
> The remote processor can have DMAENGINE capabilities and client
> can pass data to be processed via main memory. In such cases,
> the client will require DMAble memory for remote processor.
>
> This patch adds new API mbox_channel_device()
The remote processor can have DMAENGINE capabilities and client
can pass data to be processed via main memory. In such cases,
the client will require DMAble memory for remote processor.
This patch adds new API mbox_channel_device() which can be
used by clients to get struct device pointer of
The remote processor can have DMAENGINE capabilities and client
can pass data to be processed via main memory. In such cases,
the client will require DMAble memory for remote processor.
This patch adds new API mbox_channel_device() which can be
used by clients to get struct device pointer of
6 matches
Mail list logo