kernel/linux.git/include/linux/regmap.h, branch v3.8-rc4

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

2012-12-11T03:39:32+00:00

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

2012-12-11T03:39:30+00:00

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

2012-12-11T03:39:29+00:00

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

2012-11-21T02:10:31+00:00

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:46+00:00

regmap: make lock/unlock functions customizable

2012-10-17T07:52:02+00:00

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: Allow ranges to be named

2012-10-15T00:59:59+00:00

For more useful diagnostics. Signed-off-by: Mark Brown

regmap: Rename n_ranges to num_ranges

2012-10-15T00:59:59+00:00

This makes things consistent with the rest of the API and is actually what the documentation says. We don't currently have any in tree users so low cost. Signed-off-by: Mark Brown

regmap: irq: Allow users to retrieve the irq_domain

2012-10-15T00:49:23+00:00

This is useful for integration with other subsystems, especially MFD, and provides an alternative API for users that request their own IRQs. Signed-off-by: Mark Brown

regmap: irq: Add mask invert flag for enable register

2012-08-30T18:13:41+00:00

Currently, regmap will write 1 to mask_base to mask an interrupt and write 0 to unmask it. But some chips do not have an interrupt mask register, and only have interrupt enable register. Then we should write 0 to disable interrupt and 1 to enable. So add an mask_invert flag to handle this. If it is not set, behavior is same as previous. If set it to 1, the mask value will be inverted before written to mask_base Signed-off-by: Xiaofan Tian Signed-off-by: Mark Brown