[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1479319704.22212.0.camel@linux.intel.com>
Date: Wed, 16 Nov 2016 20:08:24 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Eugeniy Paltsev <Eugeniy.Paltsev@...opsys.com>
Cc: "vinod.koul@...el.com" <vinod.koul@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-snps-arc@...ts.infradead.org"
<linux-snps-arc@...ts.infradead.org>,
"mark.rutland@....com" <mark.rutland@....com>,
"dmaengine@...r.kernel.org" <dmaengine@...r.kernel.org>
Subject: Re: [PATCH 4/4] Update device tree Synopsys DW DMAC documentation
On Wed, 2016-11-16 at 17:01 +0000, 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.
> >
> > So, what I can see is
> >
> > dmacap,private
> > dmacap,memcpy
> >
> > Here is a selling point as well, i.e. standardization.
> >
>
> As I can see these property name used only in "mv_xor" driver. AndĀ
> they are marked asĀ deprecated.
> So, I'm not sure if I should used these names.
Oh, good catch! So, then I leave this to DT experienced guys to decide.
Rob?
--
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Intel Finland Oy
Powered by blists - more mailing lists