From: Khalil Blaiech <kblaiech@nvidia.com>
To: Rob Herring <robh@kernel.org>, linux-i2c@vger.kernel.org
Cc: Khalil Blaiech <kblaiech@mellanox.com>,
Vadim Pasternak <vadimp@mellanox.com>
Subject: [PATCH v11 2/2] dt-bindings: i2c: I2C binding for Mellanox BlueField SoC
Date: Tue, 22 Sep 2020 18:49:38 -0400 [thread overview]
Message-ID: <cce96d20e0bb258ad84c6ed52c49b957f0fa3452.1600804577.git.kblaiech@mellanox.com> (raw)
In-Reply-To: <cover.1600804577.git.kblaiech@mellanox.com>
In-Reply-To: <cover.1600804577.git.kblaiech@mellanox.com>
From: Khalil Blaiech <kblaiech@mellanox.com>
Add device tree bindings documentation for Mellanox BlueField
I2C SMBus controller.
Signed-off-by: Khalil Blaiech <kblaiech@mellanox.com>
---
v5->v6:
- Adding description of an extra resource to be
consistent with new BlueField-2 SoCs.
- Adding an additional example of device instance.
v3->v4:
- Re-ordering of the property descriptions.
- Removing useless register addresses from the
resource description.
- Definition of default clock-frequency value.
- Fixing format issues; removing spaces.
- Removing "aliases" from Example section.
- Renaming device instance node in Example section.
v2->v3:
- Removing shared resources from the controller
instance.
- Updating the 'compatible' property and support the
second generation of the Mellanox BlueField SoC.
- Fixing file format; replacing spaces with tabs.
v1->v2:
- Enumeration of the device resources.
- Updating the 'compatible' property to make it less
generic.
- Removing the 'bus' index property and replace it with
standard approach to read the bus identifier.
- Getting rid of the 'profile' property.
- Using 'clock-frequency' property instead of 'bus-freq'.
- Convertion of the clock frequency from KHz to Hz.
- Removing useless examples.
---
.../devicetree/bindings/i2c/mellanox,i2c-mlxbf.txt | 42 ++++++++++++++++++++++
1 file changed, 42 insertions(+)
create mode 100644 Documentation/devicetree/bindings/i2c/mellanox,i2c-mlxbf.txt
diff --git a/Documentation/devicetree/bindings/i2c/mellanox,i2c-mlxbf.txt b/Documentation/devicetree/bindings/i2c/mellanox,i2c-mlxbf.txt
new file mode 100644
index 0000000..566ea86
--- /dev/null
+++ b/Documentation/devicetree/bindings/i2c/mellanox,i2c-mlxbf.txt
@@ -0,0 +1,42 @@
+Device tree configuration for the Mellanox I2C SMBus on BlueField SoCs
+
+Required Properties:
+
+- compatible : should be "mellanox,i2c-mlxbf1" or "mellanox,i2c-mlxbf2".
+
+- reg : address offset and length of the device registers. The
+ registers consist of the following set of resources:
+ 1) Smbus block registers.
+ 2) Cause master registers.
+ 3) Cause slave registers.
+ 4) Cause coalesce registers (if compatible isn't set
+ to "mellanox,i2c-mlxbf1").
+
+- interrupts : interrupt number.
+
+Optional Properties:
+
+- clock-frequency : bus frequency used to configure timing registers;
+ allowed values are 100000, 400000 and 1000000;
+ those are expressed in Hz. Default is 100000.
+
+Example:
+
+i2c@2804000 {
+ compatible = "mellanox,i2c-mlxbf1";
+ reg = <0x02804000 0x800>,
+ <0x02801200 0x020>,
+ <0x02801260 0x020>;
+ interrupts = <57>;
+ clock-frequency = <100000>;
+};
+
+i2c@2808800 {
+ compatible = "mellanox,i2c-mlxbf2";
+ reg = <0x02808800 0x600>,
+ <0x02808e00 0x020>,
+ <0x02808e20 0x020>,
+ <0x02808e40 0x010>;
+ interrupts = <57>;
+ clock-frequency = <400000>;
+};
--
2.1.2
next prev parent reply other threads:[~2020-09-22 22:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 22:49 [PATCH v11 0/2] i2c: add driver for Mellanox BlueField SoC Khalil Blaiech
2020-09-22 22:49 ` [PATCH v11 1/2] i2c: i2c-mlxbf: I2C SMBus " Khalil Blaiech
2020-09-27 13:54 ` Wolfram Sang
2020-09-29 22:45 ` Khalil Blaiech
2020-09-30 5:41 ` Wolfram Sang
2020-10-05 23:54 ` Khalil Blaiech
2020-10-22 14:45 ` Khalil Blaiech
2020-09-22 22:49 ` Khalil Blaiech [this message]
2020-09-22 23:05 ` [PATCH v11 2/2] dt-bindings: i2c: I2C binding " Rob Herring
2020-09-29 22:59 ` Khalil Blaiech
2020-09-27 13:57 ` Wolfram Sang
2020-09-29 22:58 ` Khalil Blaiech
2020-09-30 5:44 ` Wolfram Sang
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=cce96d20e0bb258ad84c6ed52c49b957f0fa3452.1600804577.git.kblaiech@mellanox.com \
--to=kblaiech@nvidia.com \
--cc=kblaiech@mellanox.com \
--cc=linux-i2c@vger.kernel.org \
--cc=robh@kernel.org \
--cc=vadimp@mellanox.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;
as well as URLs for NNTP newsgroup(s).