linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 01/17] Documentation: i2c: describe devicetree method for instantiating devices
Date: Mon, 10 Feb 2014 11:03:55 +0100	[thread overview]
Message-ID: <1392026654-5343-2-git-send-email-wsa@the-dreams.de> (raw)
In-Reply-To: <1392026654-5343-1-git-send-email-wsa@the-dreams.de>

Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
Cc: devicetree at vger.kernel.org
Cc: linux-arm-kernel at lists.infradead.org
---

 Documentation/i2c/instantiating-devices | 34 +++++++++++++++++++++++++++++++--
 1 file changed, 32 insertions(+), 2 deletions(-)

diff --git a/Documentation/i2c/instantiating-devices b/Documentation/i2c/instantiating-devices
index c70e7a7..6df095a 100644
--- a/Documentation/i2c/instantiating-devices
+++ b/Documentation/i2c/instantiating-devices
@@ -8,8 +8,8 @@ reason, the kernel code must instantiate I2C devices explicitly. There are
 several ways to achieve this, depending on the context and requirements.
 
 
-Method 1: Declare the I2C devices by bus number
------------------------------------------------
+Method 1a: Declare the I2C devices by bus number
+------------------------------------------------
 
 This method is appropriate when the I2C bus is a system bus as is the case
 for many embedded systems. On such systems, each I2C bus has a number
@@ -51,6 +51,36 @@ The devices will be automatically unbound and destroyed when the I2C bus
 they sit on goes away (if ever.)
 
 
+Method 1b: Declare the I2C devices via devicetree
+-------------------------------------------------
+
+This method has the same implications as method 1a. The declaration of I2C
+devices is here done via devicetree as subnodes of the master controller.
+
+Example:
+
+	i2c1: i2c at 400a0000 {
+		/* ... master properties skipped ... */
+		clock-frequency = <100000>;
+
+		flash at 50 {
+			compatible = "atmel,24c256";
+			reg = <0x50>;
+		};
+
+		pca9532: gpio at 60 {
+			compatible = "nxp,pca9532";
+			gpio-controller;
+			#gpio-cells = <2>;
+			reg = <0x60>;
+		};
+	};
+
+Here, two devices are attached to the bus using a speed of 100kHz. For
+additional properties which might be needed to set up the device, please refer
+to its devicetree documentation in Documentation/devicetree/bindings/.
+
+
 Method 2: Instantiate the devices explicitly
 --------------------------------------------
 
-- 
1.8.5.1

  reply	other threads:[~2014-02-10 10:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 10:03 [PATCH 00/17] i2c: deprecate class based instantiation for embedded I2C drivers Wolfram Sang
2014-02-10 10:03 ` Wolfram Sang [this message]
2014-02-10 18:21   ` [PATCH 01/17] Documentation: i2c: describe devicetree method for instantiating devices linux at roeck-us.net
2014-02-12 15:15     ` Wolfram Sang
2014-02-15 14:48   ` Wolfram Sang
2014-02-10 10:03 ` [PATCH 02/17] i2c: add deprecation warning for class based instantiation Wolfram Sang
2014-02-10 10:04 ` [PATCH 10/17] i2c: i2c-nomadik: deprecate " Wolfram Sang
2014-02-12 16:24   ` Linus Walleij
2014-02-10 10:04 ` [PATCH 13/17] i2c: i2c-s3c2410: " Wolfram Sang
2014-02-10 10:04 ` [PATCH 14/17] i2c: i2c-sirf: " Wolfram Sang
2014-02-10 10:04 ` [PATCH 15/17] i2c: i2c-stu300: " Wolfram Sang
2014-02-12 16:22   ` Linus Walleij
2014-03-28  7:55 ` [PATCH 00/17] i2c: deprecate class based instantiation for embedded I2C drivers 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=1392026654-5343-2-git-send-email-wsa@the-dreams.de \
    --to=wsa@the-dreams.de \
    --cc=linux-arm-kernel@lists.infradead.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).