Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 05 12月, 2016 1 次提交
  3. 05 11月, 2016 1 次提交
  5. 17 9月, 2016 1 次提交
    • M
      regulator: core: Add set_voltage_time op · 73e705bf
      由 Matthias Kaehlcke 提交于 
      The new op is analogous to set_voltage_time_sel. It can be used by
regulators which don't have a table of discrete voltages. The function
returns the time for the regulator output voltage to stabilize after
being set to a new value, in microseconds. If the op is not set a
default implementation is used to calculate the delay.

This change also removes the ramp_delay calculation in the PWM
regulator, since the driver now uses the core code for the calculation
of the delay.
Signed-off-by: NMatthias Kaehlcke <mka@chromium.org>
Signed-off-by: NMark Brown <broonie@kernel.org>
      73e705bf
  7. 17 8月, 2016 1 次提交
  9. 18 7月, 2016 1 次提交
  11. 30 6月, 2016 1 次提交
  13. 09 6月, 2016 1 次提交
    • M
      regulator: Remove regulator_can_change_voltage() · fc1e1c4a
      由 Mark Brown 提交于 
      There is little obvious use case for a regualtor driver to know if it is
possible to vary voltages at all by itself.  If a consumer needs to
limit what voltages it tries to set based on the system configuration
then it will need to enumerate the possible voltages, and without that
even if it is possible to change voltages that doesn't mean that
constraints or other consumers will allow whatever change the driver is
trying to do at a given time.  It doesn't even indicate if _set_voltage()
calls will work as noop _set_voltage() calls return success.

There were no users of this API that weren't abusing it and now they're
all gone so remove the API.
Signed-off-by: NMark Brown <broonie@kernel.org>
      fc1e1c4a
  15. 18 5月, 2016 1 次提交
    • M
      regulator: Silence build warnings from regulator_can_change_voltage() · ec4c4366
      由 Mark Brown 提交于 
      Cut down on noise for mainstream users of the API and people doing build
testing by dropping the deprecated flag from regulator_can_change_voltage()
as it triggers even on the EXPORT_SYMBOL_GPL() which affects all builds
rather than just the remaining drivers with calls to it (for which fixes
are currently pending).

The function remains deprecated and is expected to be removed entirely
in v4.8.
Signed-off-by: NMark Brown <broonie@kernel.org>
      ec4c4366
  17. 21 4月, 2016 1 次提交
  19. 14 4月, 2016 1 次提交
    • L
      regulator: max8973: add support for junction thermal warning · d2d5437b
      由 Laxman Dewangan 提交于 
      The driver MAX8973 supports the driver for Maxim PMIC MAX77621.
MAX77621 supports the junction temp warning at 120 degC and
140 degC which is configurable. It generates alert signal when
junction temperature crosses these threshold.

MAX77621 does not support the continuous temp monitoring of
junction temperature. It just report whether junction temperature
crossed the threshold or not.

Add support to
- Configure junction temp warning threshold via DT property
to generate alert when it crosses the threshold.
- Add support to interrupt the host from this device when alert
occurred.
- read the junction temp via thermal framework.
Signed-off-by: NLaxman Dewangan <ldewangan@nvidia.com>
Signed-off-by: NMark Brown <broonie@kernel.org>
      d2d5437b
  21. 31 3月, 2016 1 次提交
    • M
      regulator: Deprecate regulator_can_change_voltage() · 6a0028b3
      由 Mark Brown 提交于 
      All current users of regulator_can_change_voltage() are abusing it,
using it to wrap a call to regulator_set_voltage() on probe without any
alternative handling for fixed voltages.  Drivers should only be using
regulator_set_voltage() if they need to vary voltages at runtime, fixed
voltages should normally be set via machine constraints, and calling
regulator_set_voltage() on a regulator which can't be varied will
succeed if the current voltage is within the range requested so users
shouldn't worry if they have permission to vary normally.

Deprecate the API to try to stop any new users appearing while we fix
the current callers.
Signed-off-by: NMark Brown <broonie@kernel.org>
      6a0028b3
  23. 29 3月, 2016 1 次提交
  25. 23 3月, 2016 2 次提交
  27. 02 3月, 2016 2 次提交
  29. 29 2月, 2016 1 次提交
  31. 06 2月, 2016 1 次提交
  33. 25 11月, 2015 1 次提交
  35. 18 11月, 2015 1 次提交
  37. 17 10月, 2015 1 次提交
  39. 18 8月, 2015 1 次提交
    • V
      regulator: core: Define regulator_set_voltage_triplet() · 30f93ca8
      由 Viresh Kumar 提交于 
      Voltage tolerance isn't necessarily same on both sides of the target
voltage and regulator_set_voltage_tol() wouldn't be suitable in such
cases.

Add another routine regulator_set_voltage_triplet(), which accepts
target, min and max voltages as arguments.

This first tries to set the voltage between the target voltage and the
upper limit, then fall back on the full range. The idea behind this is
to set regulator's voltage as close to the target voltage, as possible.

Based on regulator_set_voltage_tol().
Signed-off-by: NViresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: NMark Brown <broonie@kernel.org>
      30f93ca8
  41. 25 7月, 2015 1 次提交
  43. 24 7月, 2015 1 次提交
  45. 14 7月, 2015 1 次提交
  47. 11 7月, 2015 1 次提交
    • S
      regulator: Add missing dummy definition for regulator_list_voltage · 5127e31a
      由 Suzuki K. Poulose 提交于 
      Fixes a build break when CONFIG_REGULATOR is not selected.

e.g, on linux-next - 07102015:

drivers/clk/tegra/clk-dfll.c: In function ‘find_lut_index_for_rate’:
drivers/clk/tegra/clk-dfll.c:691:3: error: implicit declaration of function ‘regulator_list_voltage’ [-Werror=implicit-function-declaration]
    if (regulator_list_voltage(td->vdd_reg, td->i2c_lut[i]) == uv)
    ^
   CC      drivers/clocksource/mmio.o
   CC      fs/proc/softirqs.o
cc1: some warnings being treated as errors
make[3]: *** [drivers/clk/tegra/clk-dfll.o] Error 1
make[2]: *** [drivers/clk/tegra] Error 2
make[1]: *** [drivers/clk] Error 2
make[1]: *** Waiting for unfinished jobs....

This should be pushed to 4.2 as we have the issue in 4.2-rc1, just that
nobody uses it without the REGULATOR(yet).
Signed-off-by: NSuzuki K. Poulose <suzuki.poulose@arm.com>
Signed-off-by: NMark Brown <broonie@kernel.org>
      5127e31a
  49. 15 6月, 2015 1 次提交
  51. 12 6月, 2015 4 次提交
  53. 22 5月, 2015 1 次提交
  55. 02 4月, 2015 1 次提交
  57. 18 3月, 2015 1 次提交
  59. 10 3月, 2015 2 次提交
  61. 07 3月, 2015 1 次提交
  63. 06 3月, 2015 1 次提交
  65. 24 2月, 2015 1 次提交
  67. 23 2月, 2015 1 次提交