From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [203.10.76.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.ozlabs.org", Issuer "CA Cert Signing Authority" (verified OK)) by bilbo.ozlabs.org (Postfix) with ESMTPS id 3382FB7282 for ; Fri, 19 Jun 2009 00:06:06 +1000 (EST) Message-Id: From: Kumar Gala To: avorontsov@ru.mvista.com In-Reply-To: <20090618130955.GA1369@oksana.dev.rtsoft.ru> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Mime-Version: 1.0 (Apple Message framework v935.3) Subject: Re: [PATCH -mm][POWERPC] mpc8xxx : allow SPI without cs. Date: Thu, 18 Jun 2009 09:04:46 -0500 References: <4A39DC80.7030906@arvoo.nl> <20090618130955.GA1369@oksana.dev.rtsoft.ru> Cc: spi-devel-general@lists.sourceforge.net, Rini van Zetten , linuxppc-dev list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Jun 18, 2009, at 8:09 AM, Anton Vorontsov wrote: > On Thu, Jun 18, 2009 at 08:19:44AM +0200, Rini van Zetten wrote: >> This patch adds the possibility to have a spi device without a cs. >> >> For example, the dts file should look something like this: >> >> spi-controller { >> gpios = <&pio1 1 0 /* cs0 */ >> 0 /* cs1, no GPIO */ >> &pio2 2 0>; /* cs2 */ >> > > Interesting scheme. I guess this is for eSPI controllers that can > do their own chip-selects, but we want GPIO chip selects in addition > (or in place of built-in ones), correct? That is a good question. What HW is this for (I don't think its for eSPI but I could be wrong). - k