[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z4PdP1ZWkd_YgzJF@surfacebook.localdomain>
Date: Sun, 12 Jan 2025 17:18:23 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Javier Carrasco <javier.carrasco.cruz@...il.com>
Cc: Matti Vaittinen <mazziesaccount@...il.com>,
Jonathan Cameron <jic23@...nel.org>,
Lars-Peter Clausen <lars@...afoo.de>, linux-iio@...r.kernel.org,
linux-kernel@...r.kernel.org,
Jonathan Cameron <Jonathan.Cameron@...wei.com>
Subject: Re: [PATCH v2 3/4] iio: light: veml3235: extend regmap to add cache
Tue, Dec 24, 2024 at 11:59:02AM +0100, Javier Carrasco kirjoitti:
> The configuration and ID registers are not volatile and are not affected
> by read operations (i.e. not precious), making them suitable to be
> cached in order to reduce the number of accesses to the device.
...
> static const struct regmap_config veml3235_regmap_config = {
> .name = "veml3235_regmap",
> .reg_bits = 8,
> .val_bits = 16,
> .max_register = VEML3235_REG_ID,
> .val_format_endian = REGMAP_ENDIAN_LITTLE,
> + .rd_table = &veml3235_readable_table,
> + .wr_table = &veml3235_writable_table,
> + .volatile_table = &veml3235_volatile_table,
> + .cache_type = REGCACHE_RBTREE,
Any specific reason why this is NOT a maple tree?
> };
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists