[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170802045333.GT3053@localhost>
Date: Wed, 2 Aug 2017 10:23:33 +0530
From: Vinod Koul <vinod.koul@...el.com>
To: Dave Jiang <dave.jiang@...el.com>
Cc: Abhishek Sahu <absahu@...eaurora.org>,
"andy.gross@...aro.org" <andy.gross@...aro.org>,
"david.brown@...aro.org" <david.brown@...aro.org>,
"Williams, Dan J" <dan.j.williams@...el.com>,
"linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>,
"linux-soc@...r.kernel.org" <linux-soc@...r.kernel.org>,
"dmaengine@...r.kernel.org" <dmaengine@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 1/3] dmaengine: add DMA_PREP_CMD for non-Data
descriptors.
On Mon, Jul 31, 2017 at 09:35:53AM -0700, Dave Jiang wrote:
> On 07/31/2017 05:34 AM, Vinod Koul wrote:
> >
> > Are you asking for using DMA_PREP_CMD, for that I think should be ok
> >
> > If you asking about adding a new flag with DMA_PREP_CMD, then it would no
>
> Vinod, I wonder if we should introduce a DMA_PREP_CUSTOM flag and then
> reserve X number of upper flag bits to vendor specified that only they
> care about. That way they can define whatever they want in the upper
> bits if they need it.
Nah, that just leads to abuse :( So lets keep adding the flags generically
as and when we need them..
--
~Vinod
Powered by blists - more mailing lists