devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Simon Horman <horms+renesas@verge.net.au>
Cc: Vinod Koul <vinod.koul@intel.com>,
	dmaengine@vger.kernel.org,
	Linux-sh list <linux-sh@vger.kernel.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 4/6] dmaengine: rcar-dmac: Add device tree bindings documentation
Date: Mon, 4 Aug 2014 10:05:49 +0200	[thread overview]
Message-ID: <CAMuHMdVtU_uujbJarBSdqR2hs5+=KTAxhnOU2tEM4MXaaTTG_A@mail.gmail.com> (raw)
In-Reply-To: <3dc5d31428846326bf122a2a9b402a2a80e97681.1406766014.git.horms+renesas@verge.net.au>

On Thu, Jul 31, 2014 at 2:34 AM, Simon Horman
<horms+renesas@verge.net.au> wrote:
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/dma/renesas,rcar-dmac.txt
> @@ -0,0 +1,98 @@
> +* Renesas R-Car DMA Controller Device Tree bindings
> +
> +Renesas R-Car Generation 2 SoCs have have multiple multi-channel DMA
> +controller instances named DMAC capable of serving multiple clients. Channels
> +can be dedicated to specific clients or shared between a large number of
> +clients.
> +
> +DMA clients are connected to the DMAC ports referenced by an 8-bit identifier
> +called MID/RID.

I think the above sentence can be removed, as it's superseded by the first
sentence of the successive paragraph:

> +
> +Each DMA client is connected to one dedicated port of the DMAC, identified by
> +an 8-bit port number called the MID/RID. A DMA controller can thus serve up to
> +256 clients in total. When the number of hardware channels is lower than the
> +number of clients to be served, channels must be shared between multiple DMA
> +clients. The association of DMA clients to DMAC channels is fully dynamic and
> +not described in these device tree bindings.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2014-08-04  8:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1406766014.git.horms+renesas@verge.net.au>
2014-07-31  0:34 ` [PATCH 4/6] dmaengine: rcar-dmac: Add device tree bindings documentation Simon Horman
2014-08-04  8:05   ` Geert Uytterhoeven [this message]
2014-08-04 14:01     ` Laurent Pinchart
2014-08-05  1:46       ` Simon Horman
2014-08-05 13:33         ` Laurent Pinchart

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='CAMuHMdVtU_uujbJarBSdqR2hs5+=KTAxhnOU2tEM4MXaaTTG_A@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=horms+renesas@verge.net.au \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=vinod.koul@intel.com \
    /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).