Received: by 2002:a05:7412:8d10:b0:f3:1519:9f41 with SMTP id bj16csp6648926rdb; Fri, 15 Dec 2023 04:55:13 -0800 (PST) X-Google-Smtp-Source: AGHT+IEsIDjnw+ElMdrUQJH+JJUDvvMrTdlVQ9wPUCBIrTJud903OBXZHwvLl222JeTBssEa72Hh X-Received: by 2002:a0c:d808:0:b0:67a:c81a:368e with SMTP id h8-20020a0cd808000000b0067ac81a368emr13939210qvj.32.1702644913259; Fri, 15 Dec 2023 04:55:13 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1702644913; cv=none; d=google.com; s=arc-20160816; b=YnlxpvcyiSTrUKajCXAgz8O8+w0V5LzDSQDabhDLU4cWyxDJ9f0z66hXa+5O3NaDId 5b5XPt4X7jvH+6DBUKEPzRS2oGc/Jab33Xao5/zVrr+2LCWyGNmiuNjWJYpPh+AYXrBg DnABU+6X5ulFsfm8M28Ry98U2YKFon6EM/N3Hgn9VXW6q9q4zE7Q26/4pF+qvp1s3a9C Dxj2yFAUxiknljzlKNGaUZdr1wZg8cee8oDqxbR6+/FcKhRizVNUqf5RFhh1Pc7IDKD9 q02WcFkOlVtyEA3wqyGS0C9bmzbG1kBo11GHCOU7zB1ZvD5+lHqq0Vu1YQVXLqgshHRN SUpA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=in-reply-to:content-disposition:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:references:message-id:subject:cc :to:from:date:dkim-signature; bh=NxhvquCaP0WNGuKRIQKHOPeSir63MJp91R0Pw5xQ8hU=; fh=nmaIcstL9sV5Nq4RMhFU+6bYjxHdBWKpDsuXM6BleVE=; b=OBhIYUuBfLeVJFLV4qsiaNIT7q5eqsoti0rEMNPteKqgbaJFeH0qwYA3bUfHtJkHeG UV6HStMkAOYED3thbl56UePVxukENE68rzfigqaWjUQjfc0X+IIYpsKl3qPibkRIMaMZ E4T55kmeayJdWfULMgXUS8uSs3INrAJqFrDxc4D33Pndj0OrtP0NX9Vdat410Vx92Sqh H7fUNjTZGEAa5YvfjBTJc4ByBVQ2uAKus3ImPF9V8ruC7rhNvRNL7Vg3pRl9fRGQ3cQz +dcdaHgSBfiCqizFOqAK2BcK+gCckr4viwEDUQPdy7G1STyYL71b1J6fab1z7UKFQ6qt 9AGQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=QCEG2K7I; spf=pass (google.com: domain of linux-kernel+bounces-959-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-959-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from ny.mirrors.kernel.org (ny.mirrors.kernel.org. [2604:1380:45d1:ec00::1]) by mx.google.com with ESMTPS id a9-20020a0cb349000000b0067f07abb2b4si23954qvf.29.2023.12.15.04.55.13 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 15 Dec 2023 04:55:13 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-959-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=QCEG2K7I; spf=pass (google.com: domain of linux-kernel+bounces-959-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-959-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ny.mirrors.kernel.org (Postfix) with ESMTPS id 066411C2312B for ; Fri, 15 Dec 2023 12:55:13 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 808F42D056; Fri, 15 Dec 2023 12:55:07 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="QCEG2K7I" X-Original-To: linux-kernel@vger.kernel.org Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B92F02D033 for ; Fri, 15 Dec 2023 12:55:06 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 35C4EC433C7; Fri, 15 Dec 2023 12:55:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1702644906; bh=GiYX2dByBC38vzkmfO+cvnHpKmaS1UwkM/jOuD6+MsE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=QCEG2K7IiXiNW0BI/LX22IFcDdFusaB0moxk4gM3tIFE17Vusj49rkITKod49BNzQ OxVv+oG3u0n7o5+DW57hrGNpYug3BGRf6cp3SxPegL+ozSQEOv4K+Ci6/93SRG35Kd vxueSxAxnbKat/x7UDCu3vElVp5A1abi0elOXYrB1mBPR/pQ3oCAOcr1fTdZcnAGTg tqJS3Eci1X+DdZhiSG+dUXr6c3hgEmGpQnlzCPqg2p/lyqjLXVH07YiOluruNjr4e2 ll/xiGi5OPW8PNKJ/2ORIQ4Xg/xHTSON/76jxQI3hp0romU3I8wGDHQACqGc3SqF4O kN9Y2xYa6KH0Q== Date: Fri, 15 Dec 2023 12:55:00 +0000 From: Mark Brown To: Gergo Koteles Cc: Shenghao Ding , Kevin Lu , Baojun Xu , Jaroslav Kysela , Takashi Iwai , Liam Girdwood , linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org Subject: Re: [PATCH 03/16] ASoC: tas2781: disable regmap regcache Message-ID: <5b2eb7eb-761e-406d-8d55-b7ea8cddefa8@sirena.org.uk> References: <21a183b5a08cb23b193af78d4b1114cc59419272.1701906455.git.soyer@irl.hu> <0b836c10-b21b-4275-8dd0-254dd5467497@sirena.org.uk> <47097f19398808b64f4cc87c2a3c7cc462fb2416.camel@irl.hu> <5f3f0306-799f-4f3b-9e05-fbd300c59d5d@sirena.org.uk> <9a2b85a8a19e002093e2471a97850d26e335900f.camel@irl.hu> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="shU18Ze4Jixd/qwv" Content-Disposition: inline In-Reply-To: <9a2b85a8a19e002093e2471a97850d26e335900f.camel@irl.hu> X-Cookie: PARDON me, am I speaking ENGLISH? --shU18Ze4Jixd/qwv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Dec 15, 2023 at 02:17:01AM +0100, Gergo Koteles wrote: > On Thu, 2023-12-07 at 22:39 +0000, Mark Brown wrote: > > On Thu, Dec 07, 2023 at 10:12:13PM +0100, Gergo Koteles wrote: > > > On Thu, 2023-12-07 at 20:36 +0000, Mark Brown wrote: > > > > The code creates the impression that writing to one tas2781 writes to > > > > all of them, is that not the case? > > > Yes, the tasdevice_* functions, but the regcache_sync doesn't know > > > this. > > So this syncing is done in software not hardware? My understanding was > > that this was a hardware thing. > If you mean that the amplifier does not know that there are several > programs or configurations or profiles, but only runs the current one, > yes. No, I mean that the amplifiers don't talk to each other at a hardware level and the grouping is all in software. --shU18Ze4Jixd/qwv Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmV8TKQACgkQJNaLcl1U h9BTCwf+Pa4K2iMEqoqOz+oegGtyQpvdi/qVCmxb4ZTXaxolUdaQy2PaXjRLd8HX JvKRqh83icW7itxjaoT9Agm9u5YYtIitbHZa0EZgFPu7W7wbssEMC/PJDVde1FcF roRv64St87ObvZdagd/XFu2ZGqmFkVbRuvwsiDMAL6XImcCmZPixV8rT73+Vef+U FmJ7f31B6G07xb2nO5MklywF98z97eXc75Rg8QDleMNPe4/H6bDyLbfTDUF5DAnG vIzC6Qxm5+dXLLa2V5yZhY0xWOCNJDrmwv7bv0c9M74QigdTTtsI/JmOIj0yJjg/ m5ZFOlNVFJgDi9IzWD5gcsxzhvTymA== =DJ8M -----END PGP SIGNATURE----- --shU18Ze4Jixd/qwv--