linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: agross@codeaurora.org (Andy Gross)
To: linux-arm-kernel@lists.infradead.org
Subject: [Patch v2 2/2] dt/bindings: qcom_adm: Fix channel specificers
Date: Thu, 8 Jan 2015 11:19:46 -0600	[thread overview]
Message-ID: <20150108171946.GA15842@qualcomm.com> (raw)
In-Reply-To: <54AEAFB6.9050609@codeaurora.org>

On Thu, Jan 08, 2015 at 11:26:30AM -0500, Christopher Covington wrote:

<snip>

> > +DMA clients must use the format descripted in the dma.txt file, using a two
> >  cell specifier for each channel.
> >  
> >  Each dmas request consists of 3 cells:
> 
> Now 2 cells?

Good catch.  I'll fix in next rev.  Thanks!

> >   1. phandle pointing to the DMA controller
> >   2. channel number
> > - 3. CRCI assignment, if applicable.  If no CRCI flow control is required, use 0.
> > -    The CRCI is used for flow control.  It identifies the peripheral device that
> > -    is the source/destination for the transferred data.
> >  

<snip>

-- 
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

      reply	other threads:[~2015-01-08 17:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08  3:26 [Patch v2 0/2] Add Qualcomm ADM dmaengine driver Andy Gross
2015-01-08  3:26 ` [Patch v2 1/2] dmaengine: Add ADM driver Andy Gross
2015-01-08  3:36   ` Andy Gross
2015-01-09  4:38   ` Archit Taneja
2015-01-09 17:08     ` Andy Gross
2015-01-30 11:47   ` Pramod Gurav
2015-02-11  5:20     ` Andy Gross
2015-01-08  3:26 ` [Patch v2 2/2] dt/bindings: qcom_adm: Fix channel specificers Andy Gross
2015-01-08 16:26   ` Christopher Covington
2015-01-08 17:19     ` Andy Gross [this message]

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=20150108171946.GA15842@qualcomm.com \
    --to=agross@codeaurora.org \
    --cc=linux-arm-kernel@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 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).