Hi, On Fri, Aug 03, 2012 at 05:20:48PM +0530, Shubhrajyoti wrote: > On Friday 03 August 2012 03:28 PM, Felipe Balbi wrote: > >> [ 1.496124] spi spi1.0: setup mode 0, 8 bits/w, 6000000 Hz max --> 0 > >> > [ 1.503265] omap2_mcspi omap2_mcspi.1: registered child spi1.0 > >> > > >> > If I modify the board file so that child spi1.0 is registered before > >> > spi1.2, then it starts to work properly: > > that sounds quite odd... Shubhro, have you seen this before on any of > > our platforms ? > > > I havent seen this behaviour may be I didn't have this configuration. > Will try to see if I have any way of recreating and testing the multi cs > on one of our boards. > > BTW I didnt understand why does that matter at all the cs order. > > Aaro, > I am missing what is making the order matter. > What is it that I am missing? With multiple CS you need to configure all CHCONFx regs before any transfers work. This has been seen earlier with context save and restore for PM. See e.g. commit 89c05372d08f3982eeb94d1ea22a60a5eaa8cd6d. A. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
