From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mlbe2k2.cs.myharris.net ([137.237.90.89]) by bombadil.infradead.org with esmtp (Exim 4.69 #1 (Red Hat Linux)) id 1MJTPi-0001Mt-4l for linux-mtd@lists.infradead.org; Wed, 24 Jun 2009 14:25:32 +0000 Message-ID: <4A423750.8080605@harris.com> Date: Wed, 24 Jun 2009 10:25:20 -0400 From: "Steven A. Falco" MIME-Version: 1.0 To: David Brownell , Stefan Roese Subject: Re: [Question] m25p80 driver versus spi clock rate References: <4A3FEE98.60700@harris.com> <200906231408.26912.david-b@pacbell.net> <4A414E07.5050303@harris.com> <200906231538.40125.david-b@pacbell.net> In-Reply-To: <200906231538.40125.david-b@pacbell.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "linuxppc-dev@ozlabs.org" , linux-mtd@lists.infradead.org, Mike Frysinger List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , David Brownell wrote: > On Tuesday 23 June 2009, Steven A. Falco wrote: >> m25p80 spi0.0: invalid bits-per-word (0) >> >> This message comes from spi_ppc4xx_setupxfer. I believe your patch >> is doing what you intended (i.e. forcing an initial call to >> spi_ppc4xx_setupxfer), but it exposes an OF / SPI linkage problem. >> >> Namely, of_register_spi_devices does not support a bits-per-word >> property, so bits-per-word is zero. > > Bits-per-word == 0 must be interpreted as == 8. > > Simple bug in the ppc4xx code. It currently rejects > values other than 8. Ok - I'll post a patch for that. Your changes to bitbang_work look good. I'm not clear on why you first set do_setup = -1 but later use do_setup = 1. Perhaps they should both be "1". Other than that, Acked-by: Steven A. Falco > > Speaking of spi_ppc4xx issues ... I still have an oldish > copy in my review queue, it needs something like the > appended patch. (Plus something to accept bpw == 0.) > Is there a newer version? That is a question for Stefan. Perhaps when I post my patch to the PPC list, we can move this further along... Steve