Re: [PATCH v2] regmap: Clarify regmap_update_bits_base() 'async' kernel-doc
Mark Brown <[email protected]> Tue, 21 Jul 2026 17:18:18 +0100
| Newsgroups | dev.linux.lists.driver-core,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On Tue, Jul 21, 2026 at 10:49:02AM -0500, Bjorn Helgaas wrote: > The kernel-doc for the regmap_update_bits_base() 'async' parameter didn't > actually say what it does. It does? > Reword it to clarify the read-modify-write mechanics: when 'async' is true, > the write is queued asynchronously, but the read will still be synchronous > unless the device uses a register cache. The API here is that we'll use async as much as is supported, there are actually some buses that have a read/modify/write operation in the protocol so if one of them supported async I/O we could use it here (we'd need to plumb that through, but the users shouldn't care).
signature.asc
(application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmpfm8kACgkQJNaLcl1U h9Dg7Qf/TRbrLiq1kk0yMpLXm4Nf1A07iNFC0fnLzqPyA31d7LGISAlDq/7Rk9vD u9Gw+V1y6BjH11Ba22nP9ui2gqo+jsvtIVYSCE1yr+1n0VeANdLldN3inmGqwwR6 5szTevsycTlLSkEoDE2qjBjXQx4JpgPnGQpfwguls2V+EExtLcNVtXcU/9Wqx8yC HAtQxYqowxqJ6Sd0w7NhTS97D2dFdVYXR2cajTyiQgnXBFhvaA+wysh9A9IiNEI3 6Gr7TnexQRVYNLD+t+8RJ7rRTmiwZ85mdTkjwLD/YLM5vQb63YKTmpZJMyZdwvew +yR+6jBQX6AoVNmyUsj/ktUq9HAQPg== =UYIg -----END PGP SIGNATURE-----