1. 19 4月, 2014 1 次提交
  2. 15 4月, 2014 2 次提交
  3. 19 9月, 2013 1 次提交
  4. 15 7月, 2013 1 次提交
  5. 20 6月, 2013 1 次提交
  6. 30 1月, 2013 1 次提交
    • S
      regulator: clear state each invocation of of_regulator_match · a2f95c36
      Stephen Warren 提交于
      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: NStephen Warren <swarren@nvidia.com>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      Cc: stable@vger.kernel.org
      a2f95c36
  7. 25 9月, 2012 1 次提交
    • S
      regulator: deprecate regulator-compatible DT property · 13511def
      Stephen Warren 提交于
      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: NStephen Warren <swarren@nvidia.com>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      13511def
  8. 04 7月, 2012 1 次提交
  9. 18 6月, 2012 2 次提交
  10. 04 5月, 2012 1 次提交
  11. 26 1月, 2012 1 次提交
  12. 06 12月, 2011 2 次提交
  13. 27 11月, 2011 1 次提交
  14. 24 11月, 2011 1 次提交
    • R
      regulator: helper routine to extract regulator_init_data · 8f446e6f
      Rajendra Nayak 提交于
      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: NRajendra Nayak <rnayak@ti.com>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      8f446e6f