From: Vinod Koul <vinod.koul@intel.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: Abhishek Sahu <absahu@codeaurora.org>,
"andy.gross@linaro.org" <andy.gross@linaro.org>,
"david.brown@linaro.org" <david.brown@linaro.org>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-soc@vger.kernel.org" <linux-soc@vger.kernel.org>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] dmaengine: add DMA_PREP_CMD for non-Data descriptors.
Date: Wed, 2 Aug 2017 10:23:33 +0530 [thread overview]
Message-ID: <20170802045333.GT3053@localhost> (raw)
In-Reply-To: <790ee7c8-a011-431f-e878-636c1e8832fb@intel.com>
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
next prev parent reply other threads:[~2017-08-02 4:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 12:49 [PATCH v2 0/3] Support for QCOM BAM DMA command descriptor Abhishek Sahu
2017-06-26 12:49 ` [PATCH v2 1/3] dmaengine: add DMA_PREP_CMD for non-Data descriptors Abhishek Sahu
2017-07-17 9:24 ` Abhishek Sahu
2017-07-19 10:11 ` Vinod Koul
2017-07-19 12:26 ` Abhishek Sahu
2017-07-19 10:07 ` Vinod Koul
2017-07-19 12:18 ` Abhishek Sahu
2017-07-28 16:08 ` Abhishek Sahu
2017-07-31 12:34 ` Vinod Koul
2017-07-31 13:01 ` Abhishek Sahu
2017-07-31 16:35 ` Dave Jiang
2017-08-02 4:53 ` Vinod Koul [this message]
2017-06-26 12:49 ` [PATCH v2 2/3] dmaengine: qcom: bam_dma: wrapper functions for command descriptor Abhishek Sahu
2017-07-19 10:09 ` Vinod Koul
2017-07-19 11:31 ` Abhishek Sahu
2017-06-26 12:49 ` [PATCH v2 3/3] dmaengine: qcom: bam_dma: add command descriptor flag Abhishek Sahu
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=20170802045333.GT3053@localhost \
--to=vinod.koul@intel.com \
--cc=absahu@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=david.brown@linaro.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).