From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dt/documentation: add specification of dma bus information
Date: Mon, 9 Jun 2014 10:06:12 +0800 [thread overview]
Message-ID: <20140609020611.GW8860@dragon> (raw)
In-Reply-To: <1401981720-6946-1-git-send-email-santosh.shilimkar@ti.com>
On Thu, Jun 05, 2014 at 11:22:00AM -0400, Santosh Shilimkar wrote:
> Recently we introduced the generic device tree infrastructure for couple of DMA
> bus parameter, dma-ranges and dma-coherent. Update the documentation so that
> its useful for future users.
>
> The "dma-ranges" property is intended to be used for describing the
> configuration of DMA bus RAM addresses and its offset w.r.t CPU addresses.
>
> The "dma-coherent" property is intended to be used for identifying devices
> supported coherent DMA operations.
>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: Grant Likely <grant.likely@linaro.org>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Pawel Moll <pawel.moll@arm.com>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Ian Campbell <ijc+devicetree@hellion.org.uk>
> Cc: Shawn Guo <shawn.guo@freescale.com>
> Cc: Kumar Gala <galak@codeaurora.org>
> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Thanks for the documentation. I think it's definitely useful for future
users of the binding.
Acked-by: Shawn Guo <shawn.guo@freescale.com>
next prev parent reply other threads:[~2014-06-09 2:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 15:22 [PATCH] dt/documentation: add specification of dma bus information Santosh Shilimkar
2014-06-09 2:06 ` Shawn Guo [this message]
2014-06-09 2:13 ` Fabio Estevam
2014-06-09 13:59 ` Santosh Shilimkar
2014-06-20 15:04 ` Santosh Shilimkar
2014-06-20 15:50 ` Rob Herring
2014-06-20 17:17 ` Santosh Shilimkar
2014-06-20 18:56 ` Arnd Bergmann
2014-06-20 19:02 ` Santosh Shilimkar
2014-06-20 19:46 ` Rob Herring
2014-06-22 19:40 ` Santosh Shilimkar
2014-09-19 18:29 ` Grygorii Strashko
2014-09-26 16:32 ` Rob Herring
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=20140609020611.GW8860@dragon \
--to=shawn.guo@freescale.com \
--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).