29 Oct, 2013
5 commits
-
Add basic support for the System Power Management Interface (SPMI) bus.
This is a simple implementation which only implements register accesses
via the Extended Register Read/Write Long commands.Signed-off-by: Josh Cartwright
Signed-off-by: Mark Brown
14 Oct, 2013
1 commit
-
New API regmap_multi_reg_write() is defined that allows a set of reg,val
pairs to be written to a I2C client device as one block transfer from the
point of view of a single I2C master system.A simple demonstration implementation is included that just splits the
block write request into a sequence of single register writes.The implementation will be modified later to support those I2C clients
that implement the alternative non-standard MULTIWRITE block write mode
so to achieve a single I2C transfer that will be atomic even in multiple
I2C master systems.Signed-off-by: Anthony Olech
Signed-off-by: David Dajun Chen
Signed-off-by: Mark Brown
09 Oct, 2013
1 commit
-
Make it easier for drivers to include single register writes in
asynchronous sequences by providing async versions of the write
and update bits operations. The update bits operations are only
likely to be effective when used with devices that have caches
but this is common enough to be useful.Signed-off-by: Mark Brown
21 Sep, 2013
1 commit
-
Add helper macro to set the min and max value of the register range.
This is useful when initialising the register ranges of the device like
static const struct regmap_range readable_ranges[] = {
regmap_reg_range(DEVICE_REG0, DEVICE_REG10),
};Signed-off-by: Laxman Dewangan
Signed-off-by: Mark Brown
17 Sep, 2013
2 commits
-
Current Linux kernel is supporting regmap_field method
and it is very useful feature.
It needs one regmap_filed for one register access.OTOH, there is multi port device which
has many same registers in the market.
The difference for each register access is
only its address offset.Current API needs many regmap_field for such device,
but it is not good.
This patch adds new regmap_fileds API which can care
about multi port/offset access via regmap.Signed-off-by: Kuninori Morimoto
Signed-off-by: Mark Brown -
Current regmap_field is supporting read/write functions.
This patch adds new update_bits function for it.Signed-off-by: Kuninori Morimoto
Signed-off-by: Mark Brown
04 Sep, 2013
1 commit
-
Pull regmap updates from Mark Brown:
"A quiet release for regmap, some cleanups, fixes and:- Improved node coalescing for rbtree, reducing memory usage and
improving performance during syncs.
- Support for registering multiple register patches.
- A quirk for handling interrupts that need to be clear when masked
in regmap-irq"* tag 'regmap-v3.12' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap:
regmap: rbtree: Make cache_present bitmap per node
regmap: rbtree: Reduce number of nodes, take 2
regmap: rbtree: Simplify adjacent node look-up
regmap: debugfs: Fix continued read from registers file
regcache-rbtree: Fix reg_stride != 1
regmap: Allow multiple patches to be registered
regmap: regcache: allow read-only regs to be cached
regmap: fix regcache_reg_present() for empty cache
regmap: core: allow a virtual range to cover its own data window
regmap: irq: document mask/wake_invert flags
regmap: irq: make flags bool and put them in a bitfield
regmap: irq: Allow to acknowledge masked interrupts during initialization
regmap: Provide __acquires/__releases annotations
01 Sep, 2013
1 commit
15 Aug, 2013
1 commit
-
The use of WARN_ON() needs the definitions from bug.h, without it
you can get:include/linux/regmap.h: In function 'regmap_write':
include/linux/regmap.h:525:2: error: implicit declaration of function 'WARN_ONCE' [-Werror=implicit-function-declaration]Signed-off-by: Kevin Hilman
Signed-off-by: Mark Brown
Cc: stable@vger.kernel.org
07 Aug, 2013
1 commit
-
regmap.h requires linux/err.h if CONFIG_REGMAP is not defined. Without it I get
error.
CC drivers/media/platform/exynos4-is/fimc-reg.o
In file included from drivers/media/platform/exynos4-is/fimc-reg.c:14:0:
include/linux/regmap.h: In function ‘regmap_write’:
include/linux/regmap.h:525:10: error: ‘EINVAL’ undeclared (first use in this function)
include/linux/regmap.h:525:10: note: each undeclared identifier is reported only once for each function it appears inSigned-off-by: Mateusz Krawczuk
Signed-off-by: Kyungmin Park
Signed-off-by: Mark Brown
Cc: stable@kernel.org
24 Jul, 2013
3 commits
-
Signed-off-by: Philipp Zabel
Signed-off-by: Mark Brown -
This patch makes mask/wake_invert bool and puts all flags into a bitfield
for consistency and to save some space.Signed-off-by: Philipp Zabel
Signed-off-by: Mark Brown -
In case the hardware interrupt mask register does not prevent the chip level
irq from being asserted by the corresponding interrupt status bit, already
set interrupt bits should to be cleared once after masking them during
initialization. Add a flag to let drivers enable this behavior.Signed-off-by: Philipp Zabel
Signed-off-by: Mark Brown
30 Jun, 2013
1 commit
12 Jun, 2013
1 commit
-
It is common to access regmap registers at bit level, using
regmap_update_bits or regmap_read functions, however the end user has to
take care of a mask or shifting. This becomes overhead when such use
cases are high. Having a common function to do this is much convenient
and less error prone.The idea of regmap_field is simple, regmap_field gives a logical
structure to bits of the regmap register, and the driver can use this
logical entity without the knowledge of the bit positions and masks all
over the code. This way code looks much neat and it need not handle the
masks, shifts every time it access the those entities.With this new regmap_field_read/write apis the end user can setup a
regmap field using regmap_field_init and use the return regmap_field to
read write the register field without worrying about the masks or
shifts.Also this apis will be useful for drivers which are based on regmaps,
like some clocks or pinctrls which can work on the regmap_fields
directly without having to worry about bit positions.Signed-off-by: Srinivas Kandagatla
Signed-off-by: Mark Brown
12 May, 2013
2 commits
-
Allow drivers to use an access table as part of their implementation.
Signed-off-by: Mark Brown
-
Allow drivers to discard parts of the register cache, for example if part
of the hardware has been reset.Signed-off-by: Mark Brown
27 Mar, 2013
1 commit
-
Mainly useful internally but exported since this is a public API that's
being checked for.Signed-off-by: Mark Brown
15 Feb, 2013
5 commits
-
Some mmio devices have a dedicated interface clock that needs
to be enabled to access their registers. This patch optionally
enables a clock before accessing registers in the regmap_bus
callbacks.I added (devm_)regmap_init_mmio_clk variants of the init
functions that have an added clk_id string parameter. This
is passed to clk_get to request the clock from the clk
framework.Signed-off-by: Philipp Zabel
Signed-off-by: Mark Brown
29 Jan, 2013
2 commits
-
Some use cases like firmware download can transfer a lot of data in quick
succession. With high speed buses these use cases can benefit from having
multiple transfers scheduled at once since this allows the bus to minimise
the delay between transfers.Support this by adding regmap_raw_write_async(), allowing raw transfers to
be scheduled, and regmap_async_complete() to wait for them to finish.Signed-off-by: Mark Brown
-
This commit adds provision for "no-bus" usage of the regmap API. In
this configuration user can provide API with two callbacks 'reg_read'
and 'reg_write' which are to be called when reads and writes to one of
device's registers is performed. This is useful for devices that
expose registers but whose register access sequence does not fit the 'bus'
abstraction.Signed-off-by: Andrey Smirnov
Signed-off-by: Mark Brown
05 Jan, 2013
1 commit
-
Support devices which have an enable rather than mask register for wake
sources.Signed-off-by: Mark Brown
02 Jan, 2013
1 commit
-
While for I2C and SPI devices the overhead of using rbtree for devices with
only one block of registers is negligible the same isn't always going to
be true for MMIO devices where the I/O costs are very much lower. Cater
for these devices by adding a simple flat array type for them where the
lookups are simple array accesses, taking us right back to the original
ASoC cache implementation.Thanks to Magnus Damm for the discussion which prompted this.
Signed-off-by: Mark Brown
11 Dec, 2012
3 commits
21 Nov, 2012
2 commits
-
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 = W && reg
Signed-off-by: Mark Brown -
…ie/regmap into regmap-table
17 Oct, 2012
1 commit
-
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
15 Oct, 2012
3 commits
-
For more useful diagnostics.
Signed-off-by: Mark Brown
-
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
-
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