Re: Progress in adding ams-delta support to ASoC?
* Janusz Krzysztofik [090618 14:52]: > Tony Lindgren wrote: >> * Peter Ujfalusi [090618 12:03]: >>> On Wednesday 17 June 2009 17:12:38 ext Janusz Krzysztofik wrote: Janusz Krzysztofik wrote: > After all, it is more and more likely that the problem is not dma, but > mcbsp just not shifting any data for some mysterious reason. I finally did what I should have already done before: learned about dynamic debugging, turned it on and probably got the answer from omap_msbsp_dump_reg(): all mcbsp1 register read operations returned 0x. So it looks like I simply get no acccess to mcbsp1 at all. Now I wonder if I can close this thread with a conclusion that mcbsp1 on opam15xx is simply not yet supported by the mainline kernel that I have based my work on. >>> Hmmm, this is quite unexpected. >>> Can you access to mcbsp2 or 3 registers, or only the mcbsp1 registers >>> are not accessible? >>> One thing that I have noticed is that the McBSP1 (and 3) is under the >>> DSP Public Peripherals, while McBSP2 is under MPU Public Peripherals >>> (in OMAP1510). >>> I have to check it further what this actually means... >> >> Hmmm, do you have the DSP code compiled (and loaded)? >> >> On omap1, DSP needs to be powered and idled before some mcbsp clocks can >> be used. Or at least needs to be powered up. > > AFAICS there is no DSP code in mainline at all, so the answer is no, DSP > was likely not powered up at all. For several weeks I was trying to do > what was impossible :/. But fortunatelly, I have learned a lot ;). We at least used to have code to power and idle the DSP even without the dspgateway compiled in.. Sorry I don't remember the details. But most likely you need to have the dspgateway patch enabled. Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Progress in adding ams-delta support to ASoC?
Tony Lindgren wrote: * Peter Ujfalusi [090618 12:03]: On Wednesday 17 June 2009 17:12:38 ext Janusz Krzysztofik wrote: Janusz Krzysztofik wrote: After all, it is more and more likely that the problem is not dma, but mcbsp just not shifting any data for some mysterious reason. I finally did what I should have already done before: learned about dynamic debugging, turned it on and probably got the answer from omap_msbsp_dump_reg(): all mcbsp1 register read operations returned 0x. So it looks like I simply get no acccess to mcbsp1 at all. Now I wonder if I can close this thread with a conclusion that mcbsp1 on opam15xx is simply not yet supported by the mainline kernel that I have based my work on. Hmmm, this is quite unexpected. Can you access to mcbsp2 or 3 registers, or only the mcbsp1 registers are not accessible? One thing that I have noticed is that the McBSP1 (and 3) is under the DSP Public Peripherals, while McBSP2 is under MPU Public Peripherals (in OMAP1510). I have to check it further what this actually means... Hmmm, do you have the DSP code compiled (and loaded)? On omap1, DSP needs to be powered and idled before some mcbsp clocks can be used. Or at least needs to be powered up. AFAICS there is no DSP code in mainline at all, so the answer is no, DSP was likely not powered up at all. For several weeks I was trying to do what was impossible :/. But fortunatelly, I have learned a lot ;). Thanks, Janusz -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Progress in adding ams-delta support to ASoC?
* Peter Ujfalusi [090618 12:03]: > On Wednesday 17 June 2009 17:12:38 ext Janusz Krzysztofik wrote: > > Janusz Krzysztofik wrote: > > > After all, it is more and more likely that the problem is not dma, but > > > mcbsp just not shifting any data for some mysterious reason. > > > > I finally did what I should have already done before: learned about > > dynamic debugging, turned it on and probably got the answer from > > omap_msbsp_dump_reg(): all mcbsp1 register read operations returned > > 0x. So it looks like I simply get no acccess to mcbsp1 at all. Now I > > wonder if I can close this thread with a conclusion that mcbsp1 on > > opam15xx is simply not yet supported by the mainline kernel that I have > > based my work on. > > Hmmm, this is quite unexpected. > Can you access to mcbsp2 or 3 registers, or only the mcbsp1 registers are not > accessible? > One thing that I have noticed is that the McBSP1 (and 3) is under the DSP > Public Peripherals, while McBSP2 is under MPU Public Peripherals (in > OMAP1510). > I have to check it further what this actually means... Hmmm, do you have the DSP code compiled (and loaded)? On omap1, DSP needs to be powered and idled before some mcbsp clocks can be used. Or at least needs to be powered up. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Progress in adding ams-delta support to ASoC?
On Wednesday 17 June 2009 17:12:38 ext Janusz Krzysztofik wrote: > Janusz Krzysztofik wrote: > > After all, it is more and more likely that the problem is not dma, but > > mcbsp just not shifting any data for some mysterious reason. > > I finally did what I should have already done before: learned about > dynamic debugging, turned it on and probably got the answer from > omap_msbsp_dump_reg(): all mcbsp1 register read operations returned > 0x. So it looks like I simply get no acccess to mcbsp1 at all. Now I > wonder if I can close this thread with a conclusion that mcbsp1 on > opam15xx is simply not yet supported by the mainline kernel that I have > based my work on. Hmmm, this is quite unexpected. Can you access to mcbsp2 or 3 registers, or only the mcbsp1 registers are not accessible? One thing that I have noticed is that the McBSP1 (and 3) is under the DSP Public Peripherals, while McBSP2 is under MPU Public Peripherals (in OMAP1510). I have to check it further what this actually means... > > Thanks, > Janusz -- Péter -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
