1. 18 5月, 2012 1 次提交
  2. 17 4月, 2012 1 次提交
    • P
      mfd: Fix modular builds of rc5t583 regulator support · 82ea267f
      Paul Gortmaker 提交于
      The combination of commit 1b1247dd
      
          "mfd: Add support for RICOH PMIC RC5T583"
      
      and commit 6ffc3270
      
          "regulator: Add support for RICOH PMIC RC5T583 regulator"
      
      are causing the i386 allmodconfig builds to fail with this:
      
        ERROR: "rc5t583_update" [drivers/regulator/rc5t583-regulator.ko] undefined!
        ERROR: "rc5t583_set_bits" [drivers/regulator/rc5t583-regulator.ko] undefined!
        ERROR: "rc5t583_clear_bits" [drivers/regulator/rc5t583-regulator.ko] undefined!
        ERROR: "rc5t583_read" [drivers/regulator/rc5t583-regulator.ko] undefined!
      
      and this:
      
        ERROR: "rc5t583_ext_power_req_config" [drivers/regulator/rc5t583-regulator.ko] undefined!
      
      For the 1st four, make the simple ops static inline, instead of
      polluting the namespace with trivial exports.  For the last one,
      add an EXPORT_SYMBOL.
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      82ea267f
  3. 16 4月, 2012 2 次提交
  4. 28 3月, 2012 2 次提交
  5. 27 3月, 2012 5 次提交
    • A
      ab8500_fg: Get rid of 'struct battery_type' · c34a61b4
      Anton Vorontsov 提交于
      The struct is duplicated, plus causes the following flood:
      
        CC      drivers/power/ab8500_fg.o
      ab8500_fg.c: In function ‘ab8500_fg_get_ext_psy_data’:
      b8500_fg.c:2081:8: warning: assignment from incompatible pointer type [enabled by default]
      Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
      c34a61b4
    • A
      ab8500_fg: Get rid of 'struct v_to_cap' · 450ceb2b
      Anton Vorontsov 提交于
      The struct is duplicated, plus when used it causes the following
      warnings:
      
        CHECK   drivers/power/ab8500_fg.c
      ab8500_fg.c:818:13: warning: incorrect type in assignment (different base types)
      ab8500_fg.c:818:13:    expected struct v_to_cap *tbl
      ab8500_fg.c:818:13:    got struct abx500_v_to_cap *const v_to_cap_tbl
        CC      drivers/power/ab8500_fg.o
      ab8500_fg.c: In function 'ab8500_fg_volt_to_capacity':
      ab8500_fg.c:818:6: warning: assignment from incompatible pointer type [enabled by default]
      Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
      450ceb2b
    • A
      ab8500_btemp: Get rid of 'enum adc_therm' · d329129e
      Anton Vorontsov 提交于
      This is the same as abx500_adc_therm, but when the former is used,
      the following warning flood pops up:
      
      drivers/power/ab8500_btemp.c: In function 'ab8500_btemp_batctrl_volt_to_res':
      ab8500_btemp.c:150:25: warning: comparison between 'enum abx500_adc_therm' and 'enum adc_therm' [-Wenum-compare]
      ab8500_btemp.c: In function 'ab8500_btemp_curr_source_enable':
      ab8500_btemp.c:212:25: warning: comparison between 'enum abx500_adc_therm' and 'enum adc_therm' [-Wenum-compare]
      ab8500_btemp.c:244:32: warning: comparison between 'enum abx500_adc_therm' and 'enum adc_therm' [-Wenum-compare]
      ab8500_btemp.c: In function 'ab8500_btemp_measure_temp':
      ab8500_btemp.c:462:25: warning: comparison between 'enum abx500_adc_therm' and 'enum adc_therm' [-Wenum-compare]
      ab8500_btemp.c: In function 'ab8500_btemp_id':
      ab8500_btemp.c:528:121: warning: comparison between 'enum abx500_adc_therm' and 'enum adc_therm' [-Wenum-compare]
      ab8500_btemp.c:551:25: warning: comparison between 'enum abx500_adc_therm' and 'enum adc_therm' [-Wenum-compare]
      
      This patch fixes the issue by switching the driver to use more
      namespace-friendly enum.
      Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
      d329129e
    • A
      ab8500-charger: AB8500 charger driver · 84edbeea
      Arun Murthy 提交于
      This driver is responsible for detecting the ac/usb plugin and also includes
      function to enable ac/usb charging and re-kick the watchdog.
      It registers with the power supply class and provides information to the user
      space. The information include status of ac/usb charger device.
      This information in turn will be used by the abx500 charging algorithm driver
      to enable/disable and monitor charging.
      Signed-off-by: NArun Murthy <arun.murthy@stericsson.com>
      Acked-by: NLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
      84edbeea
    • A
      abx500-chargalg: Add abx500 charging algorithm · 1668f811
      Arun Murthy 提交于
      This is a charging algorithm driver for abx500 variants. It is the central
      entity for battery driver and is responsible for charging and monitoring
      the battery driver. It is a hardware independant driver and also monitors
      other abx500 power supply devices.
      Signed-off-by: NArun Murthy <arun.murthy@stericsson.com>
      Acked-by: NLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
      1668f811
  6. 22 3月, 2012 1 次提交
  7. 20 3月, 2012 1 次提交
  8. 17 3月, 2012 12 次提交
  9. 16 3月, 2012 1 次提交
    • P
      device.h: audit and cleanup users in main include dir · 313162d0
      Paul Gortmaker 提交于
      The <linux/device.h> header includes a lot of stuff, and
      it in turn gets a lot of use just for the basic "struct device"
      which appears so often.
      
      Clean up the users as follows:
      
      1) For those headers only needing "struct device" as a pointer
      in fcn args, replace the include with exactly that.
      
      2) For headers not really using anything from device.h, simply
      delete the include altogether.
      
      3) For headers relying on getting device.h implicitly before
      being included themselves, now explicitly include device.h
      
      4) For files in which doing #1 or #2 uncovers an implicit
      dependency on some other header, fix by explicitly adding
      the required header(s).
      
      Any C files that were implicitly relying on device.h to be
      present have already been dealt with in advance.
      
      Total removals from #1 and #2: 51.  Total additions coming
      from #3: 9.  Total other implicit dependencies from #4: 7.
      
      As of 3.3-rc1, there were 110, so a net removal of 42 gives
      about a 38% reduction in device.h presence in include/*
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      313162d0
  10. 12 3月, 2012 1 次提交
  11. 07 3月, 2012 13 次提交