Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp1149684ybt; Wed, 1 Jul 2020 20:49:03 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzanW/YKTJzWoQnKoGd1Pac5fZjIVzd4giiGBjeVfa8ydTATqWnqkaefbVZMX/YJls47U4z X-Received: by 2002:aa7:db06:: with SMTP id t6mr28158457eds.369.1593661743808; Wed, 01 Jul 2020 20:49:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1593661743; cv=none; d=google.com; s=arc-20160816; b=0E+tX8ong6ymYDaJBnS/R4UvETHhFvrr4dH20jKch8JTQz0qVvVMByHwdtw3cpDd+l OHmLGsI0E3B8N+VK9kLLfV78ABhEE+NJR0Hqc2zpAYo+usY6LXnZBHXX8u9kMGv7U9uw 4QrZFjpJBpxBKlaVx08OazkP2SNtj1mayL1UmTe2H0ro/hYoRoI3yVWdYNik2RLdNZbR t825R7nCmnWUohReRRCtipKeM8+8O62V2VwcufYUsRi/PNZ3HT8ih0Cs4jQAxInnHdNL hX6Qezv0LN7VuUjypgZEc2AIKlt6PUDxXxXHKz++QHxv2+NndUFdGldoBX86AECREzZ+ ypqQ== 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=Oqf1zdTjnVv4xMqY49vlWn2YQFtjEyzUTTviPf0shsg=; b=dTf1L2mBDJYtbtnXZ8HMXXyuPrKuOUkSNm1g2kd59dwGkA/LrcJp3ZJ3uyRt6R8RGC aGBP1fNE7deeyHi8fF9tQ8H02mZ6R4UKDrnrLdbHvbo+yBMqD3Yv3QrSaJeXs6TwuGCv AtUL3BDZPVK2qZtY2BwVjgMJbng11QkjD5+/3kwzSMkSY/FYRgvl1yTqLL5E991+Pull jmLcMXRXFXyQfmlj8/KV13OsaWjsffFnU3OZHg8sgMfCzmdIzAx98ikoNL+doLjJgDbY +Q5N1bEmI6VZxh+sNfX0ME1dWl7VznOA8nGZHX49HpIYIWvaoP1zg4tmBf/WSDdNdqNn TDxA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=dgbcAyxk; 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 c2si5092400edq.228.2020.07.01.20.48.38; Wed, 01 Jul 2020 20:49:03 -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=dgbcAyxk; 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 S1726245AbgGBDsS (ORCPT + 99 others); Wed, 1 Jul 2020 23:48:18 -0400 Received: from hqnvemgate25.nvidia.com ([216.228.121.64]:8291 "EHLO hqnvemgate25.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725857AbgGBDsR (ORCPT ); Wed, 1 Jul 2020 23:48:17 -0400 Received: from hqpgpgate101.nvidia.com (Not Verified[216.228.121.13]) by hqnvemgate25.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Wed, 01 Jul 2020 20:47:25 -0700 Received: from hqmail.nvidia.com ([172.20.161.6]) by hqpgpgate101.nvidia.com (PGP Universal service); Wed, 01 Jul 2020 20:48:16 -0700 X-PGP-Universal: processed; by hqpgpgate101.nvidia.com on Wed, 01 Jul 2020 20:48:16 -0700 Received: from [10.25.97.252] (10.124.1.5) by HQMAIL107.nvidia.com (172.20.187.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 2 Jul 2020 03:48:06 +0000 CC: , , , , , , , , , , , , , , , , , , , , Subject: Re: [PATCH v4 15/23] ASoC: soc-core: Identify 'no_pcm' DAI links for DPCM To: Kuninori Morimoto References: <1593233625-14961-1-git-send-email-spujar@nvidia.com> <1593233625-14961-16-git-send-email-spujar@nvidia.com> <87h7utytlx.wl-kuninori.morimoto.gx@renesas.com> <9c7871ae-6649-7b0d-4780-c8389c299b04@nvidia.com> <87d05ezqlc.wl-kuninori.morimoto.gx@renesas.com> From: Sameer Pujar Message-ID: <49bac9c1-093c-d353-cef3-c9c3391cc00d@nvidia.com> Date: Thu, 2 Jul 2020 09:18:02 +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: <87d05ezqlc.wl-kuninori.morimoto.gx@renesas.com> X-Originating-IP: [10.124.1.5] X-ClientProxiedBy: HQMAIL105.nvidia.com (172.20.187.12) 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=1593661645; bh=Oqf1zdTjnVv4xMqY49vlWn2YQFtjEyzUTTviPf0shsg=; 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=dgbcAyxkORD4uUkBD9tIkxdAENIWG1QJUhYTAarenLayi6aUtMJzOtPwxqdlX11aH zadPx+3Ks3QUFs89mSsFyx1sNuPJfCReUFPP75q6vJW+qOBg+QxZx48aixd5xqJ0HP NrkRa8ZYVniq52jGPIBJf2+vku+uQc6ZtJp6wxrt6PxWDpw4jns5sINzrMTwUDXZMj gJjX98OC4AmkOxBoWSRJT3mXDfeVcg5WcrP6EKxnJAGNzNN1N3aFZ9EBzgAMEw0qs7 2Pyu7ezIf8iHbyz21lsLDl66vCsP4Dpz0pdQMBC5ZVA21HgkbGGP6J6NOihWIsP+3b YW8wiHW+MBBMg== Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 7/2/2020 6:22 AM, Kuninori Morimoto wrote: > External email: Use caution opening links or attachments > > > Hi Sameer > >>> At least my CPU driver doesn't use component:pcm_construct >>> but is using DAI:pcm_new for some reasons. >>> I'm not sure checking DAI:pcm here is enough, or not... >> OK. If adding DAI:pcm_new above here is not sufficient, then a flag >> can be used to describe FE component? or is there a better >> alternative? > soc_component_is_pcm() is called from simple_dai_link_of_dpcm :: "FE" side. Yes I had to use this on "FE" side only because I wanted to find a real "FE" in FE<->BE and BE<->BE links. Please have a look at patch [23/23] for the sound DT binding I am using. Basically I want to connect multiple components in a chained fashion (FE <-> BE1 <-> BE2 ... ). Some of these BEs can be SoC components like resampler/mixer/mux/de-mux etc., the HW I am using has a cross bar which allows me to select/connect BEs in any order and I am trying to have the same flexibility here. Hence I only want to create PCM devices for real "FE" and trying to use simple-card as much as possible. More details about the HW and problems were discussed in [0]. [0] https://lkml.org/lkml/2020/4/30/519 > I wonder component->driver->non_legacy_dai_naming can't work for you ? I see currently in simple-card driver that, BE<->BE link would be treated as CODEC<->CODEC link if 'non_legacy_dai_naming' flag is set at both ends of BE. Do we need to set this flag for all BE? However I am not sure how this will work out for a BE<->BE DPCM DAI link considering the fact that I want to use chain of components and I guess routing map would get complicated. Also going by the flag name it was not meant to differentiate between a FE and BE? > Thank you for your help !! > > Best regards > --- > Kuninori Morimoto