[alsa-devel] adding an external dsp under soc-dsp framework
i plan on adding an external dsp which has slimbus interface under soc-dsp framwork. currently i would like to make the following type of connection: CPU->DSP->Codec and as the dsp is an external one (physically seperated from both the CPU and the Codec) i have a difficulty defining how to represent it: do i need to make two entities of the dsp: - one for the BE connection and one for the FE connection and add some internal routing using mixer controls? this will create two devices in the user space which the user application should open? - or is there a way to make one device which is composed of all three blocks?
last small question: as slimbus ports id should be passed how do you suggest a device should share his slimbus port id?
On Mon, Aug 06, 2012 at 12:53:40PM +0000, ziv haziz wrote:
Always CC maintainers on patches.
i plan on adding an external dsp which has slimbus interface under soc-dsp framwork.
You shouldn't be doing this. The soc-pcm code is *purely* about managing the interdependencies between the data DMAed from memory and the external interfaces on a SoC, if you're an off-SoC device then you should be providing a CODEC driver. This is why you're having trouble working out how to fit your driver into the frameworks - they're not designed to do what you're trying to do.
last small question: as slimbus ports id should be passed how do you suggest a device should share his slimbus port id?
Well, the bigger blocker here is that we don't have any Slimbus support in the kernel at the minute. I'm hoping to help push that along at the KS/LPC/LinuxCon conferences at the end of this month.
participants (2)
-
Mark Brown -
ziv haziz