[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1378381209.24019.21.camel@hornet>
Date: Thu, 05 Sep 2013 12:40:09 +0100
From: Pawel Moll <pawel.moll@....com>
To: Mark Rutland <mark.rutland@....com>
Cc: Lee Jones <lee.jones@...aro.org>,
"sa@...-dreams.de" <sa@...-dreams.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"jic23@....ac.uk" <jic23@....ac.uk>,
"linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"swarren@...dotorg.org" <swarren@...dotorg.org>,
"ian.campbell@...rix.com" <ian.campbell@...rix.com>,
"grant.likely@...aro.org" <grant.likely@...aro.org>,
"tomasz.figa@...il.com" <tomasz.figa@...il.com>,
"rob.herring@...xeda.com" <rob.herring@...xeda.com>,
"galak@...eaurora.org" <galak@...eaurora.org>
Subject: Re: [PATCH] Documentation: dt: i2c: Add LPS001WP to the Trivial
Devices list
On Thu, 2013-09-05 at 12:30 +0100, Mark Rutland wrote:
> I also note that the device can also be attached to SPI. Do we have any
> other devices which may be attached to either? Do we handle that, and if
> so, how (do we have the same compatible string for both interfaces?)?
Theoretically you don't need anything to make it work - nodes being a
children of a I2C master will instantiate i2c_clients, offspring of a
SPI master will become spi_devices. Then you register two drivers - I2C
and SPI ones, probably sharing most of the code - both matching the same
compatible value. The I2C one will be bound only with the I2C nodes, the
same applies to SPI.
I hope :-)
Paweł
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists