From: Sagar Shrikant Kadam <sagar.kadam@sifive.com>
To: robh+dt@kernel.org, mark.rutland@arm.com, palmer@sifive.com,
paul.walmsley@sifive.com, sagar.kadam@sifive.com,
peter@korsgaard.com, andrew@lunn.ch, linux-i2c@vger.kernel.org,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 v1 1/3] dt-bindings: i2c: add documentation for adding SiFive I2C driver
Date: Mon, 6 May 2019 18:23:58 +0530 [thread overview]
Message-ID: <1557147240-29551-2-git-send-email-sagar.kadam@sifive.com> (raw)
In-Reply-To: <1557147240-29551-1-git-send-email-sagar.kadam@sifive.com>
Add DT binding for OpenCore's based i2c device as found in
FU540 Chipset on HiFive Unleashed Platform (Rev A00).
The doc explains, how to add DT support for I2C devices.
Signed-off-by: Sagar Shrikant Kadam <sagar.kadam@sifive.com>
---
.../devicetree/bindings/i2c/i2c-sifive.txt | 29 ++++++++++++++++++++++
1 file changed, 29 insertions(+)
create mode 100644 Documentation/devicetree/bindings/i2c/i2c-sifive.txt
diff --git a/Documentation/devicetree/bindings/i2c/i2c-sifive.txt b/Documentation/devicetree/bindings/i2c/i2c-sifive.txt
new file mode 100644
index 0000000..2a0fc9b
--- /dev/null
+++ b/Documentation/devicetree/bindings/i2c/i2c-sifive.txt
@@ -0,0 +1,29 @@
+SiFive I2C controller Device Tree Bindings
+-------------------------------------------------
+
+Required properties:
+
+- compatible : Should be "sifive,<chipset>-i2c" for a particular chip or
+ "sifive,i2c<ver>" for a general I2C block.
+ For FU540 chipset the supported compatible string is "sifive,fu540-c000-i2c".
+- reg : Physical base address and size of I2C registers map.
+- reg-names : Should contain the resource reg names.
+- clocks : Must reference the frequency given to the controller.
+- #address-cells : Must be '1'.
+- #size-cells : Must be '0'.
+- clock-frequency : desired I2C bus clock frequency.
+
+Example:
+ i2c@10030000 {
+ compatible = "sifive,i2c0","sifive,fu540-c000-i2c";
+ reg = <0x0 0x10030000 0x0 0x1000>;
+ reg-names = "i2c-control";
+ clocks = <&tlclk>;
+ clock-frequency = <100000>;
+
+ reg-shift = <2>;
+ reg-io-width = <1>;
+
+ #address-cells = <1>;
+ #size-cells = <0>;
+ };
--
1.9.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-05-06 12:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 12:53 [PATCH v1 v1 0/3] Add dt bindings to support I2C on sifive devices and a fix for polling mode i2c transfers Sagar Shrikant Kadam
2019-05-06 12:53 ` Sagar Shrikant Kadam [this message]
2019-05-06 13:19 ` [PATCH v1 v1 1/3] dt-bindings: i2c: add documentation for adding SiFive I2C driver Andrew Lunn
2019-05-06 17:41 ` Sagar Kadam
2019-05-06 12:53 ` [PATCH v1 v1 2/3] i2c-ocore: sifive: add support for i2c device on FU540-c000 SoC Sagar Shrikant Kadam
2019-05-06 12:54 ` [PATCH v1 v1 3/3] i2c-ocores: sifive: add polling mode workaround for FU540-C000 SoC Sagar Shrikant Kadam
2019-05-06 13:29 ` Andrew Lunn
2019-05-06 17:54 ` Sagar Kadam
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=1557147240-29551-2-git-send-email-sagar.kadam@sifive.com \
--to=sagar.kadam@sifive.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=peter@korsgaard.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).