1. 25 9月, 2012 1 次提交
  2. 22 9月, 2012 2 次提交
    • P
      pda_power: Remove ac_draw_failed goto and label · c10a002a
      Paul Parsons 提交于
      A previous patch added the ac_draw_failed goto and label to
      pda_power_probe(). The goto would be invoked after a failed call to
      regulator_get().
      
      However the way ac_draw is used - always after a check for NULL - suggests
      that a failed call to regulator_get() was not fatal.
      
      This patch removes the ac_draw_failed goto and label, partly reverting the
      previous patch.
      
      This patch also removes the assignment of an error code to ret after a
      failed call to regulator_get(), since the error code is now never used.
      Signed-off-by: NPaul Parsons <lost.distance@yahoo.com>
      Cc: Philipp Zabel <philipp.zabel@gmail.com>
      Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
      c10a002a
    • C
      charger-manager: Add support sysfs entry for charger · 3950c786
      Chanwoo Choi 提交于
      This patch add support sysfs entry for each charger(regulator).
      Charger-manager use one or more chargers for charging battery but some
      charger isn't necessary on specific scenario. So, if some charger isn't
      needed, can disable specific charger through 'externally_control' entry
      while system is on state and confirm the information(name, state) of
      charger.
      
      The list of added sysfs entry
      - /sys/class/power_supply/battery/chargers/charger.[index]/name
        show name of charger(regulator)
      - /sys/class/power_supply/battery/chargers/charger.[index]/state
        show either enabled or disabled state of charger
      - /sys/class/power_supply/battery/chargers/charger.[index]/externally_control
      
      If 'externally_control' of specific charger is 1, Charger-manager cannot
      enable regulator for charging when charger cable is attached and charger
      must be maintained with disabled state. If 'externally_control' is zero,
      Charger-manager usually can control to enable/disable regulator.
      Signed-off-by: NChanwoo Choi <cw00.choi@samsung.com>
      Signed-off-by: NMyungjoo Ham <myungjoo.ham@samsung.com>
      Signed-off-by: NKyungmin Park <kyungmin.park@samsung.com>
      Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
      3950c786
  3. 21 9月, 2012 33 次提交
  4. 16 9月, 2012 1 次提交
    • M
      mfd: core: Push irqdomain mapping out into devices · 0848c94f
      Mark Brown 提交于
      Currently the MFD core supports remapping MFD cell interrupts using an
      irqdomain but only if the MFD is being instantiated using device tree
      and only if the device tree bindings use the pattern of registering IPs
      in the device tree with compatible properties.  This will be actively
      harmful for drivers which support non-DT platforms and use this pattern
      for their DT bindings as it will mean that the core will silently change
      remapping behaviour and it is also limiting for drivers which don't do
      DT with this particular pattern.  There is also a potential fragility if
      there are interrupts not associated with MFD cells and all the cells are
      omitted from the device tree for some reason.
      
      Instead change the code to take an IRQ domain as an optional argument,
      allowing drivers to take the decision about the parent domain for their
      interrupts.  The one current user of this feature is ab8500-core, it has
      the domain lookup pushed out into the driver.
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      0848c94f
  5. 23 8月, 2012 3 次提交
    • F
      mfd: lpc_ich: Fix a 3.5 kernel regression for iTCO_wdt driver · a0e35322
      Feng Tang 提交于
      There are many reports (including 2 of my machines) that iTCO_wdt watchdog
      driver fails to be initialized in 3.5 kernel with error message like:
      
      [    5.265175] ACPI Warning: 0x00001060-0x0000107f SystemIO conflicts with Region \_SB_.PCI0.LPCB.TCOI 1 (20120320/utaddress-251)
      [    5.265192] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
      [    5.265206] lpc_ich: Resource conflict(s) found affecting iTCO_wdt
      
      The root cause the iTCO_wdt driver in 3.4 probes the HW IO resource from
      LPC's PCI config space, while in 3.5 kernel it relies on lpc_ich driver
      for the probe, which adds a new acpi_check_resource_conflict() check, and
      give up the probe if there is any conflict with ACPI.
      
      Fix it by removing all the checks for iTCO_wdt to keep the same behavior as
      3.4 kernel.
      https://bugzilla.kernel.org/show_bug.cgi?id=44991
      
      Actually the same check could be removed for the gpio-ich in lpc_ich.c,
      but I'm not sure if it will cause problems.
      Signed-off-by: NFeng Tang <feng.tang@intel.com>
      Cc: Aaron Sierra <asierra@xes-inc.com>
      Cc: Wim Van Sebroeck <wim@iguana.be>
      Cc: Len Brown <len.brown@intel.com>
      Cc: Bob Moore <robert.moore@intel.com>
      Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      a0e35322
    • R
      power_supply: Add new power supply properties CHARGE_CURRENT/VOLTAGE_MAX · 2815b786
      Ramakrishna Pallala 提交于
      There are different types of chargers avalibale like AC, Solar, USB,
      etc..  Even in USB we have different types SDP/DCP/CDP/ACA and all these
      chargers have different o/p ratings. For example SDP supports only 500mA
      of charge current whereas AC charger can support upto 8A or more.
      
      Similarly batteries also come with charge current and voltage ratings
      and these ratings vary depending on its capacity and the technology
      used.
      
      This patch adds two new power supply properties
      CONSTANT_CHARGE_CURRENT_MAX and CONSTANT_CHARGE_CURRENT_MAX.
      Signed-off-by: NRamakrishna Pallala <ramakrishna.pallala@intel.com>
      Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
      2815b786
    • A
      charger-manager: Fix struct charger_desc's misleading comment · c6b2744c
      Anton Vorontsov 提交于
      The comment says that charger_regulators is an array of
      regulator_bulk_data, which is not true, since it's actually a pointer
      to 'struct charger_regulator'.
      Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
      c6b2744c