Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753083AbaBJSVW (ORCPT ); Mon, 10 Feb 2014 13:21:22 -0500 Received: from mail.active-venture.com ([67.228.131.205]:52723 "EHLO mail.active-venture.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752361AbaBJSVU (ORCPT ); Mon, 10 Feb 2014 13:21:20 -0500 Message-ID: <20140210122119.115858a7ntu4lr40@67.228.131.205> Date: Mon, 10 Feb 2014 12:21:19 -0600 From: linux@roeck-us.net To: Wolfram Sang Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Rob Landley , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 01/17] Documentation: i2c: describe devicetree method for instantiating devices References: <1392026654-5343-1-git-send-email-wsa@the-dreams.de> <1392026654-5343-2-git-send-email-wsa@the-dreams.de> In-Reply-To: <1392026654-5343-2-git-send-email-wsa@the-dreams.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.3.10) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Wolfram Sang : > Signed-off-by: Wolfram Sang > Cc: devicetree@vger.kernel.org > Cc: linux-arm-kernel@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 > +------------------------------------------------- > + Hi Wolfram, There is now also a means to instantiate I2C devices through ACPI. This is documented in Documentation/acpi/enumeration.txt. Might be worthwhile to reference it from instantiating-devices. I guess that would be a separate patch though. Thanks, Guenter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/