From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from buildserver.ru.mvista.com (unknown [213.79.90.228]) by ozlabs.org (Postfix) with ESMTP id D6E6E1007D1 for ; Fri, 27 Nov 2009 06:01:03 +1100 (EST) Date: Thu, 26 Nov 2009 22:01:01 +0300 From: Anton Vorontsov To: Grant Likely Subject: Re: spi_mpc8xxx.c: chip select polarity problem Message-ID: <20091126190101.GA19404@oksana.dev.rtsoft.ru> References: <200911161742.46663.to-fleischer@t-online.de> <200911211708.47253.to-fleischer@t-online.de> <200911252141.59549.to-fleischer@t-online.de> <20091126121204.GA3558@oksana.dev.rtsoft.ru> <20091126184157.GA16607@oksana.dev.rtsoft.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 In-Reply-To: Cc: Torsten Fleischer , spi-devel-general@lists.sourceforge.net, linuxppc-dev@lists.ozlabs.org Reply-To: avorontsov@ru.mvista.com List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, Nov 26, 2009 at 11:50:05AM -0700, Grant Likely wrote: > On Thu, Nov 26, 2009 at 11:41 AM, Anton Vorontsov > wrote: > > On Thu, Nov 26, 2009 at 11:16:34AM -0700, Grant Likely wrote: > > [...] > >> The spi-cs-high property is defined in > >> Documentation/powerpc/dts-bindings/spi-bus.txt, but it definitely was > >> a mistake > > > > Yup. > > > >> Currently the spi-cs-high property is parsed in the > >> of_register_spi_devices() function, but the CS polarity needs to be > >> known before registering devices.  It needs to be factored out into > >> another utility function callable by spi bus drivers so that it can > >> get polarity data at probe time. > > > > Untill we have this, Torsten's patch is a real improvement, and > > works for non-broken hw/fw. > > > > So I think it should be applied. > > I disagree since it only band-aids the problem and uglifies the driver > in the process. In the immediate term the driver needs to be changed > to read the spi-cs-high property out of the child nodes before > registering the devices. Hm. I thought we agreed that spi-cs-high is not good? Why do you encourage using it then? We'll have to uglify the driver with legacy device-tree handling code. -- Anton Vorontsov email: cbouatmailru@gmail.com irc://irc.freenode.net/bd2