Im getting this output from muxing: MUX: setup AF6_3430_MCBSP3_DX (0xd800216c): 0x0004 -> 0x0000 MUX: setup AE6_3430_MCBSP3_DR (0xd800216e): 0x0004 -> 0x0000 MUX: setup AF5_3430_MCBSP3_CLKX (0xd8002170): 0x0004 -> 0x0000 MUX: setup AE5_3430_MCBSP3_FSX (0xd8002172): 0x0004 -> 0x0000 Is this correct? On Thu, Apr 2, 2009 at 11:27 AM, Ernesto Torres <skullmate@xxxxxxxxx> wrote: > thank you, I'll try it and let you know how it went > > On Thu, Apr 2, 2009 at 10:56 AM, Jarkko Nikula <jhnikula@xxxxxxxxx> wrote: > >> On Thu, 2 Apr 2009 13:20:36 +0300 >> Jarkko Nikula <jhnikula@xxxxxxxxx> wrote: >> >> > > Grrr... cannot find the hack, I'm too keen to delete temporary >> > > hacks. I was >> > pretty sure I had >> > it somewhere. >> > >> > Basically it was adding necessary pin multiplexing configuration into >> > arch/arm/plat-omap/include/mach/mux.h and arch/arm/mach-omap2/mux.c >> > and then using omap_cfg_reg(...) in omap3beagle.c to change pin >> > configuration from >> > GPIOs to McBPS[1 | 3] pins. >> > >> Yes, I found it. Hack attached :-) >> >> Now I don't have here Beagle to test but hack still applies on top of >> linux-omap. Then you will need CONFIG_OMAP_MUX=y and following lines >> into omap3beagle.c or board-omap3beagle.c. >> >> omap_cfg_reg(AF6_3430_MCBSP3_DX); >> omap_cfg_reg(AE6_3430_MCBSP3_DR); >> omap_cfg_reg(AF5_3430_MCBSP3_CLKX); >> omap_cfg_reg(AE5_3430_MCBSP3_FSX); >> >> >> Jarkko >> >> _______________________________________________ >> Alsa-devel mailing list >> Alsa-devel@xxxxxxxxxxxxxxxx >> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel >> >> > > > -- > ___________ > EhTd > > -- ___________ EhTd _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
