devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: horms@verge.net.au, magnus.damm@gmail.com, geert@linux-m68k.org,
	arnd@arndb.de
Cc: linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Subject: [PATCHv4 0/4] Reference both DMA controllers
Date: Thu, 12 May 2016 10:54:41 +0200	[thread overview]
Message-ID: <1463043285-14702-1-git-send-email-niklas.soderlund+renesas@ragnatech.se> (raw)

Hi,

R-Car Gen2 have two DMA controllers, which are equivalent. However DMA
slaves were tied only to a single DMA controller in .dtsi. This series
add references to to both DMA controllers for all nodes that previously
only referenced one of them. It also adds dma references to the SDHI
nodes for r8a7794 which according to the datasheet should work but I
have not access to HW to verify.

Tested on Koelsch (r8a7791) by altering the compatible value of either
dmac0 or dmac1 and verifying that the DMA slaves pick the DMA controller
that is available.

* Changes since v3
- Fix accidentally deleted line, thanks Geert for spotting my error. I
  have now learnt the virtue of 'git diff --color-words'.
- Add Reviewed-by from Geert for patch 2-4.

* Changes since v2
- Squash a rather large series to one patch per SoC
- Rebase on top of renesas-devel-20160509-v4.6-rc7
- Always reference dmac0 before dmac1

* Changes since v1
- Rebase on top of renesas-devel-20160315-v4.5 and add dmas references
  new nodes (r8a7790: scif2 r8a7793: i2c6,i2c7,i2c8).
- Correct error in commit message 31/31 (s/QSPI/MMCIF).
- Collect Ack and Reviewed tags from Geert.

Niklas Söderlund (4):
  ARM: dts: r8a7790: Reference both DMA controllers
  ARM: dts: r8a7791: Reference both DMA controllers
  ARM: dts: r8a7793: Reference both DMA controllers
  ARM: dts: r8a7794: Reference both DMA controllers

 arch/arm/boot/dts/r8a7790.dtsi | 130 +++++++++++++++++++++---------------
 arch/arm/boot/dts/r8a7791.dtsi | 145 ++++++++++++++++++++++++-----------------
 arch/arm/boot/dts/r8a7793.dtsi | 130 +++++++++++++++++++++---------------
 arch/arm/boot/dts/r8a7794.dtsi | 119 ++++++++++++++++++++-------------
 4 files changed, 318 insertions(+), 206 deletions(-)

--
2.8.2

             reply	other threads:[~2016-05-12  8:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-12  8:54 Niklas Söderlund [this message]
     [not found] ` <1463043285-14702-1-git-send-email-niklas.soderlund+renesas-1zkq55x86MTxsAP9Fp7wbw@public.gmane.org>
2016-05-12  8:54   ` [PATCHv4 1/4] ARM: dts: r8a7790: Reference both DMA controllers Niklas Söderlund
2016-05-12  8:54 ` [PATCHv4 2/4] ARM: dts: r8a7791: " Niklas Söderlund
2016-05-12  8:54 ` [PATCHv4 3/4] ARM: dts: r8a7793: " Niklas Söderlund
2016-05-12  8:54 ` [PATCHv4 4/4] ARM: dts: r8a7794: " Niklas Söderlund
2016-05-16  8:11 ` [PATCHv4 0/4] " Simon Horman

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=1463043285-14702-1-git-send-email-niklas.soderlund+renesas@ragnatech.se \
    --to=niklas.soderlund+renesas@ragnatech.se \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=horms@verge.net.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.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).