McBSP exposure

Can anyone shed any light on how the McBSP hardware is exposed to user
space software? The necessary drivers appear to be loaded (I can see
entries for them under /sys), but I'm not sure how to talk to the
hardware itself. Any help would be greatly appreciated.

- Pat

Can anyone shed any light on how the McBSP hardware is exposed to user
space software? The necessary drivers appear to be loaded (I can see
entries for them under /sys), but I'm not sure how to talk to the
hardware itself. Any help would be greatly appreciated.

The McBSP's are not directly available in userspace AFAIK. The ALSA driver is
most likely the closest thing. All the ALSA driver does is configure the
McBSP to do I2S format, program the CODEC over I2C, and start DMAing out
sound data.

A quick and dirtly hack might be to make a copy of the sound driver and modify
it to use the McBSP you want and have it setup the McBSP the way you need.
You can stub out all the I2C stuff.

What are you trying to do with the McBSP?

-- Hunyue

That's kind of what I figured. Looks like I'll be writing some
drivers... I'm looking to use the McBSP ports to do high speed
communication between the OMAP and some other hardware, so I need the
access that that requires.

- Pat