Jarkko Nikula wrote:
On Wed, 5 Aug 2009 10:21:49 +0300
Jarkko Nikula <jhnikula@xxxxxxxxx> wrote:
If my analysis is correct, the best solution I can see would be starting McBSP
transfer for one direction only, not both, so the opposite direction can be
started when needed. That requires deeper and wider OMAP knowledge and a
change in omap_mcbsp_start() API though. I am not in a position to deal with
this myself, I'm afraid.
I favor this change. Actually I remember I was thinking shortly to
change API of omap_mcbsp_start and _stop more than year back or so but
didn't find it necessary back then.
I think change will be trivial. Basically two new arguments indicating
are the TX/RX active and let the first/last caller to deal with
sample-rate generator and frame sync activation/de-activation.
I hacked a patch below. Can you test does it help?
Will do tonight (CET).
Now seeing how easy it was (for you ;), I think I could try to follow
that way an modify omap_mcbsp_config() in the same spirit, if you find
it of any use.
Cheers,
Janusz
--
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
