From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C2C2CC34022 for ; Mon, 17 Feb 2020 23:11:18 +0000 (UTC) Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 4D26B206E2 for ; Mon, 17 Feb 2020 23:11:18 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alsa-project.org header.i=@alsa-project.org header.b="aR7cBw2a" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4D26B206E2 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=atomide.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=alsa-devel-bounces@alsa-project.org Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id ABDA683D; Tue, 18 Feb 2020 00:10:26 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz ABDA683D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1581981076; bh=gvVCL1zeZJbEjdRi9e8deBGMBO/B5k4rvAaCqBdbGRA=; h=Date:From:To:Subject:References:In-Reply-To:Cc:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=aR7cBw2auXxSROrttmiETEXCaJeadlYHpdqtGV0uYuw/ISRgvjWK3mS/qDyaB9Be5 oEz6HwcrcrVs07nnGufxiAyCCTaelPt1En3s/QZPCseuo2r8lwvU2msJNtV3ctKv4/ 2nwfCaswE36206BlovlYPiOWo2IK5eklxrF8QAYk= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 39907F8015E; Tue, 18 Feb 2020 00:10:26 +0100 (CET) Received: by alsa1.perex.cz (Postfix, from userid 50401) id EBD4EF80172; Tue, 18 Feb 2020 00:10:23 +0100 (CET) Received: from muru.com (muru.com [72.249.23.125]) by alsa1.perex.cz (Postfix) with ESMTP id 978C7F800B6 for ; Tue, 18 Feb 2020 00:10:06 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 978C7F800B6 Received: from atomide.com (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id 8890B8087; Mon, 17 Feb 2020 23:10:48 +0000 (UTC) Date: Mon, 17 Feb 2020 15:10:01 -0800 From: Tony Lindgren To: Peter Ujfalusi Subject: Re: [PATCH] ASoC: ti: Allocate dais dynamically for TDM and audio graph card Message-ID: <20200217231001.GC35972@atomide.com> References: <20200211171645.41990-1-tony@atomide.com> <20200212143543.GI64767@atomide.com> <346dfd2b-23f8-87e0-6f45-27a5099b1066@ti.com> <20200214170322.GZ64767@atomide.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: alsa-devel@alsa-project.org, linux-omap@vger.kernel.org, Kuninori Morimoto , Aaro Koskinen , linux-kernel@vger.kernel.org, Merlijn Wajer , Takashi Iwai , Liam Girdwood , Mark Brown , Pavel Machek , Sebastian Reichel , "Arthur D ." , Jarkko Nikula X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" * Peter Ujfalusi [200217 12:10]: > On 14/02/2020 19.03, Tony Lindgren wrote: > > But right now in droid4 voice call case mcbsp is just the i2s transport, > > and everything happens betwee the modem and the cpcap pmic. > > Iow you don't need McBSP DAI at all. If you would have added the dummy > codec to McBSP !3 and use that, it would work in a same way, or to DMIC > or McPDM... > > The McBSP ops are NULL for the dummy dai, so McBSP is turned off. Hmm yeah I don't know if the cpcap codec on the same mcbsp needs mcbsp for voice call. According to Sebastian sounds like mcbsp can be idle at that point. But what about capture of voice call at the mcbsp from the TDM slot? In that case mcbsp would be active. > >>>> I know it was discussed, but can not find the mail: > >>>> Can you brief again on the audio connection? > >>> > >>> Below is a link to a mailing list thread where Sebastian describes > >>> the audio connection: > >>> > >>> https://lkml.org/lkml/2018/3/28/881 > >> > >> Thanks! > >> > >>>> Do you have branch with working code? > >>> > >>> Yeah I have slightly older set of the patches in my droid4-pending-v5.5 > >>> kernel.org git branch with voice calls working. > >> > >> I think I should put my droid4 out and try to get it working... > >> Do you have a link for dummies to follow to get started? ;) > > > > Probably the easiest one to use right now is the Maemo-leste devuan based > > test image using v5.5 kernel + modem and audio patches: > > > > https://leste.maemo.org/Motorola_Droid_4 > > > > Just use a decent speed micro-sd card rated "a1" for example. > > Cool. Now I can dual boot the droid4 :D > I needed to rewrite the /etc/shadow to get a known root password so I > can log in. Not sure if you mean password for the droid4-kexecboot or the Linux distro you installed.. But for droid4-kexecboot, you can configure it to automatically download new kernels over wlan. There's some info on the machine specific password and how to configure wlan in the droid4-kexecboot buildroot commits here: https://github.com/tmlind/buildroot/commits/droid4-kexecboot-2017.11 > Wifi is up, so in theory I can scp kernel/dtb to /boot/boot/ and update > the /boot/boot/boot.cfg to boot my kernel, right? Yeah you can update kernels and modules over wlan from the distro(s) you have configured, and also from droid4-kexecboot as above. And note that kexecboot looks for a boot/boot.cfg file to use on every usable parition it finds and uses all the found entries based on the priority configured for the boot.cfg entry. Regards, Tony