diff options
author | Aidan MacDonald <aidanmacdonald.0x0@gmail.com> | 2022-06-23 22:14:14 +0100 |
---|---|---|
committer | Mark Brown <broonie@kernel.org> | 2022-06-29 18:13:11 +0100 |
commit | ad22b3e98f9430896bd4bd8f4fbff4667f02a0c8 (patch) | |
tree | d30cf70ebd15c61d4794eb61e3c4fec22e00a2e7 /scripts/extract-module-sig.pl | |
parent | 6b0c31747722936101d56e71e809bfd7a6a440b7 (diff) | |
download | linux-ad22b3e98f9430896bd4bd8f4fbff4667f02a0c8.tar.bz2 |
regmap-irq: Remove mask_writeonly and regmap_irq_update_bits()
Commit a71411dbf6c8 ("regmap: irq: add chip option mask_writeonly")
introduced the mask_writeonly option, but it isn't used now and it
appears it's never been used by any in-tree drivers. The motivation
for the option is mentioned in the commit message,
Some irq controllers have writeonly/multipurpose register
layouts. In those cases we read invalid data back. [...]
The option causes mask register updates to use regmap_write_bits()
instead of regmap_update_bits().
However, regmap_write_bits() doesn't solve the reading invalid data
problem. It's still a read-modify-write op like regmap_update_bits().
The difference is that 'update bits' will only write the new value
if it is different from the current value, while 'write bits' will
write the new value unconditionally, even if it's the same as the
current value.
This seems like a bit of a specialized use case and probably isn't
that useful for regmap-irq, so let's just remove the option and go
back to using an 'update bits' op for the mask registers. We can
always add the option back if some driver ends up needing it in the
future.
Signed-off-by: Aidan MacDonald <aidanmacdonald.0x0@gmail.com>
Link: https://lore.kernel.org/r/20220623211420.918875-7-aidanmacdonald.0x0@gmail.com
Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'scripts/extract-module-sig.pl')
0 files changed, 0 insertions, 0 deletions