From: Eugeniy.Paltsev@synopsys.com (Eugeniy Paltsev)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH 4/4] Update device tree Synopsys DW DMAC documentation
Date: Wed, 16 Nov 2016 17:01:23 +0000 [thread overview]
Message-ID: <1479315682.2534.20.camel@synopsys.com> (raw)
In-Reply-To: <1479309042.24056.40.camel@linux.intel.com>
Hi?Andy,
On Wed, 2016-11-16@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.
I agree with other comments.
--
?Paltsev Eugeniy
WARNING: multiple messages have this Message-ID (diff)
From: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
To: "andriy.shevchenko@linux.intel.com" <andriy.shevchenko@linux.intel.com>
Cc: "vinod.koul@intel.com" <vinod.koul@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Eugeniy.Paltsev@synopsys.com" <Eugeniy.Paltsev@synopsys.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>
Subject: Re: [PATCH 4/4] Update device tree Synopsys DW DMAC documentation
Date: Wed, 16 Nov 2016 17:01:23 +0000 [thread overview]
Message-ID: <1479315682.2534.20.camel@synopsys.com> (raw)
In-Reply-To: <1479309042.24056.40.camel@linux.intel.com>
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
>
> 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.
I agree with other comments.
--
Paltsev Eugeniy
next prev parent reply other threads:[~2016-11-16 17:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 13:56 [PATCH 0/4] DW DMAC: update device tree Eugeniy Paltsev
2016-11-16 13:56 ` Eugeniy Paltsev
2016-11-16 13:56 ` Eugeniy Paltsev
2016-11-16 13:56 ` [PATCH 1/4] DW DMAC: rename is_private property as ordered by DT policy Eugeniy Paltsev
2016-11-16 13:56 ` Eugeniy Paltsev
2016-11-16 15:11 ` Andy Shevchenko
2016-11-16 15:11 ` Andy Shevchenko
2016-11-16 15:11 ` Andy Shevchenko
2016-11-16 13:56 ` [PATCH 2/4] DW DMAC: add is-memcpu property to device tree Eugeniy Paltsev
2016-11-16 13:56 ` Eugeniy Paltsev
2016-11-16 15:12 ` Andy Shevchenko
2016-11-16 15:12 ` Andy Shevchenko
2016-11-16 13:56 ` [PATCH 3/4] DW DMAC: add hw-llp " Eugeniy Paltsev
2016-11-16 13:56 ` Eugeniy Paltsev
2016-11-16 15:13 ` Andy Shevchenko
2016-11-16 15:13 ` Andy Shevchenko
2016-11-16 15:13 ` Andy Shevchenko
2016-11-16 13:56 ` [PATCH 4/4] Update device tree Synopsys DW DMAC documentation Eugeniy Paltsev
2016-11-16 13:56 ` Eugeniy Paltsev
2016-11-16 15:10 ` Andy Shevchenko
2016-11-16 15:10 ` Andy Shevchenko
2016-11-16 15:10 ` Andy Shevchenko
2016-11-16 17:01 ` Eugeniy Paltsev [this message]
2016-11-16 17:01 ` Eugeniy Paltsev
2016-11-16 18:08 ` Andy Shevchenko
2016-11-16 18:08 ` Andy Shevchenko
2016-11-16 18:14 ` Rob Herring
2016-11-16 18:14 ` Rob Herring
2016-11-16 15:18 ` [PATCH 0/4] DW DMAC: update device tree Andy Shevchenko
2016-11-16 15:18 ` Andy Shevchenko
2016-11-16 15:18 ` Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1479315682.2534.20.camel@synopsys.com \
--to=eugeniy.paltsev@synopsys.com \
--cc=linux-snps-arc@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.