From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mika.eatserver.nl (mika.eatserver.nl [195.20.9.75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 7C6651007D2 for ; Fri, 27 Jan 2012 02:07:23 +1100 (EST) Message-ID: <4F216C25.6000303@aimvalley.nl> Date: Thu, 26 Jan 2012 16:07:17 +0100 From: Norbert van Bolhuis MIME-Version: 1.0 To: Bruce_Leonard@selinc.com Subject: Re: FSL SPI driver question References: <4F2004B1.5030607@aimvalley.nl> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: linuxppc-dev@lists.ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi Bruce, On 01/25/12 20:49, Bruce_Leonard@selinc.com wrote: . . . > Thanks for the reply. Yes I did find spidev_fdx.c and in fact copied it > for my tests. I still see SPICLK active only during the time the 8308 is > sending data (read cmd + address). Nothing happens with the clock after > that when the NvRAM is ready to send data. > > Bruce > ok, then I don't know. I doubt this is a spidev or FSP SPI driver problem though. Questions like: Could it be a HW problem ? Is the correct SPI mode used ? Does it work in u-boot ? Come to mind in a situation like this. Norbert.