1. 13 12月, 2013 1 次提交
  2. 24 10月, 2013 2 次提交
  3. 17 9月, 2013 1 次提交
  4. 28 4月, 2013 1 次提交
  5. 04 3月, 2013 1 次提交
  6. 13 2月, 2013 2 次提交
  7. 08 2月, 2013 1 次提交
  8. 04 2月, 2013 1 次提交
  9. 18 1月, 2013 1 次提交
  10. 17 1月, 2013 1 次提交
  11. 25 12月, 2012 1 次提交
    • I
      regulator: s5m8767: Fix probe failure due to stack corruption · 3ef30398
      Inderpal Singh 提交于
      The function sec_reg_read invokes regmap_read which expects unsigned int *
      as the destination address. The existing driver is passing address of local
      variable "val" which is u8. This causes the stack corruption and following
      dump is observed during probe.
      
      Hence change "val" from u8 to unsigned int.
      
      Unable to handle kernel paging request at virtual address 02410020
      pgd = c0004000
      [02410020] *pgd=00000000
      Internal error: Oops: 80000005 [#1] PREEMPT SMP ARM
      Modules linked in:
      CPU: 0    Not tainted  (3.6.0-00696-g98a28b18-dirty #27)
      PC is at 0x2410020
      LR is at _regulator_get_voltage+0x3c/0x70
      pc : [<02410020>]    lr : [<c02395d4>]    psr: 20000013
      sp : cf839b68  ip : 00000000  fp : cf92d410
      r10: 0000cfd0  r9 : c06d9878  r8 : 0000f0a0
      r7 : cf839b70  r6 : cf92d400  r5 : 00000011  r4 : cf000000
      r3 : 02410020  r2 : 00000000  r1 : 00000048  r0 : cf000000
      Flags: nzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
      ...........................
      .................................
      
      [<c02395d4>] (_regulator_get_voltage+0x3c/0x70) from [<c023ad80>] (print_constraints+0x50/0x36c)
      [<c023ad80>] (print_constraints+0x50/0x36c) from [<c023e504>] (set_machine_constraints+0xe8/0x2b0)
      [<c023e504>] (set_machine_constraints+0xe8/0x2b0) from [<c023e9c8>] (regulator_register+0x2fc/0x604)
      [<c023e9c8>] (regulator_register+0x2fc/0x604) from [<c049d628>] (s5m8767_pmic_probe+0x688/0x718)
      [<c049d628>] (s5m8767_pmic_probe+0x688/0x718) from [<c029915c>] (platform_drv_probe+0x18/0x1c)
      [<c029915c>] (platform_drv_probe+0x18/0x1c) from [<c0297dd0>] (really_probe+0x68/0x1f4)
      [<c0297dd0>] (really_probe+0x68/0x1f4) from [<c0298070>] (driver_probe_device+0x30/0x48)
      Signed-off-by: NInderpal Singh <inderpal.singh@linaro.org>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      3ef30398
  12. 11 12月, 2012 3 次提交
  13. 20 11月, 2012 3 次提交
  14. 31 7月, 2012 1 次提交
    • S
      regulator: Fix an s5m8767 build failure · 938e05bf
      Samuel Ortiz 提交于
      Due to a merge conflict we are getting this:
      
      drivers/regulator/s5m8767.c: In function ‘s5m8767_pmic_probe’:
      drivers/regulator/s5m8767.c:575:2: error: implicit declaration of function
      ‘s5m_reg_write’ [-Werror=implicit-function-declaration]
      
      This is fixed by fully converting this driver to the new s5m API.
      
      Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>
      Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      938e05bf
  15. 16 7月, 2012 4 次提交
  16. 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
  17. 25 6月, 2012 1 次提交
  18. 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
  19. 18 6月, 2012 1 次提交
  20. 14 6月, 2012 1 次提交
  21. 13 6月, 2012 1 次提交
  22. 12 5月, 2012 1 次提交
  23. 23 4月, 2012 2 次提交
  24. 10 4月, 2012 3 次提交
  25. 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
  26. 01 4月, 2012 1 次提交
  27. 31 3月, 2012 1 次提交
  28. 14 3月, 2012 1 次提交