Skip to content

L
linux
An error occurred fetching the project authors.
Switch branch/tag
  1. 22 Jun, 2016 1 commit
  3. 30 Mar, 2016 1 commit
  5. 27 Mar, 2016 1 commit
  7. 22 Mar, 2016 1 commit
  9. 12 Mar, 2016 1 commit
  11. 02 Mar, 2016 1 commit
  13. 17 Sep, 2015 1 commit
  15. 24 Jul, 2015 1 commit
  17. 12 Jun, 2015 4 commits
  19. 13 May, 2015 1 commit
  21. 27 Apr, 2015 1 commit
  23. 08 Jan, 2015 1 commit
  25. 26 Nov, 2014 3 commits
  27. 03 Nov, 2014 1 commit
  29. 31 Oct, 2014 1 commit
  31. 29 Oct, 2014 1 commit
  33. 22 Oct, 2014 1 commit
  35. 20 Oct, 2014 1 commit
  37. 10 Sep, 2014 1 commit
    • Mark Brown's avatar
      regulator: of: Provide simplified DT parsing method · a0c7b164
      Mark Brown authored 
      Currently regulator drivers which support DT all repeat very similar code
to supply a list of known regulator identifiers to be matched with DT,
convert that to platform data which is then matched up with the regulators
as they are registered. This is both fiddly to get right and for devices
which can use the standard helpers to provide their operations is the main
source of code in the driver.

Since this code is essentially identical for most drivers we can factor it
out into the core, moving the identifiers in the match table into the
regulator descriptors and also allowing drivers to pass in the name of the
subnode to search. When a driver provides an of_match string for the
regulator the core will attempt to use that to obtain init_data, allowing
the driver to remove all explicit code for DT parsing and simply provide
data instead.

The current code leaks the phandles for the child nodes, this will be
addressed incrementally and makes no practical difference for FDT anyway
as the DT data structures are never freed.
Signed-off-by: default avatarMark Brown <broonie@linaro.org>
      a0c7b164
  39. 01 Jun, 2014 1 commit
  41. 18 Apr, 2014 1 commit
  43. 14 Apr, 2014 2 commits
  45. 18 Sep, 2013 1 commit
  47. 15 Jul, 2013 1 commit
  49. 20 Jun, 2013 1 commit
  51. 30 Jan, 2013 1 commit
    • Stephen Warren's avatar
      regulator: clear state each invocation of of_regulator_match · a2f95c36
      Stephen Warren authored 
      of_regulator_match() saves some dynamcially allocated state into the
match table that's passed to it. By implementation and not contract, for
each match table entry, if non-NULL state is already present,
of_regulator_match() will not overwrite it. of_regulator_match() is
typically called each time a regulator is probe()d. This means it is
called with the same match table over and over again if a regulator
triggers deferred probe. This results in stale, kfree()d data being left
in the match table from probe to probe, which causes a variety of crashes
or use of invalid data.

Explicitly free all output state from of_regulator_match() before
generating new results in order to avoid this.
Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
Signed-off-by: default avatarMark Brown <broonie@opensource.wolfsonmicro.com>
Cc: stable@vger.kernel.org
      a2f95c36
  53. 25 Sep, 2012 1 commit
    • Stephen Warren's avatar
      regulator: deprecate regulator-compatible DT property · 13511def
      Stephen Warren authored 
      When the bindings for the TPS6586x regulator were being proposed, I
asserted that DT node naming rules for bus child nodes should also be
applied to nodes inside the TPS6586x regulator node itself. In other
words, that each node providing regulator init data should be named
after the type of object it represented ("regulator") and hence that
some other property was required to indicate which regulator the node
described ("regulator-compatible"). In turn this led to multiple nodes
having the same name, thus requiring node names to use a unit address
to make them unique, thus requiring reg properties within the nodes and

However, subsequent discussion indicates that the rules I was asserting
only applies to standardized bus nodes, and within a device's own node,
the binding can basically do anything sane that it wants.

Hence, this change deprecates the register-compatible property, and
instead uses node names to replace this functionality. This greatly
simplifies the device tree content, making them smaller and more legible.

The code is changed such that old device trees continue to work.
Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
Signed-off-by: default avatarMark Brown <broonie@opensource.wolfsonmicro.com>
      13511def
  55. 03 Jul, 2012 1 commit
  57. 18 Jun, 2012 1 commit
  59. 17 Jun, 2012 1 commit
    • Yadwinder Singh Brar's avatar
      regulator: Add ramp_delay configuration to constraints · 6f0b2c69
      Yadwinder Singh Brar authored 
      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: default avatarYadwinder Singh Brar <yadi.brar@samsung.com>
Signed-off-by: default avatarMark Brown <broonie@opensource.wolfsonmicro.com>
      6f0b2c69
  61. 04 May, 2012 1 commit
  63. 26 Jan, 2012 1 commit
  65. 05 Dec, 2011 2 commits
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7