Hi Mark,
On Tue, Mar 27, 2018 at 08:14:41PM +0800, Mark Brown wrote:
On Mon, Mar 26, 2018 at 05:58:28PM +0200, Sebastian Reichel wrote:
My understanding is, that we only need to replace the audio-graph-card driver to something more complex. The VOICE DAI needs to be configured differently based on the use case:
No, this is exactly the sort of use case with multiple DAIs that the graph card is intended to enable over the old simple-card.
Oh nice. So the Droid 4 hardware wiring looks like this (at least according to my understanding):
+----------+ +-------------+ | OMAP4 | | CPCAP | | | | | | [McBSP2] | <-----> | [HiFi DAI] | | | | | | [McBSP3] | <--+--> | [Voice DAI] | | | | | | +----------+ | +-------------+ | +----------+ | +-------------+ | MDM6600 | | | WL1285 | | | | | | | [DAI] | <--+--> | [DAI] | | | | | +----------+ +-------------+
Legend: OMAP4 = SoC running Linux CPCAP = Audio codec MDM6600 = Baseband WL1285 = Bluetooth
Re-reading the audio-graph-card binding document I still don't see how the network (OMAP.McBSP3, CPCAP.Voice, MDM6600, WL1285) is supposed to look like. It seems to expect point-to-point DAI connections.
"audio-graph-card" is not capable of doing this. I was planning to try "audio-graph-scu-card" in combination with adding codecs for the modem and BT to DT. If that does not work we need a Droid 4 specific soundcard driver.
That's just the audio graph card with some hacks for working with a DPCM based SoC driver set.
Ok.
-- Sebastian