Received: by 2002:a05:6602:2086:0:0:0:0 with SMTP id a6csp3445803ioa; Tue, 26 Apr 2022 03:54:15 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy42PcM75Y9AMaZnJoXT4NV3zNF1Z95NvOjz12tCjMf4duGBpSYUMdqK0/r08KQa+ti+0Oi X-Received: by 2002:a17:90a:3c84:b0:1ca:56c8:5793 with SMTP id g4-20020a17090a3c8400b001ca56c85793mr26385170pjc.226.1650970454802; Tue, 26 Apr 2022 03:54:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1650970454; cv=none; d=google.com; s=arc-20160816; b=fKMi6yVVn7yAWRx8SzBZwC3wCtWTLIeAflfbYki3FshA1aN3Mhyv3AsNlodiw/J7qm Jtxj916XhO+KsNvFTy4jx9Nf+vLoRkSwx2aTWUsBzefoJ3M3f7nYuSgt8rJJrXPA1iJJ JC48LEwWIh+6M8H8qUkxNTdKpirf1KRX08FWabDRgpbEDLE0i9sf3jQLuHS3Ii29YoIX W0l+/cjhXq6TL5Rw1IZvH9wPvOT+stxUV/ckT1gfu4aeCTTxhPCKpVBTvmu7c+lfzz7J iO4qxj2mH3jV+cH5//mPwS0uE3TfsNhxehdKsr40BIDQbd9j3Azab4dgsrM2eE/PG1NZ osbA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=yLCv6FewgWJlHLlMN/fEyi9qB4NATfbJd/f8gLX6fKs=; b=GEq8ZOvvboMH0FhLkihZi1TMnky1YFdHQysVWvhyEXCR7vyFBRFOzeSwQXSkoPrCDJ kGSAtFrvCaIdWPxqdUJy5huqPWj3lOnSTw1d9pehrGZxOQEAqUNQRxWoGfAeq3f9p7kS eAjWpOpaCgvsg+QocS003+//S9sBZKRdqmnHls1XEi+rOXZR426Gn8+r74vHt66puxIk 1+uYtuBW6M+sAHO0b0iQz8PYKg20qSKknYqwPn9qzwoxJ1hhz45duB6hEZysVIS4QFYY sTn+bxh6Q5sXeB9ps59vLXa0sOM6XXva3oGY/VbXkfk0NKk0J4XiMcY64sDILzLp4A7B TEnA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=jA1s0kuS; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id s142-20020a632c94000000b0039da9a719ddsi19388365pgs.18.2022.04.26.03.54.00; Tue, 26 Apr 2022 03:54:14 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=jA1s0kuS; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238251AbiDYNuE (ORCPT + 99 others); Mon, 25 Apr 2022 09:50:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54544 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230034AbiDYNuB (ORCPT ); Mon, 25 Apr 2022 09:50:01 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E406C13DF7; Mon, 25 Apr 2022 06:46:56 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 85D67615BA; Mon, 25 Apr 2022 13:46:56 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 35886C385A4; Mon, 25 Apr 2022 13:46:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1650894415; bh=cnaPGcH4wGvOkYGwNrD3V8c2ZplgPQyr3KVOqiR+sJ8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=jA1s0kuSSuLQE2bT8lYq2PPV04y02D7wZ8T7PdJUl0+pIvcQzNQnEkHrKO/VLIdgb 2m1RDD1iU6fclgB2yt1Cje9fNi0pxMXo9Afs/v7KguWBId5ui/5gXhFdyMHHH8XIRQ bOftIFstCxWmSjJHS3lBhWNxeu4gXmX0XXBJbCx4vqu2bqlpY3wW9SyWSPVIMDLzeT BX2eE8JH6eajiA+UVHxwl22jmU3zQixvCowQ3xKibegjrsmrkShuAPa1Y4rNBOa55o S2JjJmmeYwllM2K1/vcfweK03kM9wQnTiueeD9g3slFnmadjGloilFczuOGhiju7TU mzZXT8lv+7Cdw== Date: Mon, 25 Apr 2022 14:46:49 +0100 From: Mark Brown To: Martin =?utf-8?Q?Povi=C5=A1er?= Cc: Martin =?utf-8?Q?Povi=C5=A1er?= , Liam Girdwood , Rob Herring , Krzysztof Kozlowski , Jaroslav Kysela , Takashi Iwai , alsa-devel@alsa-project.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Mark Kettenis , Hector Martin , Sven Peter Subject: Re: [RFC PATCH 3/5] HACK: ASoC: Tolerate N-cpus-to-M-codecs links Message-ID: References: <20220331000449.41062-1-povik+lin@cutebit.org> <20220331000449.41062-4-povik+lin@cutebit.org> <904EB8A1-5561-4555-8030-B85703E24F2E@cutebit.org> <9F8BCBA8-5EE3-4F87-9518-91CB7AB4E077@cutebit.org> <4CF6B0A7-F218-4798-BB21-18D563309D5C@cutebit.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="V5YMDCcjWGsw/lIg" Content-Disposition: inline In-Reply-To: <4CF6B0A7-F218-4798-BB21-18D563309D5C@cutebit.org> X-Cookie: An apple a day makes 365 apples a year. X-Spam-Status: No, score=-7.7 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --V5YMDCcjWGsw/lIg Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 25, 2022 at 03:11:14PM +0200, Martin Povi=C5=A1er wrote: > > On 25. 4. 2022, at 14:55, Mark Brown wrote: > > I am surprised that doesn't otherwise explode TBH - at the very least > > I'd expect it to show two PCMs to userspace which if I'm understanding > > your description correctly isn't really what's going on. > I fill in a single snd_soc_dai_link, it exposes a single PCM and works > like a charm. That is as long as I patch the playback/capture check in > question. > I read that to be the clear intention of ASoC code: a DAI link becomes > one snd_soc_pcm_runtime. Yes, so long as you boil it down to a single link it works fine but the bit on top of the binding where you tie the two CPU DAIs to what is actually exposed is all in code. The reason this stuff isn't filled in is that connecting the thing that applications see to the physical links isn't at all obvious and needs at least some driver sitting in the middle to make the links - I'd imagine there's a DSP sitting there which probably has quite a bit of flexability about how the various hardware components available are actually related. This makes figuring out what to do with the relationship between the multiple CPU DAIs hard. --V5YMDCcjWGsw/lIg Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmJmpkkACgkQJNaLcl1U h9C/GQf+OjJGWvlH5dhjAe5s8YfzoSM40Z2KmKGWDIcK8eWx0PFyUNUbga/WyQfu /DZp541i+iDNis3n38axj/4MJkr6Fv79zkvqkXcDoJRwvHPN4pUnWuayW4R9dzOD RCziMyqgTtA4L9aCBI3OW6j6iDy5giYhk1ZGom2XGghdavCGptkPmXnWebvjTP1u 86P8dTNBR5iyhFdxG6ZQXgGOoj+HDKc7wd8GeKmUErNfgDPJhLKe4+2CPyX/l8cp 7yO9I0+h4S/GIOyCjybXqlEfCKLSYk6S7rf+grBcXOfQlb+AUo27WCSS1E2AvH/P /5nrS6m379X9QqI4rhcsEJOfwZo+1w== =/H/Q -----END PGP SIGNATURE----- --V5YMDCcjWGsw/lIg--