Received-SPF: pass (google.com: domain of linux-kernel+bounces-95447-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Date: Thu, 7 Mar 2024 11:39:55 +0000
From: Mark Brown <broonie@kernel.org>
To: "Ding, Shenghao" <shenghao-ding@ti.com>
Cc: "andriy.shevchenko@linux.intel.com" <andriy.shevchenko@linux.intel.com>,
	"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
	"perex@perex.cz" <perex@perex.cz>,
	"pierre-louis.bossart@linux.intel.com" <pierre-louis.bossart@linux.intel.com>,
	"13916275206@139.com" <13916275206@139.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"liam.r.girdwood@intel.com" <liam.r.girdwood@intel.com>,
	"bard.liao@intel.com" <bard.liao@intel.com>,
	"mengdong.lin@intel.com" <mengdong.lin@intel.com>,
	"yung-chuan.liao@linux.intel.com" <yung-chuan.liao@linux.intel.com>,
	"Xu, Baojun" <baojun.xu@ti.com>, "Lu, Kevin" <kevin-lu@ti.com>,
	"tiwai@suse.de" <tiwai@suse.de>, "soyer@irl.hu" <soyer@irl.hu>,
	"Baojun.Xu@fpt.com" <Baojun.Xu@fpt.com>,
	"Navada Kanyana, Mukund" <navada@ti.com>
Subject: Re: [EXTERNAL] Re: [PATCH v10] The tas2783 is a smart audio
 amplifier with integrated MIPI SoundWire interface (Version 1.2.1
 compliant), I2C, and I2S/TDM interfaces designed for portable applications.
 An on-chip DSP supports Texas Instruments SmartAmp sp
Message-ID: <73a4416f-4738-485d-aa5a-431c306e7023@sirena.org.uk>
References: <dff90323b41a4e3a8e0e8540fbb32154@ti.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="13xliTJPAqH3UJDZ"
Content-Disposition: inline
In-Reply-To: <dff90323b41a4e3a8e0e8540fbb32154@ti.com>


--13xliTJPAqH3UJDZ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Mar 07, 2024 at 03:56:40AM +0000, Ding, Shenghao wrote:

> > We also try to keep default settings from the silicon except in the most
> > obvious cases, it avoids issues with trying to work out what to set and
> > accomodate different use cases for different systems.

> > If you do need to set non-default values then either just regular write=
s during
> > probe or a regmap patch would do it.

> So, can I remove=20
> ".reg_defaults =3D tas2783_reg_defaults," and tas2783_reg_defaults from t=
he code?

Yes, supplying register defaults is completely optional.  It means we
can't omit default values from cache sync and have to read values back
=66rom the device the first time we read but those tend to be fairly minor
performance impacts.

--13xliTJPAqH3UJDZ
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmXpp4sACgkQJNaLcl1U
h9ARWwf9HcdUwT7bKSmEfdLwH0kU4RDbbNZ1UNhRUruO7+2kcrukoh9IbkAmJHHg
7lUfJI6hks3ir1uTyONS3PVarAim8mvzQfQZmuyu4mrWqHDXcIc/eAuX0mlrV3mv
2h5EPcE050Hi1esdMYb2+ax80Y3VlzPgTgqxkZCFzVNH7Yj4tr2Z3MidZQMlLR2W
vzJ7S+cs2kiq8TFkxMKECTDDEN02cqrC5+KxXPr6vXbQIPP8RP1ouO7wFoLQyvYM
OYSH/d/VB0O47dSfAscE/2aX+kOlBJkViIYHCJUqcUAp0xS5aWXM6il9ihS7tTw1
Awg6yj0cCP6wSRcPknF56znWUqLBCA==
=F7oz
-----END PGP SIGNATURE-----

--13xliTJPAqH3UJDZ--