From: Pawel Moll <pawel.moll@arm.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Lee Jones <lee.jones@linaro.org>,
"sa@the-dreams.de" <sa@the-dreams.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jic23@cam.ac.uk" <jic23@cam.ac.uk>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
"grant.likely@linaro.org" <grant.likely@linaro.org>,
"tomasz.figa@gmail.com" <tomasz.figa@gmail.com>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"galak@codeaurora.org" <galak@codeaurora.org>
Subject: Re: [PATCH] Documentation: dt: i2c: Add LPS001WP to the Trivial Devices list
Date: Thu, 05 Sep 2013 12:40:09 +0100 [thread overview]
Message-ID: <1378381209.24019.21.camel@hornet> (raw)
In-Reply-To: <20130905113001.GR18206@e106331-lin.cambridge.arm.com>
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=C5=82
prev parent reply other threads:[~2013-09-05 11:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 13:50 [PATCH] Documentation: dt: i2c: Add LPS001WP to the Trivial Devices list Lee Jones
2013-09-04 14:24 ` Mark Rutland
2013-09-04 15:11 ` Lee Jones
2013-09-04 16:33 ` Lee Jones
2013-09-05 11:30 ` Mark Rutland
2013-09-05 11:40 ` Pawel Moll [this message]
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=1378381209.24019.21.camel@hornet \
--to=pawel.moll@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=jic23@cam.ac.uk \
--cc=lee.jones@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rob.herring@calxeda.com \
--cc=sa@the-dreams.de \
--cc=swarren@wwwdotorg.org \
--cc=tomasz.figa@gmail.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).