From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-i2c@vger.kernel.org, linux-sh@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
Simon Horman <horms@verge.net.au>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [RFC 3/3] ARM: shmobile: r8a7791: add DMA nodes for IIC
Date: Sun, 02 Nov 2014 21:47:46 +0000 [thread overview]
Message-ID: <17049901.fYZShuhnQA@avalon> (raw)
In-Reply-To: <1414752678-26078-4-git-send-email-wsa@the-dreams.de>
Hi Wolfram,
Thank you for the patch.
On Friday 31 October 2014 11:51:18 Wolfram Sang wrote:
> From: Wolfram Sang <wsa+renesas@sang-engineering.com>
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
> arch/arm/boot/dts/r8a7791.dtsi | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/arch/arm/boot/dts/r8a7791.dtsi b/arch/arm/boot/dts/r8a7791.dtsi
> index 9a57215f54f7..213b6bda6201 100644
> --- a/arch/arm/boot/dts/r8a7791.dtsi
> +++ b/arch/arm/boot/dts/r8a7791.dtsi
> @@ -371,6 +371,8 @@
> reg = <0 0xe60b0000 0 0x425>;
> interrupts = <0 173 IRQ_TYPE_LEVEL_HIGH>;
> clocks = <&mstp9_clks R8A7791_CLK_IICDVFS>;
> + dmas = <&dmac0 0x77>, <&dmac0 0x78>;
> + dma-names = "tx", "rx";
> status = "disabled";
> };
>
> @@ -381,6 +383,8 @@
> reg = <0 0xe6500000 0 0x425>;
> interrupts = <0 174 IRQ_TYPE_LEVEL_HIGH>;
> clocks = <&mstp3_clks R8A7791_CLK_IIC0>;
> + dmas = <&dmac0 0x61>, <&dmac0 0x62>;
> + dma-names = "tx", "rx";
> status = "disabled";
> };
>
> @@ -391,6 +395,8 @@
> reg = <0 0xe6510000 0 0x425>;
> interrupts = <0 175 IRQ_TYPE_LEVEL_HIGH>;
> clocks = <&mstp3_clks R8A7791_CLK_IIC1>;
> + dmas = <&dmac0 0x65>, <&dmac0 0x66>;
> + dma-names = "tx", "rx";
> status = "disabled";
> };
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-11-02 21:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 10:51 [RFC 0/3] i2c: sh_mobile: add DMA support Wolfram Sang
2014-10-31 10:51 ` [RFC 1/3] " Wolfram Sang
2014-11-02 22:04 ` Laurent Pinchart
2014-11-03 7:47 ` Wolfram Sang
2014-11-03 8:58 ` Geert Uytterhoeven
[not found] ` <CAMuHMdX1-ANQQhZkfKG67-TSKEUO6sFeiUMkkA323Ww4Cw9JrA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-04 10:19 ` Wolfram Sang
[not found] ` <1414752678-26078-1-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2014-10-31 10:51 ` [RFC 2/3] ARM: shmobile: r8a7790: add DMA nodes for IIC Wolfram Sang
[not found] ` <1414752678-26078-3-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2014-11-02 21:47 ` Laurent Pinchart
2014-11-03 9:04 ` Geert Uytterhoeven
2014-10-31 10:51 ` [RFC 3/3] ARM: shmobile: r8a7791: " Wolfram Sang
2014-11-02 21:47 ` Laurent Pinchart [this message]
[not found] ` <1414752678-26078-4-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2014-11-03 9:04 ` Geert Uytterhoeven
2014-11-02 21:14 ` [RFC 0/3] i2c: sh_mobile: add DMA support Laurent Pinchart
2014-11-02 21:53 ` Wolfram Sang
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=17049901.fYZShuhnQA@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--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).