devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Paterson <chris.paterson2@renesas.com>
To: Ulf Hansson <ulf.hansson@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Simon Horman <horms@verge.net.au>,
	Magnus Damm <magnus.damm@gmail.com>,
	Russell King <linux@armlinux.org.uk>
Cc: Biju Das <biju.das@bp.renesas.com>,
	linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Chris Paterson <chris.paterson2@renesas.com>
Subject: [PATCH 0/3] Add MMCIF0 support for r8a7743/iwg20m
Date: Wed, 12 Jul 2017 11:03:22 +0100	[thread overview]
Message-ID: <1499853805-5915-1-git-send-email-chris.paterson2@renesas.com> (raw)

This series adds MMCIF0 support for the r8a7743 SoC and the iWave-RZG1M-20M
Qseven SOM.

This series is based on renesas-devel-20170711-v4.12.

Chris Paterson (3):
  dt-bindings: mmc: sh_mmcif: Document r8a7743 DT bindings
  ARM: dts: r8a7743: Add MMCIF0 support
  ARM: dts: iwg20m: Add MMCIF0 support

 .../devicetree/bindings/mmc/renesas,mmcif.txt      |  3 ++-
 arch/arm/boot/dts/r8a7743-iwg20m.dtsi              | 26 ++++++++++++++++++++++
 arch/arm/boot/dts/r8a7743.dtsi                     | 16 +++++++++++++
 3 files changed, 44 insertions(+), 1 deletion(-)

-- 
1.9.1

             reply	other threads:[~2017-07-12 10:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-12 10:03 Chris Paterson [this message]
2017-07-12 10:03 ` [PATCH 1/3] dt-bindings: mmc: sh_mmcif: Document r8a7743 DT bindings Chris Paterson
2017-07-12 11:20   ` Geert Uytterhoeven
2017-07-13  7:54     ` Simon Horman
2017-07-13  8:00       ` Geert Uytterhoeven
2017-07-13  8:07         ` Simon Horman
2017-07-13 10:06   ` Ulf Hansson
2017-07-12 10:03 ` [PATCH 2/3] ARM: dts: r8a7743: Add MMCIF0 support Chris Paterson
2017-07-12 11:21   ` Geert Uytterhoeven
2017-07-13  7:59     ` Simon Horman
2017-07-12 10:03 ` [PATCH 3/3] ARM: dts: iwg20m: " Chris Paterson
     [not found]   ` <1499853805-5915-4-git-send-email-chris.paterson2-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
2017-07-12 11:52     ` Geert Uytterhoeven
2017-07-13  8:02       ` Simon Horman
     [not found]         ` <20170713080228.GI5580-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2017-07-13  8:12           ` Simon Horman
2017-07-13  9:28             ` Chris Paterson
2017-07-13  0:25   ` kbuild test robot
     [not found]     ` <201707130850.0py1QazG%fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-07-13  7:54       ` Simon Horman
     [not found]         ` <20170713075414.GF5580-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2017-07-13  8:46           ` [kbuild-all] " Ye Xiaolong
2017-07-13 15:39   ` [PATCH v2] " Chris Paterson
2017-07-13 16:31     ` Geert Uytterhoeven
     [not found]       ` <CAMuHMdV2f1oyi9dNGdGmqx7x7RNk10jomKQ4jHJ9wXNSEBKtNA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-07-14  7:33         ` 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=1499853805-5915-1-git-send-email-chris.paterson2@renesas.com \
    --to=chris.paterson2@renesas.com \
    --cc=biju.das@bp.renesas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=horms@verge.net.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=magnus.damm@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=ulf.hansson@linaro.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).