Re: [PATCH v1] regmap: Clarify _regmap_update_bits() 'async' kernel-doc

Mark Brown <[email protected]> Fri, 17 Jul 2026 23:59:14 +0100

Newsgroups	dev.linux.lists.driver-core,org.kernel.vger.linux-kernel
Message-ID	<[email protected]>

On Fri, Jul 17, 2026 at 03:50:31PM -0500, Bjorn Helgaas wrote:

> 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.

> - * If async is true:
> - *
> - * With most buses the read must be done synchronously so this is most useful
> - * for devices with a cache which do not need to interact with the hardware to
> - * determine the current register value.
> + * If async is true, queue an asynchronous write. However, most buses
> + * require synchronous reads, so the read-modify-write cycle will still
> + * block on the read unless the device uses a register cache.  Therefore,
> + * this flag is most useful for cached devices, where the current value can
> + * be read from memory without hardware I/O.

That's...  verbose.  If you want to add a statement that async mode
will be using async I/O then possibly I guess but there's a whole bunch
more there.

signature.asc (application/pgp-signature, 488 B)