Linux Kernel https://git.stealer.net/cgit.cgi/user/sven/linux.git/atom?h=v4.1.18 2015-02-04T11:22:21Z 2015-02-04T11:22:21Z Krzysztof Kozlowski k.kozlowski@samsung.com 2015-02-04T10:45:28Z urn:sha1:509102760da3a21831e763560ba4715760e3fbda Add missing stubs for regulator_suspend_prepare() and regulator_suspend_finish() to fix exynos_defconfig build without REGULATOR: arch/arm/mach-exynos/built-in.o: In function `exynos_suspend_finish': arch/arm/mach-exynos/suspend.c:537: undefined reference to `regulator_suspend_finish' arch/arm/mach-exynos/built-in.o: In function `exynos_suspend_prepare': arch/arm/mach-exynos/suspend.c:520: undefined reference to `regulator_suspend_prepare' make: *** [vmlinux] Error 1 Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com> Reported-by: Joerg Roedel <joro@8bytes.org> Reported-by: Marek Szyprowski <m.szyprowski@samsung.com> Signed-off-by: Mark Brown <broonie@kernel.org> 2014-08-28T08:59:42Z Randy Dunlap rdunlap@infradead.org 2014-08-27T21:31:24Z urn:sha1:a8dbfeedfe47a19a4712749eb2444b1d7ea1150e Fix kernel-doc warnings in regulator header files: Warning(..//include/linux/regulator/machine.h:140): No description found for parameter 'ramp_disable' Warning(..//include/linux/regulator/driver.h:279): No description found for parameter 'linear_ranges' Warning(..//include/linux/regulator/driver.h:279): No description found for parameter 'n_linear_ranges' Signed-off-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Mark Brown <broonie@linaro.org> 2013-10-24T10:11:39Z Mark Brown broonie@linaro.org 2013-10-24T10:11:39Z urn:sha1:aef393da7501693a1b91a1cfed1a9ea408ceabe6 2013-09-18T16:13:02Z Laxman Dewangan ldewangan@nvidia.com 2013-09-18T12:48:02Z urn:sha1:00c877c69ba315d6c565a4df51c71b11e82cdeb8 The turn-on time of the regulator depends on the regulator device's electrical characteristics. Sometimes regulator turn-on time also depends on the capacitive load on the given platform and it can be more than the datasheet value. The driver provides the enable-time as per datasheet. Add support for configure the enable ramp time through regulator constraints so that regulator core can take this value for enable time for that regulator. Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com> Acked-by: Stephen Warren <swarren@nvidia.com> Signed-off-by: Mark Brown <broonie@linaro.org> 2013-09-16T23:30:25Z Mark Brown broonie@linaro.org 2013-09-13T18:51:47Z urn:sha1:4f0ac6dabf867095b31f851ba0d0ceaca2f87e2e No boards have used this functionality and the new default of providing dummy regulators by default provides a better solution to the problem it was trying to solve. Signed-off-by: Mark Brown <broonie@linaro.org> 2013-07-15T10:27:48Z Yadwinder Singh Brar yadi.brar@samsung.com 2013-06-29T12:51:15Z urn:sha1:1653ccf4c52df6a4abe8ec2f33f2cb2896d129ea Some hardwares support disabling ramp delay, so adding ramp_disable flag to constraints. It will be used to figure out whether ramp_delay in constraints is explicitly set to zero or its unintialized (zero by default). And we don't need to call set_voltage_time_sel() for regulators for whom ramp delay is disabled in constraints. Signed-off-by: Yadwinder Singh Brar <yadi.brar@samsung.com> Signed-off-by: Mark Brown <broonie@linaro.org> 2012-09-10T03:25:10Z Mark Brown broonie@opensource.wolfsonmicro.com 2012-08-31T17:36:37Z urn:sha1:f59c8f9fe689790248ae7aa7426579982050638c Many regulators support a bypass mode where they simply switch their input supply to the output. This is mainly used in low power retention states where power consumption is extremely low so higher voltage or less clean supplies can be used. Support this by providing ops for the drivers and a consumer API which allows the device to be put into bypass mode if all consumers enable it and the machine enables permission for this. This is not supported as a mode since the existing modes are rarely used due to fuzzy definition and mostly redundant with modern hardware which is able to respond promptly to load changes. Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com> Reviewed-by: Graeme Gregory <gg@slimlogic.co.uk> 2012-06-18T09:56:58Z Axel Lin axel.lin@gmail.com 2012-06-18T06:03:16Z urn:sha1:ea38d13fd1666bc030cb1c0feec5b0da2f89f9b2 This change makes it possible to set ramp_delay with 0.xxx mV/uS without truncation issue. Signed-off-by: Axel Lin <axel.lin@gmail.com> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com> 2012-06-17T20:08:52Z Yadwinder Singh Brar yadi.brar01@gmail.com 2012-06-11T12:11:08Z urn:sha1:6f0b2c696ca340cc2da381fe693fda3f8fdb2149 For some hardwares ramp_delay for BUCKs is a configurable parameter which can be configured through DT or board file.This patch adds ramp_delay to regulator constraints and allow user to configure it for regulators which supports this feature, through DT or board file. It will provide two ways of setting the ramp_delay for a regulator: First, by setting it as constraints in board file(for configurable regulators) and set_machine_constraints() will take care of setting it on hardware by calling(the provided) .set_ramp_delay() operation(callback). Second, by setting it as data in regulator_desc(as fixed/default ramp_delay rate) for a regulator in driver. regulator_set_voltage_time_sel() will give preference to constraints->ramp_delay while reading ramp_delay rate for regulator. Similarly users should also take care accordingly while refering ramp_delay rate(in case of implementing their private .set_voltage_time_sel() callbacks for different regulators). [Rewrote subject for 80 columns -- broonie] Signed-off-by: Yadwinder Singh Brar <yadi.brar@samsung.com> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com> 2012-03-29T11:09:45Z Axel Lin axel.lin@gmail.com 2012-03-29T04:21:17Z urn:sha1:15c08f664d8ca4f4d0e202cbd4034422a706ef80 Signed-off-by: Axel Lin <axel.lin@gmail.com> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>