linux.git/drivers/base/regmap/regcache.c, branch v3.10-rc2

regmap: cache: Fix format specifier in dev_dbg

2013-04-05T10:28:12+00:00

Fix format specifier in dev_dbg and suppress the following warning

drivers/base/regmap/regcache.c: In function
‘regcache_sync_block_raw_flush’:
drivers/base/regmap/regcache.c:593:2: warning: format ‘%d’ expects
argument of type ‘int’, but argument 4 has type ‘size_t’ [-Wformat]

Signed-off-by: Stratos Karafotis 
Signed-off-by: Mark Brown

regmap: cache: Make regcache_sync_block_raw static

2013-04-05T10:28:12+00:00

regcache_sync_block_raw is used only in this file. Hence make it static.
Silences the following warning:
drivers/base/regmap/regcache.c:608:5: warning:
symbol 'regcache_sync_block_raw' was not declared. Should it be static?

Signed-off-by: Sachin Kamat 
Signed-off-by: Mark Brown

regmap: cache: Write consecutive registers in a single block write

2013-03-30T13:52:36+00:00

When syncing blocks of data using raw writes combine the writes into a
single block write, saving us bus overhead for setup, addressing and
teardown.

Currently the block write is done unconditionally as it is expected that
hardware which has a register format which can support raw writes will
support auto incrementing writes, this decision may need to be revised in
future.

Signed-off-by: Mark Brown 
Reviewed-by: Dimitris Papastamos

regmap: cache: Split raw and non-raw syncs

2013-03-30T13:52:31+00:00

For code clarity after implementing block writes split out the raw and
non-raw I/O sync implementations.

Signed-off-by: Mark Brown 
Reviewed-by: Dimitris Papastamos

regmap: cache: Factor out block sync

2013-03-30T13:52:25+00:00

The idea of holding blocks of registers in device format is shared between
at least rbtree and lzo cache formats so split out the loop that does the
sync from the rbtree code so optimisations on it can be reused.

Signed-off-by: Mark Brown 
Reviewed-by: Dimitris Papastamos

regmap: cache: Factor out reg_present support from rbtree cache

2013-03-30T13:49:17+00:00

The idea of maintaining a bitmap of present registers is something that
can usefully be used by other cache types that maintain blocks of cached
registers so move the code out of the rbtree cache and into the generic
regcache code.

Refactor the interface slightly as we go to wrap the set bit and enlarge
bitmap operations (since we never do one without the other) and make it
more robust for reads of uncached registers by bounds checking before we
look at the bitmap.

Signed-off-by: Mark Brown 
Reviewed-by: Dimitris Papastamos

regmap: cache: Provide a get address of value operation

2013-03-26T21:38:16+00:00

Provide a helper to do the size based index into a block of registers and
use it when reading a value.

Signed-off-by: Mark Brown

regmap: cache: Store caches in native register format where possible

2013-03-04T02:30:28+00:00

This allows the cached data to be sent directly to the device when
we sync it.

Signed-off-by: Mark Brown

regmap: cache: Use regcache_get_value() to check if we updated

2013-03-04T02:30:27+00:00

Factor things out a little.

Signed-off-by: Mark Brown

regmap: cache: Pass the map rather than the word size when updating values

2013-03-04T02:30:27+00:00

It's more idiomatic to pass the map structure around and this means we
can use other bits of information from the map.

Signed-off-by: Mark Brown