Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
1 年多 前同步成功

通知 160
Star 36
Fork 7
cloud-kernel
cloud-kernel
切换分支/标签
  1. 04 4月, 2012 1 次提交
  3. 03 4月, 2012 1 次提交
  5. 01 4月, 2012 1 次提交
  7. 14 3月, 2012 1 次提交
  9. 12 3月, 2012 2 次提交
  11. 07 3月, 2012 1 次提交
  13. 20 1月, 2012 4 次提交
  15. 15 12月, 2011 1 次提交
  17. 23 11月, 2011 1 次提交
  19. 12 10月, 2011 1 次提交
  21. 09 10月, 2011 1 次提交
    • H
      regulator: Add driver for gpio-controlled regulators · 3f0292ae
      由 Heiko Stübner 提交于 
      This patch adds support for regulators that can be controlled via gpios.

Examples for such regulators are the TI-tps65024x voltage regulators
with 4 fixed and 1 runtime-switchable voltage regulators
or the TI-bq240XX charger regulators.

The number of controlling gpios is not limited, the mapping between
voltage/current and target gpio state is done via the states map
and the driver can be used for either voltage or current regulators.

A mapping for a regulator with two GPIOs could look like:

gpios = {
	{ .gpio = GPIO1, .flags = GPIOF_OUT_INIT_HIGH, .label = "gpio name 1" },
	{ .gpio = GPIO2, .flags = GPIOF_OUT_INIT_LOW,  .label = "gpio name 2" },
}

The flags element of the gpios array determines the initial state of
the gpio, set during probe. The initial state of the regulator is also
calculated from these values

states = {
	{ .value = volt_or_cur1, .gpios = (0 << 1) | (0 << 0) },
	{ .value = volt_or_cur2, .gpios = (0 << 1) | (1 << 0) },
	{ .value = volt_or_cur3, .gpios = (1 << 1) | (0 << 0) },
	{ .value = volt_or_cur4, .gpios = (1 << 1) | (1 << 0) },
}

The target-state for the n-th gpio is determined by the n-th bit
in the bitfield of the target-value.
Signed-off-by: NHeiko Stuebner <heiko@sntech.de>
Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      3f0292ae
  23. 01 8月, 2011 2 次提交
  25. 23 7月, 2011 1 次提交
  27. 27 5月, 2011 1 次提交
  29. 25 5月, 2011 1 次提交
  31. 26 3月, 2011 1 次提交
  33. 23 3月, 2011 2 次提交
  35. 12 1月, 2011 4 次提交
  37. 29 10月, 2010 2 次提交
  39. 11 8月, 2010 7 次提交
  41. 08 3月, 2010 2 次提交
  43. 03 3月, 2010 2 次提交
    • M
      regulator: Provide optional dummy regulator for consumers · 34abbd68
      由 Mark Brown 提交于 
      In order to ease transitions with drivers are boards start using regulators
provide an option to cause all regulator_get() calls to succeed, with a
dummy always on regulator being supplied where one has not been configured.
A warning is printed whenever the dummy regulator is used to aid system
development.

This regulator does not implement any regulator operations but will allow
simple consumers which only do enable() and disable() calls to run. It
is kept separate from the fixed voltage regulator to avoid Kconfig
confusion on the part of users when it is extended to allow boards to
explicitly use the dummy regulator to simplify cases where the majority
of supplies are from fixed regulators without software control.

This option is currently only effective for systems which do not specify
full constriants. If required an override could also be provided to allow
these systems to use the dummy regulator, though it is likely that
unconfigured supplies on such systems will lead to error due to
regulators being powered down more aggressively when not in use.
Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: NLiam Girdwood <lrg@slimlogic.co.uk>
      34abbd68
    • M
      regulator: Add WM8994 regulator support · 69dc16c3
      由 Mark Brown 提交于 
      The WM8994 contains two LDOs with mixed hardware/software control to
minimise the number of external supplies required while delivering
optimal voltages to minimise power consumption.
Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: NLiam Girdwood <lrg@slimlogic.co.uk>
      69dc16c3