mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org,
	"Masahiro Yamada" <yamada.masahiro@socionext.com>,
	"Satoru OKAMOTO" <okamoto.satoru@socionext.com>,
	"Andreas Färber" <afaerber@suse.de>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Mark Rutland" <mark.rutland@arm.com>,
	devicetree@vger.kernel.org
Subject: [PATCH 3/5] dt-bindings: arm: Document Socionext MB86S71 and Fujitsu F-Cue
Date: Sun, 25 Jun 2017 19:00:18 +0200	[thread overview]
Message-ID: <20170625170020.11791-4-afaerber@suse.de> (raw)
In-Reply-To: <20170625170020.11791-1-afaerber@suse.de>

For consistency with existing SoC bindings, use "fujitsu,mb86s71" but
socionext.txt.

Signed-off-by: Andreas Färber <afaerber@suse.de>
---
 Documentation/devicetree/bindings/arm/socionext.txt | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/arm/socionext.txt

diff --git a/Documentation/devicetree/bindings/arm/socionext.txt b/Documentation/devicetree/bindings/arm/socionext.txt
new file mode 100644
index 000000000000..63227fe7b773
--- /dev/null
+++ b/Documentation/devicetree/bindings/arm/socionext.txt
@@ -0,0 +1,17 @@
+Socionext platforms device tree bindings
+----------------------------------------
+
+
+MB86S7x SoC
+===========
+
+Required root node properties:
+
+ - compatible :  must contain "fujitsu,mb86s71" for MB86S71
+
+
+Boards:
+
+Root node property compatible must contain, depending on board:
+
+ - Fujitsu F-Cue: "fujitsu,f-cue"
-- 
2.12.3

  parent reply	other threads:[~2017-06-25 17:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-25 17:00 [PATCH 0/5] ARM: Socionext MB86S71 and Fujitsu F-Cue enablement Andreas Färber
2017-06-25 17:00 ` [PATCH 1/5] clk: mb86s7x: Suppress build Andreas Färber
2017-06-28 16:13   ` Stephen Boyd
2017-06-28 17:32     ` Jassi Brar
2017-06-28 22:29       ` Stephen Boyd
2017-06-29 11:17         ` Andreas Färber
2017-06-25 17:00 ` [PATCH 2/5] ARM: Prepare Socionext MB86S71 Andreas Färber
2017-06-25 17:00 ` Andreas Färber [this message]
2017-06-28 16:46   ` [PATCH 3/5] dt-bindings: arm: Document Socionext MB86S71 and Fujitsu F-Cue Rob Herring
2017-06-29 12:18     ` Masahiro Yamada
2017-06-29 12:53       ` Andreas Färber
2017-06-29 17:18         ` Masahiro Yamada
2017-11-04 13:44           ` Andreas Färber
2017-11-04 14:57             ` Ard Biesheuvel
2017-11-04 15:30               ` Andreas Färber
2017-11-04 15:39                 ` Ard Biesheuvel
2017-11-04 20:06                   ` Andreas Färber
2017-11-04 20:39                     ` Ard Biesheuvel
2017-11-06  6:58                       ` Andreas Färber
2017-11-06  8:05                         ` Yang Zhang
2017-11-06 11:28                         ` Ard Biesheuvel
2017-11-13 15:40                           ` Andreas Färber
2017-11-13 15:55                             ` Ard Biesheuvel
2017-06-25 17:00 ` [PATCH 4/5] ARM: dts: Add " Andreas Färber
2017-06-25 17:00 ` [PATCH 5/5] ARM: dts: mb86s71-f-cue: Add fake UART0 clock Andreas Färber

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=20170625170020.11791-4-afaerber@suse.de \
    --to=afaerber@suse.de \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=okamoto.satoru@socionext.com \
    --cc=robh+dt@kernel.org \
    --cc=yamada.masahiro@socionext.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

all inboxes | Powered by JetHome®