1. 16 7月, 2012 1 次提交
    • A
      regulator: s5m8767: Properly handle gpio_request failure · 5febb3c9
      Axel Lin 提交于
      Convert to devm_gpio_request to save a few error handling code.
      
      This patch properly handle the gpio_request failure, we should return error
      when gpio_request fails rather than just show warning.
      
      I think one of the reason we got -EBUSY is because current code does not free
      gpios in s5m8767_pmic_remove(). So it got -EBUSY when reload the module.
      
      Yest another reason is in current code if gpio_request() returns error,
      the rest of the code still calls gpio_direction_output to config buck_gpios
      and buck_ds gpios. This looks wrong to me.
      Signed-off-by: NAxel Lin <axel.lin@gmail.com>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      5febb3c9
  2. 26 6月, 2012 1 次提交
    • A
      regulator: s5m8767: Convert to regulator_list_voltage_linear · e2eb169b
      Axel Lin 提交于
      In current code, .list_voltage and .set_voltage_sel callbacks for BUCK7 and
      BUCK8 return -EINVAL.
      
      This patch adds s5m8767_buck78_ops for BUCK7 and BUCK8 which does not set
      .list_voltage, .get_voltage_sel and .set_voltage_sel. ( This has the same
      effect of returning -EINVAL in the callbacks)
      
      Then for all the users of s5m8767_list_voltage, we don't need to worry about
      the case reg_voltage_map[reg_id] is NULL.
      So we can convert s5m8767_list_voltage to regulator_list_voltage_linear.
      Signed-off-by: NAxel Lin <axel.lin@gmail.com>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      e2eb169b
  3. 25 6月, 2012 1 次提交
  4. 19 6月, 2012 1 次提交
    • S
      regulator: s5m8767a: Support AP watchdog reset operation · c848bc85
      Sangbeom Kim 提交于
      The S5M8767A can't know status of ap reset.
      So, After AP watchdog reset, AP can't boot normally.
      
      Problem can be happened like below condition.
      - AP Bootable lowest voltage(vdd_arm): 0.9v
      - AP DVFS voltage table: 0.8v, 0.9v, 1.0v
      - During AP works on lowest voltage(0.8V), watchdog reset is asserted
      - AP can't boot, because vdd arm is still 0.8v
      
      Solution
      - Basic concept:
        After ap watchdog reset, GPIO configuration is changed by default value
      - S5M8767A has function of voltage control with gpio (8 levels with 3 gpios)
      - Set bootable voltage on level 0 -> can work with default gpio configuration
      - In the probing, Change voltage control level from level 0 to level 1
      - Execute normal dvfs operation on level 1
      - After watchdog reset, ap gpio is set by default value
      - PMIC operation mode is changed by ap reset (level1 -> level0)
      - Regardless of previous vdd_arm voltage, AP always can be booted.
      Signed-off-by: NSangbeom Kim <sbkim73@samsung.com>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      c848bc85
  5. 18 6月, 2012 1 次提交
  6. 14 6月, 2012 1 次提交
  7. 13 6月, 2012 1 次提交
  8. 12 5月, 2012 1 次提交
  9. 23 4月, 2012 2 次提交
  10. 10 4月, 2012 3 次提交
  11. 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
  12. 01 4月, 2012 1 次提交
  13. 31 3月, 2012 1 次提交
  14. 14 3月, 2012 2 次提交
  15. 12 3月, 2012 5 次提交
  16. 02 2月, 2012 1 次提交
  17. 20 1月, 2012 4 次提交