From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ey0-f170.google.com (mail-ey0-f170.google.com [209.85.215.170]) by ozlabs.org (Postfix) with ESMTP id 3E3F8B714E for ; Fri, 3 Sep 2010 22:09:03 +1000 (EST) Received: by eyg24 with SMTP id 24so1204577eyg.15 for ; Fri, 03 Sep 2010 05:09:01 -0700 (PDT) Date: Fri, 3 Sep 2010 16:08:58 +0400 From: Anton Vorontsov To: =?utf-8?B?QW5kcsOp?= Schwarz Subject: Re: How to define an I2C-to-SPI bridge device ? Message-ID: <20100903120858.GA19380@oksana.dev.rtsoft.ru> References: <1283502979.17812.22.camel@swa-m460> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 In-Reply-To: <1283502979.17812.22.camel@swa-m460> Cc: LinuxPPC List , DevTreeDiscuss List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anton Vorontsov Subject: Re: How to define an I2C-to-SPI bridge device ? Date: Fri, 3 Sep 2010 16:08:58 +0400 Message-ID: <20100903120858.GA19380@oksana.dev.rtsoft.ru> References: <1283502979.17812.22.camel@swa-m460> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: Content-Disposition: inline In-Reply-To: <1283502979.17812.22.camel@swa-m460> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linuxppc-dev-bounces+glppe-linuxppc-embedded-2=m.gmane.org@lists.ozlabs.org Errors-To: linuxppc-dev-bounces+glppe-linuxppc-embedded-2=m.gmane.org@lists.ozlabs.org To: =?utf-8?B?QW5kcsOp?= Schwarz Cc: LinuxPPC List , DevTreeDiscuss List-Id: devicetree@vger.kernel.org T24gRnJpLCBTZXAgMDMsIDIwMTAgYXQgMTA6MzY6MTlBTSArMDIwMCwgQW5kcsOpIFNjaHdhcnog d3JvdGU6Cj4gSGksCj4gCj4gd2UncmUgYWJvdXQgdG8gZ2V0IG5ldyBNUEM4Mzc3IGJhc2VkIGhh cmR3YXJlIHdpdGggdmFyaW91cyBwZXJpcGhlcmFscy4KPiBUaGVyZSBhcmUgdHdvIEkyQy10by1T UEkgYnJpZGdlIGRldmljZXMgKE5YUCBTQzE4SVM2MDIpIGFuZCBJJ20gbm90IHN1cmUKPiBob3cg dG8gZGVmaW5lIGEgcHJvcGVyIGR0cy4uLgo+IAo+IE9mIGNvdXJzZSBpdCdzIGFuIGVhc3kgdGhp bmcgY3JlYXRpbmcgMiBjaGlsZCBub2RlcyBvbiB0aGUgQ1BVJ3MgSTJDCj4gZGV2aWNlIC0gYnV0 IGhvdyBjYW4gSSByZXByZXNlbnQgdGhlIGNyZWF0ZWQgU1BJIGJ1cyA/CgpVbS4uIHRoZSBzYW1l IGFzIHRoZSBvdGhlciBTUEkgYnVzZXM/IEkuZS4KCmkyYy1jb250cm9sbGVyIHsgIC8qIFNPQyBJ MkMgY29udHJvbGxlciAqLwoJc3BpLWNvbnRyb2xsZXIgeyAgLyogVGhlIEkyQy10by1TUEkgYnJp ZGdlICovCgkJc3BpLWRldmljZUAwIHsKCQl9OwoJCXNwaS1kZXZpY2VAMSB7CgkJfTsKCX07Cn07 Cgo+IElzIHRoZSAocG9zc2libHkpIHJlcXVpcmVkIGRyaXZlciAob2Zfc2MxOGlzNjB4X3NwaSA/ KSBzdXBwb3NlZCB0byBiZSBhbgo+IEkyQyBzbGF2ZSBvciBhbiBTUEkgaG9zdCBkcml2ZXIgPwoK SXQgc2hvdWxkIGJlIGFuIEkyQyBkcml2ZXIgdGhhdCByZWdpc3RlcnMgYW4gU1BJIG1hc3RlciAo aS5lLgpjYWxscyBzcGlfYWxsb2NfbWFzdGVyKCkgYW5kIHNwaV9yZWdpc3Rlcl9tYXN0ZXIoKSku CgpUaGFua3MsCgotLSAKQW50b24gVm9yb250c292CmVtYWlsOiBjYm91YXRtYWlscnVAZ21haWwu Y29tCmlyYzovL2lyYy5mcmVlbm9kZS5uZXQvYmQyCl9fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fCkxpbnV4cHBjLWRldiBtYWlsaW5nIGxpc3QKTGludXhwcGMt ZGV2QGxpc3RzLm96bGFicy5vcmcKaHR0cHM6Ly9saXN0cy5vemxhYnMub3JnL2xpc3RpbmZvL2xp bnV4cHBjLWRldg==