Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp3259925ybt; Mon, 29 Jun 2020 20:48:45 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxsbpAA0W7mt21TI7m1MrEq1eP9a+XPQTgWWmPrGIb9bBSF8Uy3RFsFYwAoKup2WvUkpeJq X-Received: by 2002:aa7:dcc8:: with SMTP id w8mr21441720edu.305.1593488925352; Mon, 29 Jun 2020 20:48:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1593488925; cv=none; d=google.com; s=arc-20160816; b=GRbJ2ophIGkKtTCJyKKGo5kJMhPF4zOPEs0VMDvQ6eckxM+tLMx+MOQGcFEyK3SOJ2 AAwP2wrdLZGw77WqJ7eRL9ZhxGaxPFcqpFRSXsjhGUD6yNtpt1NbRP3nLu1t2votbi/Q Gjq13SA+nhBexV9wr1E1hPhC5x7bKZU5v6Y7WmzRrX3JY3g3ZiUrRol/7bw5Ij5082i1 CjuUht4Vo7no/reBuz72bSAoKGhLQEnIEusOOxlYoCdY+tJOpzUeRiIi9KFoGeVuuMVu 3HWkrYCn2I0Hght6h2B7JCqmWmnF8pb+g3mQcwduXMxqXNESOjmfCyrJs0ykrVibwqkp aZzA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:dkim-signature:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:to:subject:cc; bh=Waf+fRsBa+tnFyTsNnzSNk2rurwJRlEFA5A13c5KFMs=; b=XMfSNQBk+UoxIl8G/xBf2UaRuA6EpSd+HcpcJDO97JaPHF+UA37RhDfLFxSd/gbfOU 0dajQVHu8TOxo9dn1IRFuajr/ogA0bu74f19cb8u6NHVYORlbyQrx7OO27rjFwxm63+x A1LsloUV6jinOyNF6NY30fkInPmlUpC9pnVK+M3MUPQzAlWSvjWcfOXnlrAxtONQTGnU BzWqxqxKF/qRhmeNHhkDEFHrhiFUNzAAptIcyfyqknjKCN1VzluR8djqeif0VIVg3XxA PzyEhM0GX0uHNDLyowj1S6YYWc2RuOCnsg168wAMGwKoF9ngAOnSugCbldja00Ckdck3 8QyQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=qwFpHH7Q; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id r8si956139edq.393.2020.06.29.20.48.22; Mon, 29 Jun 2020 20:48:45 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=qwFpHH7Q; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728930AbgF3DsN (ORCPT + 99 others); Mon, 29 Jun 2020 23:48:13 -0400 Received: from hqnvemgate24.nvidia.com ([216.228.121.143]:11419 "EHLO hqnvemgate24.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726686AbgF3DsN (ORCPT ); Mon, 29 Jun 2020 23:48:13 -0400 Received: from hqpgpgate102.nvidia.com (Not Verified[216.228.121.13]) by hqnvemgate24.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Mon, 29 Jun 2020 20:46:34 -0700 Received: from hqmail.nvidia.com ([172.20.161.6]) by hqpgpgate102.nvidia.com (PGP Universal service); Mon, 29 Jun 2020 20:48:12 -0700 X-PGP-Universal: processed; by hqpgpgate102.nvidia.com on Mon, 29 Jun 2020 20:48:12 -0700 Received: from [10.25.97.62] (10.124.1.5) by HQMAIL107.nvidia.com (172.20.187.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 30 Jun 2020 03:48:03 +0000 CC: , , , , , , , , , , , , , , , , , , , , Subject: Re: [PATCH v4 10/23] ASoC: simple-card: Wrong daifmt for CPU end of DPCM DAI link To: Kuninori Morimoto References: <1593233625-14961-1-git-send-email-spujar@nvidia.com> <1593233625-14961-11-git-send-email-spujar@nvidia.com> <877dvq1yhy.wl-kuninori.morimoto.gx@renesas.com> <6e27daa5-331e-968b-4027-2e30aeb7d382@nvidia.com> <87o8p1z81b.wl-kuninori.morimoto.gx@renesas.com> From: Sameer Pujar Message-ID: <841ac69f-1c3f-2b13-17f9-6f196811ce52@nvidia.com> Date: Tue, 30 Jun 2020 09:17:59 +0530 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0 MIME-Version: 1.0 In-Reply-To: <87o8p1z81b.wl-kuninori.morimoto.gx@renesas.com> X-Originating-IP: [10.124.1.5] X-ClientProxiedBy: HQMAIL101.nvidia.com (172.20.187.10) To HQMAIL107.nvidia.com (172.20.187.13) Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1593488794; bh=Waf+fRsBa+tnFyTsNnzSNk2rurwJRlEFA5A13c5KFMs=; h=X-PGP-Universal:CC:Subject:To:References:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:X-Originating-IP: X-ClientProxiedBy:Content-Type:Content-Transfer-Encoding: Content-Language; b=qwFpHH7QE9mC28kfCJxAzmZEE6JRNuOHvraL8M+Y1I0zQ2WHYK/Oh8u5rmuHvtNqL GcmVOB6EW9EOlpdfCaH4AOmTYNBxxacg/Aqt2JtYELBNEAWybmjXvu3pfb4AEyqrHY yYntjl5O1xuuT5F/Sh4kN2gK+PEGfeQf+KCl4vnYO0NNbx7GcryFnkzP9t1XgMNp6w +kXre478ipBLf7aA32L6fd0Y6QQeVQ5UhAfx1kBLrlGT0G/1FnvSypYJelewxTlkSP ACpFmiAhdlrKdgWY8KEQGkm7JZP3NEu8oHzSFiQf8DZKRtYw9BWJms99RTFKLDDhT7 ThgNFlWVXU8Ag== Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 6/30/2020 6:26 AM, Kuninori Morimoto wrote: > External email: Use caution opening links or attachments > > > Hi Sameer > >> snd_soc_runtime_set_dai_fmt() { >> ... >> >> if (cpu_dai->component->driver->non_legacy_dai_naming) >> fmt = inv_dai_fmt; >> >> ... >> } >> >> Above flips polarity for 'cpu_dai' if 'non_legacy_dai_naming' flag is set. >> >> 1. Hence example mentioned in the commit message does not work if my 'cpu_dai' >> driver does not have this flag set. > ? > Do you want fo flip it ? or don't flip? > It is for Codec <-> Codec connection. For DPCM links I don't want to flip based on one Codec reference. My goal was to make the binding work for multiple CPU/Codec link. Hence I thought it would be better to explicitly describe the 'Master' DAI. We can eventually get rid of 'codec' argument from simple_dai_link_of_dpcm(). >> 2. While it is true that we consider reference of 'Codec' mode for simple CPU<-> >> Codec DAI links, for DPCM this does not seem flexible. For DPCM links CPU and >> Codec are not directly connected (CPU<->Dummy or Dummy<->Codec). Please >> consider, for example, if the DAI link has multiple CPU/Codecs. Which 'Codec' >> reference needs to be considered? Isn't it better if we explicitly mention which >> DAI we want to operate as 'Master'? > I think Lars-Peter has (had ?) plan for this SND_SOC_DAIFMT_CBx_CFx > flag flexibility ? Yes maybe it is needed for multi CPU/Codec system. > > Thank you for your help !! > > Best regards > --- > Kuninori Morimoto