Skip to content

L
linux
An error occurred fetching the project authors.
Switch branch/tag
  1. 20 Jul, 2012 1 commit
  3. 11 Jul, 2012 1 commit
  5. 25 Jun, 2012 1 commit
  7. 20 Jun, 2012 1 commit
  9. 19 Jun, 2012 1 commit
  11. 03 Jun, 2012 1 commit
  13. 19 May, 2012 1 commit
  15. 04 Apr, 2012 2 commits
  17. 01 Apr, 2012 1 commit
  19. 14 Mar, 2012 1 commit
  21. 11 Mar, 2012 1 commit
  23. 07 Mar, 2012 1 commit
  25. 03 Mar, 2012 1 commit
  27. 20 Jan, 2012 4 commits
  29. 14 Dec, 2011 1 commit
  31. 23 Nov, 2011 1 commit
    • Rajendra Nayak's avatar
      regulator: helper routine to extract regulator_init_data · 8f446e6f
      Rajendra Nayak authored 
      The helper routine is meant to be used by the regulator drivers
to extract the regulator_init_data structure from the data
that is passed from device tree.
'consumer_supplies' which is part of regulator_init_data is not extracted
as the regulator consumer mappings are passed through DT differently,
implemented in subsequent patches.
Similarly the regulator<-->parent/supply mapping is handled in
subsequent patches.

Also add documentation for regulator bindings to be used to pass
regulator_init_data struct information from device tree.

Some of the regulator properties which are linux and board specific,
are left out since its not clear if they can
be in someway embedded into the kernel or passed in from DT.
They will be revisited later.
Signed-off-by: default avatarRajendra Nayak <rnayak@ti.com>
Signed-off-by: default avatarMark Brown <broonie@opensource.wolfsonmicro.com>
      8f446e6f
  33. 09 Oct, 2011 1 commit
    • Heiko Stübner's avatar
      regulator: Add driver for gpio-controlled regulators · 3f0292ae
      Heiko Stübner authored 
      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: default avatarHeiko Stuebner <heiko@sntech.de>
Signed-off-by: default avatarMark Brown <broonie@opensource.wolfsonmicro.com>
      3f0292ae
  35. 31 Jul, 2011 2 commits
  37. 27 May, 2011 1 commit
  39. 24 May, 2011 1 commit
  41. 23 Mar, 2011 2 commits
  43. 12 Jan, 2011 3 commits
  45. 28 Oct, 2010 3 commits
  47. 11 Aug, 2010 5 commits
  49. 07 Mar, 2010 1 commit
  51. 03 Mar, 2010 1 commit
    • Mark Brown's avatar
      regulator: Provide optional dummy regulator for consumers · 34abbd68
      Mark Brown authored 
      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: default avatarMark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: default avatarLiam Girdwood <lrg@slimlogic.co.uk>
      34abbd68
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7