Received-SPF: pass (google.com: domain of linux-kernel+bounces-102023-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
Date: Wed, 13 Mar 2024 16:46:04 +0000
From: Mark Brown <broonie@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	Ansuel Smith <ansuelsmth@gmail.com>
Subject: Re: [PATCH 5.15 72/76] regmap: allow to define reg_update_bits for
 no bus configuration
Message-ID: <6274f1ce-f2e0-414b-b9a9-bf2840fefd90@sirena.org.uk>
References: <20240313164223.615640-1-sashal@kernel.org>
 <20240313164223.615640-73-sashal@kernel.org>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="cjF8jBOhLBvTK2G3"
Content-Disposition: inline
In-Reply-To: <20240313164223.615640-73-sashal@kernel.org>


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

On Wed, Mar 13, 2024 at 12:42:19PM -0400, Sasha Levin wrote:
> From: Ansuel Smith <ansuelsmth@gmail.com>
>=20
> [ Upstream commit 02d6fdecb9c38de19065f6bed8d5214556fd061d ]
>=20
> Some device requires a special handling for reg_update_bits and can't use
> the normal regmap read write logic. An example is when locking is
> handled by the device and rmw operations requires to do atomic operations.
> Allow to declare a dedicated function in regmap_config for
> reg_update_bits in no bus configuration.

This is fairly clearly new functionality?

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

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

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmXx2EsACgkQJNaLcl1U
h9DU7wf8Cc9vW6X2/usR4C76o8n6h/sawjjlFC4FnswhsVx8SShR2YdDzOsdRCiK
r6SpKfi4Apx/anRoZ8Sc67tp0AY43NKh0hCUwiNsmhTDWoSHQ4i6NPgsHJNIDyyu
YCH/I6dPidoN3yzs6pBbrwHJKkMMRim5kjZbfgAZLfqV3nWHEDTkCF+EipuhyE4T
henmSMRPDdkfEIEe4zG6aHWr/9b9uG/XOdZ5W32iCFNNpmvMZ0X76KtYTALV0b9q
braOwEgoFBEmN2KQvVEqd5icIortuQhD1J9PoJ0CRmJbdoNGVJ+9RzAE8knTf1pg
eXR9f1bFSIg/KWbmoKY7+6w+7ZsRXA==
=yQty
-----END PGP SIGNATURE-----

--cjF8jBOhLBvTK2G3--