From: Anton Vorontsov <cbouatmailru@gmail.com>
To: "André Schwarz" <andre.schwarz@matrix-vision.de>
Cc: LinuxPPC List <linuxppc-dev@ozlabs.org>,
DevTreeDiscuss <devicetree-discuss@lists.ozlabs.org>
Subject: Re: How to define an I2C-to-SPI bridge device ?
Date: Fri, 3 Sep 2010 16:08:58 +0400 [thread overview]
Message-ID: <20100903120858.GA19380@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <1283502979.17812.22.camel@swa-m460>
On Fri, Sep 03, 2010 at 10:36:19AM +0200, André Schwarz wrote:
> Hi,
>
> we're about to get new MPC8377 based hardware with various peripherals.
> There are two I2C-to-SPI bridge devices (NXP SC18IS602) and I'm not sure
> how to define a proper dts...
>
> Of course it's an easy thing creating 2 child nodes on the CPU's I2C
> device - but how can I represent the created SPI bus ?
Um.. the same as the other SPI buses? I.e.
i2c-controller { /* SOC I2C controller */
spi-controller { /* The I2C-to-SPI bridge */
spi-device@0 {
};
spi-device@1 {
};
};
};
> Is the (possibly) required driver (of_sc18is60x_spi ?) supposed to be an
> I2C slave or an SPI host driver ?
It should be an I2C driver that registers an SPI master (i.e.
calls spi_alloc_master() and spi_register_master()).
Thanks,
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
next prev parent reply other threads:[~2010-09-03 12:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 8:36 How to define an I2C-to-SPI bridge device ? André Schwarz
2010-09-03 12:08 ` Anton Vorontsov [this message]
2010-09-06 11:40 ` Andre Schwarz
2010-09-06 14:37 ` André Schwarz
2010-09-09 18:23 ` Grant Likely
2010-09-10 8:11 ` André Schwarz
2010-09-10 17:37 ` Grant Likely
2010-09-10 18:14 ` André Schwarz
2010-09-10 18:27 ` Anton Vorontsov
2010-09-10 18:28 ` Grant Likely
2010-09-12 15:10 ` André Schwarz
2010-09-13 4:39 ` Grant Likely
2011-03-25 9:28 ` Andre Schwarz
2011-03-29 16:21 ` Andre Schwarz
2011-03-31 3:43 ` Grant Likely
2010-09-09 17:06 ` Grant Likely
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=20100903120858.GA19380@oksana.dev.rtsoft.ru \
--to=cbouatmailru@gmail.com \
--cc=andre.schwarz@matrix-vision.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linuxppc-dev@ozlabs.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).