Messages in this thread | | | Date | Mon, 10 Feb 2014 12:21:19 -0600 | From | linux@roeck-us ... | Subject | Re: [PATCH 01/17] Documentation: i2c: describe devicetree method for instantiating devices |
| |
Quoting Wolfram Sang <wsa@the-dreams.de>:
> Signed-off-by: Wolfram Sang <wsa@the-dreams.de> > 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
| |