From: Yuan Yao <yao.yuan@freescale.com>
To: wsa@the-dreams.de, marex@denx.de
Cc: mark.rutland@arm.com, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org, fugang.duan@freescale.com,
shawn.guo@linaro.org, linux-arm-kernel@lists.infradead.org,
LW@KARO-electronics.de
Subject: [PATCH v7 2/2] Documentation:add DMA support for freescale i2c driver
Date: Wed, 13 Aug 2014 17:46:55 +0800 [thread overview]
Message-ID: <1407923215-3749-3-git-send-email-yao.yuan@freescale.com> (raw)
In-Reply-To: <1407923215-3749-1-git-send-email-yao.yuan@freescale.com>
Add i2c dts node properties for eDMA support, them depend on the eDMA driver.
Signed-off-by: Yuan Yao <yao.yuan@freescale.com>
---
Documentation/devicetree/bindings/i2c/i2c-imx.txt | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/Documentation/devicetree/bindings/i2c/i2c-imx.txt b/Documentation/devicetree/bindings/i2c/i2c-imx.txt
index 4a8513e..52d37fd 100644
--- a/Documentation/devicetree/bindings/i2c/i2c-imx.txt
+++ b/Documentation/devicetree/bindings/i2c/i2c-imx.txt
@@ -11,6 +11,8 @@ Required properties:
Optional properties:
- clock-frequency : Constains desired I2C/HS-I2C bus clock frequency in Hz.
The absence of the propoerty indicates the default frequency 100 kHz.
+- dmas: A list of two dma specifiers, one for each entry in dma-names.
+- dma-names: should contain "tx" and "rx".
Examples:
@@ -26,3 +28,12 @@ i2c@70038000 { /* HS-I2C on i.MX51 */
interrupts = <64>;
clock-frequency = <400000>;
};
+
+i2c0: i2c@40066000 { /* i2c0 on vf610 */
+ compatible = "fsl,vf610-i2c";
+ reg = <0x40066000 0x1000>;
+ interrupts =<0 71 0x04>;
+ dmas = <&edma0 0 50>,
+ <&edma0 0 51>;
+ dma-names = "rx","tx";
+};
--
1.8.4
next prev parent reply other threads:[~2014-08-13 9:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 9:46 [PATCH v7 0/2] i2c: imx: add DMA support for freescale i2c driver Yuan Yao
[not found] ` <1407923215-3749-1-git-send-email-yao.yuan-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-08-13 9:46 ` [PATCH v7 1/2] " Yuan Yao
[not found] ` <1407923215-3749-2-git-send-email-yao.yuan-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-09-04 3:38 ` Yao Yuan
2014-09-04 14:38 ` Marek Vasut
2014-09-05 10:32 ` Yao Yuan
[not found] ` <c10c1960255e4dbca2a281b995290c6d-AZ66ij2kwaZYLYlmg7qx2OO6mTEJWrR4XA4E9RH9d+qIuWR1G4zioA@public.gmane.org>
2014-09-05 10:40 ` Marek Vasut
2014-09-10 14:48 ` Yao Yuan
2014-09-16 18:17 ` Marek Vasut
2014-09-17 14:50 ` Yao Yuan
[not found] ` <1410965416759.91038-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-09-17 19:14 ` Marek Vasut
[not found] ` <201409172114.36617.marex-ynQEQJNshbs@public.gmane.org>
2014-09-18 15:46 ` Yao Yuan
[not found] ` <1411055145666.72178-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-09-19 12:15 ` Marek Vasut
2014-08-13 9:46 ` Yuan Yao [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-13 9:37 Yuan Yao
[not found] ` <1407922676-31438-2-git-send-email-yao.yuan-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-08-13 9:37 ` [PATCH v7 2/2] Documentation:add " Yuan Yao
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=1407923215-3749-3-git-send-email-yao.yuan@freescale.com \
--to=yao.yuan@freescale.com \
--cc=LW@KARO-electronics.de \
--cc=fugang.duan@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=mark.rutland@arm.com \
--cc=shawn.guo@linaro.org \
--cc=wsa@the-dreams.de \
/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).