linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Brandt <chris.brandt@renesas.com>
To: Simon Horman <horms@verge.net.au>,
	Rob Herring <robh+dt@kernel.org>,
	"Mark Rutland" <mark.rutland@arm.com>
Cc: <devicetree@vger.kernel.org>, <linux-i2c@vger.kernel.org>,
	<linux-renesas-soc@vger.kernel.org>,
	Chris Brandt <chris.brandt@renesas.com>
Subject: [PATCH 3/7] dt-bindings: i2c: riic: document r7s9210 support
Date: Tue, 30 Apr 2019 08:23:05 -0500	[thread overview]
Message-ID: <20190430132309.12473-4-chris.brandt@renesas.com> (raw)
In-Reply-To: <20190430132309.12473-1-chris.brandt@renesas.com>

Document support for the R7S9210 (RZ/A2) SoC. Also explicitly document
bindings for the R7S72100 (RZ/A1) SoC.

Signed-off-by: Chris Brandt <chris.brandt@renesas.com>
---
 Documentation/devicetree/bindings/i2c/i2c-riic.txt | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/i2c/i2c-riic.txt b/Documentation/devicetree/bindings/i2c/i2c-riic.txt
index 0bcc4716c319..e26fe3ad86a9 100644
--- a/Documentation/devicetree/bindings/i2c/i2c-riic.txt
+++ b/Documentation/devicetree/bindings/i2c/i2c-riic.txt
@@ -1,7 +1,10 @@
 Device tree configuration for Renesas RIIC driver
 
 Required properties:
-- compatible      : "renesas,riic-<soctype>". "renesas,riic-rz" as fallback
+- compatible      :
+	"renesas,riic-r7s72100" if the device is a part of a R7S72100 SoC.
+	"renesas,riic-r7s9210" if the device is a part of a R7S9210 SoC.
+	"renesas,riic-rz" for a generic RZ/A compatible device.
 - reg             : address start and address range size of device
 - interrupts      : 8 interrupts (TEI, RI, TI, SPI, STI, NAKI, ALI, TMOI)
 - clock-frequency : frequency of bus clock in Hz
-- 
2.16.1


  parent reply	other threads:[~2019-04-30 13:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-30 13:23 [PATCH 0/7] dts: r7s9210: Add RZ/A2 devices Chris Brandt
2019-04-30 13:23 ` [PATCH 1/7] ARM: dts: r7s9210: Add RSPI Chris Brandt
2019-04-30 14:30   ` Geert Uytterhoeven
2019-04-30 13:23 ` [PATCH 2/7] ARM: dts: r7s9210: Add Ethernet support Chris Brandt
2019-04-30 14:38   ` Geert Uytterhoeven
2019-04-30 13:23 ` Chris Brandt [this message]
2019-04-30 14:47   ` [PATCH 3/7] dt-bindings: i2c: riic: document r7s9210 support Geert Uytterhoeven
2019-05-02 21:07   ` Rob Herring
2019-05-03 14:53   ` Wolfram Sang
2019-04-30 13:23 ` [PATCH 4/7] ARM: dts: r7s9210: Add RIIC support Chris Brandt
2019-04-30 14:47   ` Geert Uytterhoeven
2019-04-30 13:23 ` [PATCH 5/7] ARM: dts: r7s9210: Add SDHI support Chris Brandt
2019-04-30 14:53   ` Geert Uytterhoeven
2019-04-30 13:23 ` [PATCH 6/7] ARM: dts: r7s9210-rza2mevb: Add Ethernet support Chris Brandt
2019-04-30 15:21   ` Geert Uytterhoeven
2019-04-30 16:03     ` Chris Brandt
2019-04-30 13:23 ` [PATCH 7/7] ARM: dts: r7s9210-rza2mevb: Add SDHI support Chris Brandt
2019-04-30 15:30   ` Geert Uytterhoeven
2019-05-06 14:02 ` [PATCH 0/7] dts: r7s9210: Add RZ/A2 devices 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=20190430132309.12473-4-chris.brandt@renesas.com \
    --to=chris.brandt@renesas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=horms@verge.net.au \
    --cc=linux-i2c@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).