linux-toradex.git/drivers/base/regmap, branch v3.14.20 Linux kernel for Apalis and Colibri modules regmap: Don't attempt block writes when syncing cache on single_rw devices 2014-10-05T21:52:17+00:00 Mark Brown broonie@linaro.org 2014-08-27T12:09:12+00:00 79c770cb58596b91c2e07a39090401fcc580cc14 commit 5c1ebe7f73f9166893c3459915db8a09d6d1d715 upstream. If the device can't support block writes then don't attempt to use raw syncing which will automatically generate block writes for adjacent registers, use the existing _single() block syncing implementation. Reported-by: Jarkko Nikula <jarkko.nikula@linux.intel.com> Tested-by: Jarkko Nikula <jarkko.nikula@linux.intel.com> Signed-off-by: Mark Brown <broonie@linaro.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 
commit 5c1ebe7f73f9166893c3459915db8a09d6d1d715 upstream.

If the device can't support block writes then don't attempt to use raw
syncing which will automatically generate block writes for adjacent
registers, use the existing _single() block syncing implementation.

Reported-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Tested-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Signed-off-by: Mark Brown <broonie@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
regmap: Fix handling of volatile registers for format_write() chips 2014-10-05T21:52:17+00:00 Mark Brown broonie@linaro.org 2014-08-26T11:12:17+00:00 83c40254d2ab977aa87c3e424c8b82ceb422d8be commit 5844a8b9d98ec11ce1d77610daacf3f0a0e14715 upstream. A previous over-zealous factorisation of code means that we only treat registers as volatile if they are readable. For most devices this is fine since normally most registers can be read and volatility implies readability but for format_write() devices where there is no readback from the hardware and we use volatility to mean simply uncacheability this means that we end up treating all registers as cacheble. A bigger refactoring of the code to clarify this is in order but as a fix make a minimal change and only check readability when checking volatility if there is no format_write() operation defined for the device. Signed-off-by: Mark Brown <broonie@linaro.org> Tested-by: Lars-Peter Clausen <lars@metafoo.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 
commit 5844a8b9d98ec11ce1d77610daacf3f0a0e14715 upstream.

A previous over-zealous factorisation of code means that we only treat
registers as volatile if they are readable. For most devices this is fine
since normally most registers can be read and volatility implies
readability but for format_write() devices where there is no readback from
the hardware and we use volatility to mean simply uncacheability this means
that we end up treating all registers as cacheble.

A bigger refactoring of the code to clarify this is in order but as a fix
make a minimal change and only check readability when checking volatility
if there is no format_write() operation defined for the device.

Signed-off-by: Mark Brown <broonie@linaro.org>
Tested-by: Lars-Peter Clausen <lars@metafoo.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Merge remote-tracking branch 'regmap/topic/ack' into regmap-next 2014-01-09T14:34:13+00:00 Mark Brown broonie@linaro.org 2014-01-09T14:34:13+00:00 86776fc174973e556be7d668763f509a81124f8b 






regmap: Allow regmap_bulk_write() to work for "no-bus" regmaps
2013-12-30T12:39:20+00:00

Stephen Boyd
sboyd@codeaurora.org

2013-12-26T21:52:04+00:00

f4298360a5c21409e04cd2b0e220c8f8521fd14c

regmap_bulk_write() should decay to performing individual writes
if we're using a "no-bus" regmap. Unfortunately, it returns an
error because there is no map->bus pointer. Fix it.

Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
Signed-off-by: Mark Brown <broonie@linaro.org>





regmap_bulk_write() should decay to performing individual writes
if we're using a "no-bus" regmap. Unfortunately, it returns an
error because there is no map->bus pointer. Fix it.

Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
Signed-off-by: Mark Brown <broonie@linaro.org>







Merge tag 'v3.13-rc4' into regmap-core
2013-12-30T12:38:53+00:00

Mark Brown
broonie@linaro.org

2013-12-30T12:38:53+00:00

34f653345018c42cedea89b7f6a4aba3783ebd7b

Needed as a subsequent patch is built on some of the fixes.

Linux 3.13-rc4





Needed as a subsequent patch is built on some of the fixes.

