Received: by 2002:a25:23cc:0:0:0:0:0 with SMTP id j195csp2021053ybj; Wed, 6 May 2020 09:14:35 -0700 (PDT) X-Google-Smtp-Source: APiQypIxu4k/8bEtvjWCgQy49QXhFirK0QdoMESjTfsWykPhniXNMvOWfx2f6DcbpTn6ZwXX+gI3 X-Received: by 2002:a17:906:7f13:: with SMTP id d19mr8144555ejr.57.1588781674836; Wed, 06 May 2020 09:14:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588781674; cv=none; d=google.com; s=arc-20160816; b=m7dKLpDrmVg6Ec8ydfEkKYofMWY+eHhVTmGXjLZyuba1aM8/0/YyCPdyzMbwhYbNeV qNwB9XIS8CG71sik0phzJlwTaOoFE1wmYsCXH0m5PeMAP+2x/JHoZhWavYvbAFhT7eM1 z8Ylsi8nF3f7BfkYOX/+4SphjJomc/hbz9RPV7q/Jj9rlYO+LfMvZDPEY5iAXTdJg5G/ 2sSRCFu0ox2jzAbS2omraHAsbR4IFcK8u8y33eirV9fyXlg8c1IjGaLtzfmNiItWmkxV /x59X2O1hJVY5tDO1doFSzlSUqw+iItJSgeQErGBQMhEN3ri0rxgGgMi/Ezj65Smm3lw xlew== 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=luEZbp/2pQikNm6FKyeutAkc6bT22MBQsDLNbbelIrA=; b=HwZfClRe69S5N5S+9ykeSp4tg8mDU81R94w7zC4cv6Ip9ONEKz+mwoAa1O5tvPI7II 9xFigc43S8OnNlOAuQv/fRhLQ4lunA2ozgxphEHiPf5vP7cqEoOGe06164Oe76ppt6Kg YLTy9LJ8yNv160FMBWgwNy3nr2HGjtS7uEx//XkspNYUFdizBWN6NdtsH+CkjFh9BB78 YyVKIP1z+KImBju9hsBm1SNMRIQwYA6c9yxpy1R9euGLjR23/ktLY5PyGdBrUN/k9jUt u6ZTL7zqEtrKiBJ9K2O9HaQ2Hbgwv/Jsge799h7HBW+fpbshKz/VlL5+VbdToO92CJPU Pg+w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=a9mOjW6R; 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 c2si1555839ejd.263.2020.05.06.09.14.12; Wed, 06 May 2020 09:14:34 -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=a9mOjW6R; 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 S1730056AbgEFQKK (ORCPT + 99 others); Wed, 6 May 2020 12:10:10 -0400 Received: from hqnvemgate24.nvidia.com ([216.228.121.143]:15094 "EHLO hqnvemgate24.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729425AbgEFQKK (ORCPT ); Wed, 6 May 2020 12:10:10 -0400 Received: from hqpgpgate102.nvidia.com (Not Verified[216.228.121.13]) by hqnvemgate24.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Wed, 06 May 2020 09:08:00 -0700 Received: from hqmail.nvidia.com ([172.20.161.6]) by hqpgpgate102.nvidia.com (PGP Universal service); Wed, 06 May 2020 09:10:10 -0700 X-PGP-Universal: processed; by hqpgpgate102.nvidia.com on Wed, 06 May 2020 09:10:10 -0700 Received: from [10.25.100.73] (172.20.13.39) by HQMAIL107.nvidia.com (172.20.187.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 6 May 2020 16:10:01 +0000 CC: , , , , , , , , , , , , , , , , , , , Subject: Re: Re: [RFC] DPCM for Tegra To: Mark Brown , Jerome Brunet References: <1588250483-10014-1-git-send-email-spujar@nvidia.com> <1jzhalffhh.fsf@starbuckisacylon.baylibre.com> <1jwo5pf7de.fsf@starbuckisacylon.baylibre.com> <20200506155311.GG5299@sirena.org.uk> From: Sameer Pujar Message-ID: <74e724ec-72c9-e06a-cada-85110c9b145b@nvidia.com> Date: Wed, 6 May 2020 21:39:58 +0530 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <20200506155311.GG5299@sirena.org.uk> X-Originating-IP: [172.20.13.39] X-ClientProxiedBy: HQMAIL107.nvidia.com (172.20.187.13) 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=1588781280; bh=luEZbp/2pQikNm6FKyeutAkc6bT22MBQsDLNbbelIrA=; 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=a9mOjW6RuG26hYzX7UOGzVEZDVrreu3mqV6fw12xry5J1FudrZ+vEg9ndnajwE97Q UvxZTMPsQg6LlL2Db0Z+bSoHxp2ygtUeO2JxAJauQRWWKt44llawNCjfCIBKFs3gV9 LWQi1aF3m7ewByj1PsniavquSAbPLxtrLslPRveM122li9gSihnjFuLY6zgfQU7cWR 9q3+wy/DGpzQCGvM4l5dJxVFoXIXiw/xbo1bnfP7ib1tdfL8cHi5vn8CSW7DXzO6k4 FdsOiiYA7EtaQXVOjkZW0TCMFSHgwUH8fBYjN60WgW/unKVFhREP9lKoGw470ibQFw mhwElpSkq9KhQ== Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 5/6/2020 9:23 PM, Mark Brown wrote: > On Wed, May 06, 2020 at 04:47:09PM +0200, Jerome Brunet wrote: >> On Wed 06 May 2020 at 16:12, Sameer Pujar wrote: >>> XBAR currently exports all routing widgets which can be used to >>> interconnect multiple components and thus implements Mux widgets. Fixing >>> the routing paths in driver would limit anyone to try a different >>> combination as per the need, unless driver is modified. >> I did not mean that you should restrict the routing ability of your SoC, >> quite the opposite actually. >> You should just expose it correctly > Yes, it's going to be less effort in the long run if nothing else. This is what below reference tried to achieve in the original series, where all Mux widgets and corresponding kcontrols were exposed. [1] http://patchwork.ozlabs.org/project/linux-tegra/patch/1582180492-25297-6-git-send-email-spujar@nvidia.com/ However it has DAI declarations too, that was mainly because codec-to-codec links were used to connect multiple components. DT would expose all these links (please note that machine driver was not sent as part of the original series). May be with DPCM these additional DAIs can be avoided, but it comes with few challenges highlighted in this RFC patch.