From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752444AbeC0WWn (ORCPT ); Tue, 27 Mar 2018 18:22:43 -0400 Received: from bhuna.collabora.co.uk ([46.235.227.227]:44602 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752232AbeC0WWl (ORCPT ); Tue, 27 Mar 2018 18:22:41 -0400 Date: Wed, 28 Mar 2018 00:22:37 +0200 From: Sebastian Reichel To: Mark Brown Cc: Pavel Machek , Liam Girdwood , Rob Herring , Tony Lindgren , Lee Jones , Jaroslav Kysela , Takashi Iwai , alsa-devel@alsa-project.org, linux-omap@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, kernel@collabora.com Subject: Re: omap4-droid4: voice call support was Re: [PATCHv5,5/5] ARM: dts: omap4-droid4: add soundcard Message-ID: <20180327222237.wcx2aqznvdrvbaa5@earth.universe> References: <20180223200254.25685-6-sebastian.reichel@collabora.co.uk> <20180322204804.GA26871@amd> <20180322234832.o24ut5ahon46mdu4@earth.universe> <20180323100930.GA21644@amd> <20180323103006.alymgb3ywftb4gek@earth.universe> <20180326141638.GB1450@amd> <20180326155828.ttnduivadob4iqmd@earth.universe> <20180327121441.GH29239@sirena.org.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ohop5liubgppbvc6" Content-Disposition: inline In-Reply-To: <20180327121441.GH29239@sirena.org.uk> User-Agent: NeoMutt/20180223 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --ohop5liubgppbvc6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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: >=20 > > 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: >=20 > 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 =3D SoC running Linux CPCAP =3D Audio codec MDM6600 =3D Baseband WL1285 =3D 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. >=20 > That's just the audio graph card with some hacks for working with a DPCM > based SoC driver set. Ok. -- Sebastian --ohop5liubgppbvc6 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE72YNB0Y/i3JqeVQT2O7X88g7+poFAlq6xCsACgkQ2O7X88g7 +pr4Mw/9H73f8pw44CXjo5tlVFXl5Q1SECW4Rtl7d7ji8UPUi5vVX/AKb+Aai1Ag PW3EzEUuz8qLKgXtb21eTRazQd4ueh6XuzaTucUIhTv/jELr/jt99Sw9xby2loPU UN0X6w/h6Qsfqi2mfaLfsNv/6fTZqKbgCIVEV6eA6rf0W0zcTm3rNMtnuzG7l6z1 iUnPxWXeSBE4gqr6xwn1JQ21QH3R7HCZpsRc1nJA46OnT5D7eg40lOnHOVOH0jD1 erb9Q4R1NdDHDn9iPWQPmmK30gFpKr/etPO+r3PhNysQpoikU3ZfrD2u4626ssiy 6tIRogsxECPWnmHCn89QnQQiI691S7zWlbJnlbPAdU7g1Re1MHZs2o+XQYDPU4bA tf0nVubaQeSI+JyqdY5OnSEJlDp9F089HBnjWJnK9ptror/Zfl5BePG3LtfyWZOB 7QyrQkW4vA4jN6wBuOU+QW//Lt+bEvjZeH8qc2s07Ubp2+cmOdV8Ug6xowfWvH0p rGqG5QW/PYy5UU/60+Qlj0vvyS8GDjJk5f9QgA2vxC8kql21yFzAO2e6rjc5HaCO usnVZ84zflgzH3CIkk5Mt34d54KFvo/tRQJFGir6A/+5dNUVg29JjykDNEaPrn1r 5gtCJ7yvtbfM0yZnTy7oTtfgDRZCCwu1OCLW4sX1HUMC91wkqEI= =mFzH -----END PGP SIGNATURE----- --ohop5liubgppbvc6--