linux/drivers/base/regmap/regmap.c, branch v3.8

regmap: fix small typo in regmap_bulk_write comment

2013-01-22T08:24:12Z

Signed-off-by: Nestor Ovroy Signed-off-by: Mark Brown

Merge remote-tracking branch 'regmap/topic/type' into regmap-next

2012-12-11T03:39:49Z

regmap: introduce tables for readable/writeable/volatile/precious checks

2012-11-21T02:10:31Z

Many of the regmap enabled drivers implementing one or more of the readable, writeable, volatile and precious methods use the same code pattern: return ((reg >= X && reg <= Y) || (reg >= W && reg <= Z) || ...) Switch to a data driven approach, using tables to describe readable/writeable/volatile and precious registers ranges instead. The table based check can still be overridden by passing the usual function pointers via struct regmap_config. Signed-off-by: Davide Ciminaghi Signed-off-by: Mark Brown

Merge branch 'topic/lock' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap into regmap-table

2012-11-21T02:09:46Z

Merge branches 'topic/core' and 'topic/range' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap into regmap-table

2012-11-21T02:08:31Z

regmap: core: Report registers in hex when we can't cache

2012-10-30T13:37:26Z

This seems to be the most common way of reporting register numbers, it's certainly what we do for trace. Signed-off-by: Mark Brown

regmap: Fix printing of size_t variable

2012-10-25T17:55:11Z

val_bytes is of 'size_t', so it should be printed as '%zu'. Fixes the following build warning on x86: drivers/base/regmap/regmap.c:872:4: warning: format '%d' expects argument of type 'int', but argument 5 has type 'size_t' [-Wformat] Signed-off-by: Fabio Estevam Signed-off-by: Mark Brown

regmap: make lock/unlock functions customizable

2012-10-17T07:52:02Z

It is sometimes convenient for a regmap user to override the standard regmap lock/unlock functions with custom functions. For instance this can be useful in case an already existing spinlock or mutex has to be used for locking a set of registers instead of the internal regmap spinlock/mutex. Note that the fast_io field of struct regmap_bus is ignored in case custom locking functions are used. Signed-off-by: Davide Ciminaghi Signed-off-by: Mark Brown

regmap: silence GCC warning

2012-10-15T01:03:19Z

Building regmap.o triggers this GCC warning: drivers/base/regmap/regmap.c: In function ‘regmap_raw_read’: drivers/base/regmap/regmap.c:1172:6: warning: ‘ret’ may be used uninitialized in this function [-Wmaybe-uninitialized] Long story short: Jakub Jelinek pointed out that there is a type mismatch between 'num' in regmap_volatile_range() and 'val_count' in regmap_raw_read(). And indeed, converting 'num' to the type of 'val_count' (ie, size_t) makes this warning go away. Signed-off-by: Paul Bolle Signed-off-by: Mark Brown

regmap: Split raw writes that cross window boundaries

2012-10-15T01:00:00Z

If a block write covers a paged memory region and crosses a window boundary then rather than failing the write split the transfer up into multiple writes, making the whole process more transparent for drivers. Signed-off-by: Mark Brown