On Thu, 19 May 2011 17:58:56 -0700 Steve Calfee <stevecalfee@xxxxxxxxx> wrote: > > I also tried to get as close as I could to the soc/omap/omap3pandora.c > > machine driver with my omap3beaglexm.c machine driver. Specifically in > > the *_hw_params init routines. > > > > But when I start things up (even with the codec disconnected from the > > bclk line), I don't get any movement on the CLK and fsx. And of course > > the dma doesn't send anything. > > > > I have gotten mcbsp1 to work as a slave (sort-of) with Peter's help. I > havent been able to get it to clock as a master. So now I try with > mcbsp3, still no luck. > This very likely sounds that in master mode the master clock to McBSP is missing if there is no DMA running. Did you try to use internal 96 MHz from my example or did you try to use external CLKS what Pandora is using? That CLKS setup in Pandora requires that there is a clock coming to McBSP CLKS pin. But as you got codec slave mode working it seems that pin multiplexing is ok so there is no need to try with master mode. In problematic cases the master mode is a good start since then only McBSP clock setup and pin multiplexing can affect if there are no clock and data signals visible. > And with the mcbsp 4 pins not connected to anything but the scope, I > don't see any bitclock movement. I think others used u-boot to setup the > mcbspx, but has anyone successfully used linux to set up the pins? > Yep, in a couple omap boards. Remember that for kernel based multiplexing the CONFIG_OMAP_MUX=y must be set. -- Jarkko -- 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
