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

Merge remote-tracking branch 'regmap/fix/debugfs' into regmap-linus

2013-06-03T17:07:38Z

regmap: rbtree: Fixed node range check on sync

2013-06-01T19:10:05Z

A node starting before the minimum register is no reason to reject it, since its end could be in range. The check for the end already exists two lines lower, so we can just remove the incorrect check. Signed-off-by: Maarten ter Huurne Signed-off-by: Mark Brown

regmap: regcache: Fixup locking for custom lock callbacks

2013-05-23T16:02:14Z

The parameter passed to the regmap lock/unlock callbacks needs to be map->lock_arg, regcache passes just map. This works fine in the case that no custom locking callbacks are used since in this case map->lock_arg equals map, but will break when custom locking callbacks are used. The issue was introduced in commit 0d4529c5("regmap: make lock/unlock functions customizable") and is fixed by this patch. Signed-off-by: Lars-Peter Clausen Signed-off-by: Mark Brown

regmap: debugfs: Check return value of regmap_write()

2013-05-12T14:57:48Z

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

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

2013-04-16T15:05:50Z

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

2013-04-16T15:05:48Z

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

2013-04-16T15:05:46Z

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

2013-04-16T15:05:44Z

regmap: don't corrupt work buffer in _regmap_raw_write()

2013-04-16T15:05:03Z

_regmap_raw_write() contains code to call regcache_write() to write values to the cache. That code calls memcpy() to copy the value data to the start of the work_buf. However, at least when _regmap_raw_write() is called from _regmap_bus_raw_write(), the value data is in the work_buf, and this memcpy() operation may over-write part of that value data, depending on the value of reg_bytes + pad_bytes. At least when using reg_bytes==1 and pad_bytes==0, corruption of the value data does occur. To solve this, remove the memcpy() operation, and modify the subsequent .parse_val() call to parse the original value buffer directly. At least in the case of 8-bit register address and 16-bit values, and writes of single registers at a time, this memcpy-then-parse combination used to cancel each-other out; for a work-buffer containing xx 89 03, the memcpy changed it to 89 03 03, and the parse_val changed it back to 89 89 03, thus leaving the value uncorrupted. This appears completely accidental though. Since commit 8a819ff "regmap: core: Split out in place value parsing", .parse_val only returns the parsed value, and does not modify the buffer, and hence does not (accidentally) undo the corruption caused by memcpy(). This caused bogus values to get written to HW, thus preventing e.g. audio playback on systems with a WM8903 CODEC. This patch fixes that. Signed-off-by: Stephen Warren Signed-off-by: Mark Brown

Merge tag 'v3.9-rc7' into regmap-cache

2013-04-16T15:02:41Z

Linux 3.9-rc7