Linux kernel documentation tree maintained by Jonathan Corbet http://mirrors.hust.edu.cn/git/lwn.git/atom?h=v3.17-rc5 2014-08-31T12:23:45+00:00 2014-08-31T12:23:45+00:00 Mark Brown broonie@kernel.org 2014-08-31T12:23:45+00:00 urn:sha1:d3b05339873d42a1820d9215ce3885b61d9a95a1 2014-08-31T12:22:37+00:00 Mark Brown broonie@linaro.org 2014-08-27T12:09:12+00:00 urn:sha1:5c1ebe7f73f9166893c3459915db8a09d6d1d715 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> Cc: stable@vger.kernel.org 2014-08-26T17:34:26+00:00 Mark Brown broonie@linaro.org 2014-08-26T11:12:17+00:00 urn:sha1:5844a8b9d98ec11ce1d77610daacf3f0a0e14715 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> Cc: stable@vger.kernel.org 2014-08-26T08:11:56+00:00 Lars-Peter Clausen lars@metafoo.de 2014-08-24T13:32:27+00:00 urn:sha1:5e0cbe78762b5f02986bf9e59a188dad2f6e0be1 Commit 6cfec04bcc05 ("regmap: Separate regmap dev initialization") moved the regmap debugfs initialization after regcache initialization. This means that the regmap debugfs directory is not created yet when the cache initialization runs and so any debugfs files registered by the regcache are created in the debugfs root directory rather than the debugfs directory of the regmap instance. Fix this by adding a separate callback for the regcache debugfs initialization which will be called after the parent debugfs entry has been created. Fixes: 6cfec04bcc05 (regmap: Separate regmap dev initialization) Signed-off-by: Lars-Peter Clausen <lars@metafoo.de> Signed-off-by: Mark Brown <broonie@linaro.org> Cc: stable@vger.kernel.org 2014-07-25T17:30:31+00:00 Mark Brown broonie@linaro.org 2014-07-25T17:30:31+00:00 urn:sha1:fa2fbe4a981a70866d20cee62af0d89eb6b6027e Signed-off-by: Mark Brown <broonie@linaro.org> 2014-07-25T17:29:28+00:00 Tuomas Tynkkynen ttynkkynen@nvidia.com 2014-07-21T15:38:47+00:00 urn:sha1:8d7d3972a9ae962bbf8ce49c83f4a40082708f69 Add a new function regmap_get_device to obtain the underlying struct device from a regmap. Signed-off-by: Tuomas Tynkkynen <ttynkkynen@nvidia.com> Signed-off-by: Mark Brown <broonie@linaro.org> 2014-06-02T16:07:42+00:00 Mark Brown broonie@linaro.org 2014-06-02T16:07:42+00:00 urn:sha1:ef98ae45e6b3ea17d3ed27cec9afdd7e46f916ae 2014-06-02T16:07:39+00:00 Mark Brown broonie@linaro.org 2014-06-02T16:07:39+00:00 urn:sha1:522168d178208ff821b9bc37ffcd2442b80f6e6d 2014-05-26T15:56:02+00:00 Philipp Zabel p.zabel@pengutronix.de 2014-05-16T14:25:34+00:00 urn:sha1:2e804b7c72d4efd2318428a2c1e40fd0e173c487 Commit 932580409a9dacbf42215fa737bf06ae2c0aa624 "regmap: mmio: Add support for 1/2/8 bytes wide register address." broke regmap_mmio_write for uneven counts, for example 32-bit register addresses with no padding and 8-byte values (count = 5). Fix this by allowing all counts large enough to include some value. This check was BUG_ON(count < 4) before the last change. Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de> Signed-off-by: Mark Brown <broonie@linaro.org> 2014-05-26T15:37:04+00:00 Xiubo Li Li.Xiubo@freescale.com 2014-05-19T07:13:45+00:00 urn:sha1:e12892070184ee782c207f09722a93d0236be955 Since we cannot make sure the 'chip->num_regs' will always be none zero from the users, and then if 'chip->num_regs' equals to zero by mistake or other reasons, the kzalloc() will return ZERO_SIZE_PTR, which equals to ((void *)16). So this patch fix this with just checking the 'chip->num_regs' before calling kzalloc(). This also sorts the header files in alphabetical order at the same time. Signed-off-by: Xiubo Li <Li.Xiubo@freescale.com> Signed-off-by: Mark Brown <broonie@linaro.org>