| commit | b44d48c1ccf70273a91b7d3a920b0b54c3cb314f | |
| author | Lars-Peter Clausen <lars@metafoo.de> | |
| Wed, 16 Nov 2011 19:34:04 +0000 (16 20:34 +0100) | ||
| committer | Mark Brown <broonie@opensource.wolfsonmicro.com> | |
| Thu, 17 Nov 2011 16:51:27 +0000 (17 16:51 +0000) | ||
| tree | 1208c5fa80a8e0b4f14844914afc76914572eb67 | treesnapshot (tar.gz zip) |
| parent | 064d4db11e23949c40b8a2f2f6be11c131b53932 | commitdiff |
regmap: Drop check whether a register is readable in regcache_read
One of the reasons for using a cache is to have a software shadow of a register
which is writable but not readable. This allows us to do a read-modify-write
operation on such a register.
Currently regcache checks whether a register is readable when performing a
cached read and returns an error if it is not. Drop this check, since it will
prevent us from using the cache for registers where read-back is not possible.
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
One of the reasons for using a cache is to have a software shadow of a register
which is writable but not readable. This allows us to do a read-modify-write
operation on such a register.
Currently regcache checks whether a register is readable when performing a
cached read and returns an error if it is not. Drop this check, since it will
prevent us from using the cache for registers where read-back is not possible.
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
| drivers/base/regmap/regcache.c | diffblobblamehistory |