linux/drivers/base/regmap, branch v3.3

regmap: Fix cache defaults initialization from raw cache defaults

2012-02-15T16:31:32Z

Currently registers with a value of 0 are ignored when initializing the register defaults from raw defaults. This worked in the past, because registers without a explicit default were assumed to have a default value of 0. This was changed in commit b03622a8 ("regmap: Ensure rbtree syncs registers set to zero properly"). As a result registers, which have a raw default value of 0 are now assumed to have no default. This again can result in unnecessary writes when syncing the cache. It will also result in unnecessary reads for e.g. the first update operation. In the case where readback is not possible this will even let the update operation fail, if the register has not been written to before. So this patch removes the check. Instead it adds a check to ignore raw defaults for registers which are volatile, since those registers are not cached. Signed-off-by: Lars-Peter Clausen Signed-off-by: Mark Brown Cc: stable@vger.kernel.org

regmap: Reset cache status when reinitialsing the cache

2012-01-20T13:49:30Z

When we reinitialise the cache make sure that we reset the cache access flags, ensuring that the reinitialised cache is in the default state which is what callers would and do expect given the function name. This is particularly likely to cause issues in systems where there was no cache previously as those systems have cache bypass enabled, as for the wm8994 driver where this was noticed. Signed-off-by: Mark Brown

Merge branch 'regmap/irq' into regmap-next

2011-12-05T16:21:05Z

regmap: Add irq_base accessor to regmap_irq

2011-12-05T16:13:31Z

Allows devices to discover their own interrupt without having to remember it themselves. Signed-off-by: Mark Brown

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

2011-12-05T13:18:50Z

regmap: Allow drivers to reinitialise the register cache at runtime

2011-12-05T13:17:36Z

Sometimes the register map information may change in ways that drivers can discover at runtime. For example, new revisions of a device may add new registers. Support runtime discovery by drivers by allowing the register cache to be reinitialised with a new function regmap_reinit_cache() which discards the existing cache and creates a new one. Signed-off-by: Mark Brown

regmap: Add trace event for successful cache reads

2011-11-30T20:51:09Z

Currently we only trace physical reads, there's no instrumentation if the read is satisfied from cache. Signed-off-by: Mark Brown

regmap: Allow regmap_update_bits() users to detect changes

2011-11-29T20:15:50Z

Some users of regmap_update_bits() would like to be able to tell their users if they actually did an update so provide a variant which also returns a flag indicating if an update took place. We could return a tristate in the return value of regmap_update_bits() but this makes the API more cumbersome to use and doesn't fit with the general zero for success idiom we have. Signed-off-by: Mark Brown

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

2011-11-28T18:52:24Z

regmap: Report if we actually handled an interrupt in regmap-irq

2011-11-28T18:51:57Z

While the IRQ core doesn't currently support shared threaded interrupts that's no reason for drivers not to do their bit and report IRQ_NONE when they don't get an interrupt. This allows the core spurious/wedget interrupt detection support to do its thing. Signed-off-by: Mark Brown