Linux 3.13-rc4







regmap: Allow regmap_bulk_read() to work for "no-bus" regmaps
2013-12-16T20:54:35+00:00

Stephen Boyd
sboyd@codeaurora.org

2013-12-13T17:14:07+00:00

3b58ee13da7510115b66f71c67c9e87b47e9c4aa

regmap_bulk_read() should decay to performing individual reads if
we're using a "no-bus" regmap. Unfortunately, it returns an
error because there is no map->bus pointer. Fix it.

Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
Signed-off-by: Mark Brown <broonie@linaro.org>





regmap_bulk_read() should decay to performing individual reads if
we're using a "no-bus" regmap. Unfortunately, it returns an
error because there is no map->bus pointer. Fix it.

Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
Signed-off-by: Mark Brown <broonie@linaro.org>







regmap: irq: Allow using zero value for ack_base
2013-12-16T20:50:13+00:00

Alexander Shiyan
shc_work@mail.ru

2013-12-15T09:36:51+00:00

d3233433356aa1965b60b08ee61465b20e50474b

In some cases, clear interrupt register may be at address 0.
This patch allows to use such configurations by adding additional
configuration bit to indicate this.

[With doc fix from Levente Kurusa <levex@linux.com> -- broonie]

Signed-off-by: Alexander Shiyan <shc_work@mail.ru>
Signed-off-by: Mark Brown <broonie@linaro.org>





In some cases, clear interrupt register may be at address 0.
This patch allows to use such configurations by adding additional
configuration bit to indicate this.

[With doc fix from Levente Kurusa <levex@linux.com> -- broonie]

Signed-off-by: Alexander Shiyan <shc_work@mail.ru>
Signed-off-by: Mark Brown <broonie@linaro.org>







Merge remote-tracking branches 'regmap/fix/doc' and 'regmap/fix/mmio' into regmap-linus
2013-11-26T13:16:56+00:00

Mark Brown
broonie@linaro.org

2013-11-26T13:16:56+00:00

652787ab1aca35e5e85e644757f7ea2cc00681d1












regmap: use IS_ERR() to check clk_get() results
2013-11-26T13:16:31+00:00

Stephen Warren
swarren@nvidia.com

2013-11-25T22:12:47+00:00

6b8e090ecc3dc977fe2eabf6e50bb3870de9ebac

clk_get() returns an error pointer, or a valid token to pass back to the
clock API. Hence, the result must be checked with IS_ERR(), not by
comparison against NULL.

Signed-off-by: Stephen Warren <swarren@nvidia.com>
Signed-off-by: Mark Brown <broonie@linaro.org>





clk_get() returns an error pointer, or a valid token to pass back to the
clock API. Hence, the result must be checked with IS_ERR(), not by
comparison against NULL.

Signed-off-by: Stephen Warren <swarren@nvidia.com>
Signed-off-by: Mark Brown <broonie@linaro.org>







regmap: Fix 'ret' would return an uninitialized value
2013-11-24T13:59:14+00:00

Cai Zhiyong
caizhiyong@huawei.com

2013-11-18T12:21:49+00:00

bd60e381fab88979c3312265d18bb635c314d242

This patch give a warning when calling regmap_register_patch with
parameter num_regs <= 0.

When the num_regs parameter is zero and krealloc doesn't fail,
then the code would return an uninitialized value. However,
calling this function with num_regs == 0, would be a waste as it
essentially does nothing.

Signed-off-by: Cai Zhiyong <caizhiyong@huawei.com>
Reviewed-by: Geyslan G. Bem <geyslan@gmail.com>
Signed-off-by: Mark Brown <broonie@linaro.org>





This patch give a warning when calling regmap_register_patch with
parameter num_regs <= 0.

When the num_regs parameter is zero and krealloc doesn't fail,
then the code would return an uninitialized value. However,
calling this function with num_regs == 0, would be a waste as it
essentially does nothing.

Signed-off-by: Cai Zhiyong <caizhiyong@huawei.com>
Reviewed-by: Geyslan G. Bem <geyslan@gmail.com>
Signed-off-by: Mark Brown <broonie@linaro.org>