mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
synced 2026-05-08 08:02:59 -04:00
Merge tag 'regmap-v6.9' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap
Pull regmap updates from Mark Brown: "Just two updates this time around, a rework of max_register handling which enables us to support devices with only one register better and a new test which will be used to validate use of some new SPI optimisations which will be coming in during this merge window" * tag 'regmap-v6.9' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap: regmap: kunit: Add a test for ranges in combination with windows regmap: rework ->max_register handling
This commit is contained in:
@@ -332,6 +332,10 @@ typedef void (*regmap_unlock)(void *);
|
||||
* @io_port: Support IO port accessors. Makes sense only when MMIO vs. IO port
|
||||
* access can be distinguished.
|
||||
* @max_register: Optional, specifies the maximum valid register address.
|
||||
* @max_register_is_0: Optional, specifies that zero value in @max_register
|
||||
* should be taken into account. This is a workaround to
|
||||
* apply handling of @max_register for regmap that contains
|
||||
* only one register.
|
||||
* @wr_table: Optional, points to a struct regmap_access_table specifying
|
||||
* valid ranges for write access.
|
||||
* @rd_table: As above, for read access.
|
||||
@@ -422,6 +426,7 @@ struct regmap_config {
|
||||
bool io_port;
|
||||
|
||||
unsigned int max_register;
|
||||
bool max_register_is_0;
|
||||
const struct regmap_access_table *wr_table;
|
||||
const struct regmap_access_table *rd_table;
|
||||
const struct regmap_access_table *volatile_table;
|
||||
|
||||
Reference in New Issue
Block a user