Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-renesas-soc@vger.kernel.org, robh+dt@kernel.org,
	mark.rutland@arm.com, devicetree@vger.kernel.org
Cc: horms@verge.net.au
Subject: [PATCH RFC v2 10/12] DT: arm: shmobile: document SK-RZG1M board
Date: Fri, 30 Sep 2016 01:32:38 +0300	[thread overview]
Message-ID: <32082029.3R2IVcCXuY@wasted.cogentembedded.com> (raw)
In-Reply-To: <1987532.PE2ex6PrJ5@wasted.cogentembedded.com>

Document the SK-RZG1M device tree bindings, listing it as a supported board.

This allows to use checkpatch.pl to validate .dts files referring to the
SK-RZG1M board.

Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>

---
Changes in version 2:
- new patch.

 Documentation/devicetree/bindings/arm/shmobile.txt |    2 ++
 1 file changed, 2 insertions(+)

Index: renesas/Documentation/devicetree/bindings/arm/shmobile.txt
===================================================================
--- renesas.orig/Documentation/devicetree/bindings/arm/shmobile.txt
+++ renesas/Documentation/devicetree/bindings/arm/shmobile.txt
@@ -75,5 +75,7 @@ Boards:
     compatible = "renesas,salvator-x", "renesas,r8a7796";
   - SILK (RTP0RC7794LCB00011S)
     compatible = "renesas,silk", "renesas,r8a7794"
+  - SK-RZG1M (YR8A77430S000BE)
+    compatible = "renesas,sk-rzg1m", "renesas,r8a7743"
   - Wheat
     compatible = "renesas,wheat", "renesas,r8a7792"

  parent reply	other threads:[~2016-09-29 22:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-29 22:14 [PATCH RFC v2 0/12] Add R8A7743/SK-RZG1M board support Sergei Shtylyov
2016-09-29 22:16 ` [PATCH RFC v2 1/12] ARM: shmobile: r8a7743: add clock index macros Sergei Shtylyov
2016-09-29 22:17 ` [PATCH RFC v2 2/12] ARM: shmobile: r8a7743: add power domain " Sergei Shtylyov
2016-09-29 22:21 ` [PATCH RFC v2 3/12] soc: renesas: rcar-sysc: add R8A7743 support Sergei Shtylyov
2016-09-29 22:23 ` [PATCH RFC v2 4/12] ARM: shmobile: r8a7743: basic SoC support Sergei Shtylyov
2016-10-05 10:32   ` Laurent Pinchart
2016-09-29 22:25 ` [PATCH RFC v2 5/12] ARM: dts: r8a7743: initial SoC device tree Sergei Shtylyov
2016-09-29 22:26 ` [PATCH RFC v2 6/12] ARM: dts: r8a7743: add SYS-DMAC support Sergei Shtylyov
2016-09-29 22:28 ` [PATCH RFC v2 7/12] ARM: dts: r8a7743: add [H]SCIF[AB] support Sergei Shtylyov
2016-09-29 22:29 ` [PATCH RFC v2 8/12] ARM: dts: r8a7743: add Ether support Sergei Shtylyov
2016-09-29 22:30 ` [PATCH RFC v2 9/12] ARM: dts: r8a7743: add IRQC support Sergei Shtylyov
2016-09-29 22:32 ` Sergei Shtylyov [this message]
2016-09-30  8:32   ` [PATCH RFC v2 10/12] DT: arm: shmobile: document SK-RZG1M board Geert Uytterhoeven
2016-09-29 22:34 ` [PATCH RFC v2 11/12] ARM: dts: sk-rzg1m: initial device tree Sergei Shtylyov
2016-10-05  7:46   ` Geert Uytterhoeven
2016-09-29 22:35 ` [PATCH RFC v2 12/12] ARM: dts: sk-rzg1m: add Ether support Sergei Shtylyov
2016-10-01 11:29 ` [PATCH RFC v2 0/12] Add R8A7743/SK-RZG1M board support Geert Uytterhoeven

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=32082029.3R2IVcCXuY@wasted.cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=devicetree@vger.kernel.org \
    --cc=horms@verge.net.au \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.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