On Wed, Nov 16, 2016 at 12:08 PM, Andy Shevchenko
wrote:
> On Wed, 2016-11-16 at 17:01 +, Eugeniy Paltsev wrote:
>> On Wed, 2016-11-16 at 17:10 +0200, Andy Shevchenko wrote:
>> > Overall, since we are going to expose some properties to the Device
>> > Tree
>> > I would really think twice about
On Wed, 2016-11-16 at 17:01 +, Eugeniy Paltsev wrote:
> On Wed, 2016-11-16 at 17:10 +0200, Andy Shevchenko wrote:
> > Overall, since we are going to expose some properties to the Device
> > Tree
> > I would really think twice about naming. Better if we reuse
> > something
> > existing already.
Hi Andy,
On Wed, 2016-11-16 at 17:10 +0200, Andy Shevchenko wrote:
> Overall, since we are going to expose some properties to the Device
> Tree
> I would really think twice about naming. Better if we reuse something
> existing already.
>
> So, what I can see is
>
> dmacap,private
> dmacap,memcpy
On Wed, 2016-11-16 at 16:56 +0300, Eugeniy Paltsev wrote:
> * Rename is_private to is-private as ordered by DT policy.
> The change leaves the support for the old format.
>
> * Add is-memcpu property, so it is possible to
> enable memory-to-memory transfers support via DT.
>
> * Add hw-llp p
* Rename is_private to is-private as ordered by DT policy.
The change leaves the support for the old format.
* Add is-memcpu property, so it is possible to
enable memory-to-memory transfers support via DT.
* Add hw-llp property, so it is possible to enable
hardware multi block transfers sup
