1. 17 9月, 2013 1 次提交
  2. 30 8月, 2013 1 次提交
    • A
      regulator: tps65217: Convert to use linear ranges · 6290d606
      Axel Lin 提交于
      Below is the equation in original code:
      
      tps65217_uv1_ranges:
              0  ... 24: uV = vsel * 25000 + 900000;
              25 ... 52: uV = (vsel - 24) * 50000 + 1500000;
                            = (vsel - 25) * 50000 + 1550000;
              53 ... 55: uV = (vsel - 52) * 100000 + 2900000;
                            = (vsel - 53) * 100000 + 3000000;
              56 ... 62: uV = 3300000;
      
      tps65217_uv2_ranges:
              0  ...  8: uV = vsel * 50000 + 1500000;
              9  ... 13: uV = (vsel - 8) * 100000 + 1900000;
                            = (vsel - 9) * 100000 + 2000000;
              14 ... 31: uV = (vsel - 13) * 50000 + 2400000;
                            = (vsel - 14) * 50000 + 2450000;
      
      The voltage tables are composed of linear ranges.
      This patch converts this driver to use multiple linear ranges APIs.
      
      In original code, voltage range for DCDC1 is 900000 ~ 1800000 and voltage range
      for DCDC3 is 900000 ~ 1500000.  This patch separates the range 25~52 in
      tps65217_uv1_ranges table to two linear ranges: 25~30 and 31~52.
      This change makes it possible to reuse the same linear_ranges table for DCDCx.
      Signed-off-by: NAxel Lin <axel.lin@ingics.com>
      Signed-off-by: NMark Brown <broonie@linaro.org>
      6290d606
  3. 12 5月, 2013 1 次提交
  4. 24 1月, 2013 1 次提交
  5. 20 11月, 2012 3 次提交
  6. 22 8月, 2012 2 次提交
    • A
      mfd: Move tps65217 regulator plat data handling to regulator · 1922b0f2
      AnilKumar Ch 提交于
      Regulator platform data handling was mistakenly added to MFD
      driver. So we will see build errors if we compile MFD drivers
      without CONFIG_REGULATOR. This patch moves regulator platform
      data handling from TPS65217 MFD driver to regulator driver.
      
      This makes MFD driver independent of REGULATOR framework so
      build error is fixed if CONFIG_REGULATOR is not set.
      
      drivers/built-in.o: In function `tps65217_probe':
      tps65217.c:(.devinit.text+0x13e37): undefined reference
      to `of_regulator_match'
      
      This patch also fix allocation size of tps65217 platform data.
      Current implementation allocates a struct tps65217_board for each
      regulator specified in the device tree. But the structure itself
      provides array of regulators so one instance of it is sufficient.
      Signed-off-by: NAnilKumar Ch <anilkumar@ti.com>
      1922b0f2
    • A
      mfd: Move tps65217 regulator plat data handling to regulator · 817bb7fb
      AnilKumar Ch 提交于
      Regulator platform data handling was mistakenly added to MFD
      driver. So we will see build errors if we compile MFD drivers
      without CONFIG_REGULATOR. This patch moves regulator platform
      data handling from TPS65217 MFD driver to regulator driver.
      
      This makes MFD driver independent of REGULATOR framework so
      build error is fixed if CONFIG_REGULATOR is not set.
      
      drivers/built-in.o: In function `tps65217_probe':
      tps65217.c:(.devinit.text+0x13e37): undefined reference
      to `of_regulator_match'
      
      This patch also fix allocation size of tps65217 platform data.
      Current implementation allocates a struct tps65217_board for each
      regulator specified in the device tree. But the structure itself
      provides array of regulators so one instance of it is sufficient.
      Signed-off-by: NAnilKumar Ch <anilkumar@ti.com>
      817bb7fb
  7. 13 7月, 2012 1 次提交
  8. 04 7月, 2012 1 次提交
  9. 03 7月, 2012 1 次提交
  10. 02 7月, 2012 1 次提交
  11. 14 6月, 2012 1 次提交
  12. 18 5月, 2012 1 次提交
  13. 09 4月, 2012 1 次提交
    • M
      regulator: core: Use a struct to pass in regulator runtime configuration · c172708d
      Mark Brown 提交于
      Rather than adding new arguments to regulator_register() every time we
      want to add a new bit of dynamic information at runtime change the function
      to take these via a struct. By doing this we avoid needing to do further
      changes like the recent addition of device tree support which required each
      regulator driver to be updated to take an additional parameter.
      
      The regulator_desc which should (mostly) be static data is still passed
      separately as most drivers are able to configure this statically at build
      time.
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      c172708d
  14. 06 4月, 2012 1 次提交
  15. 12 3月, 2012 2 次提交
  16. 20 1月, 2012 2 次提交