28 Aug, 2013

1 commit


07 Jun, 2013

1 commit

  • The driver core clears the driver data to NULL after device_release or on
    probe failure, since commit 0998d0631001288a5974afc0b2a5f568bcdecb4d
    (device-core: Ensure drvdata = NULL when no driver is bound). Thus, it is
    not needed to manually clear the device driver data to NULL.

    Signed-off-by: Jingoo Han
    Acked-by: Lee Jones
    Signed-off-by: Anton Vorontsov

    Jingoo Han
     

07 Mar, 2013

14 commits


23 Jan, 2013

9 commits


16 Jan, 2013

6 commits


06 Jan, 2013

2 commits


12 Dec, 2012

1 commit


11 Dec, 2012

4 commits

  • Now that we always pass platform specific battery management data
    through platform_data instead of obtaining it via different means
    depending the way be boot the system (DT or ATAGs); we need to
    re-jiggle the way we acquire it in the driver start-up functions.
    Now it is wrong for it to be missing, but we still allow Device
    Tree code to fiddle with it once we've confirmed it's there.

    Signed-off-by: Lee Jones

    Lee Jones
     
  • Currently the AB8500 battery management subsystem receives platform
    specific information via two different means depending on how the
    platform is booted. If DT is not enabled, a reference to a *_bm_data
    data structure containing each platform specific attribute is passed
    though platform_data. However, if DT is enabled, then platform_data
    is empty and the reference is gained though a DT specific probe
    function. There are two issues here 1) the same reference is
    being collected each time and 2) the DT way doesn't allow any
    provisions to select different platform specific attributes, which
    kind of defeats the object.

    Cc: Samuel Ortiz
    Signed-off-by: Lee Jones

    Lee Jones
     
  • The platform specific battery management configuration data structure
    is currently called 'bat' short for 'battery'; however, it contains
    information for all components of the battery management group, rather
    than information pertaining to the battery itself - there are other
    structures for that. So, in keeping with its structure namesake
    'abx500_bm_data', we rename it to 'bm' here. Using similar logic,
    we're also renaming 'bmdevs_of_probe' to the more device specific
    'ab8500_bm_of_probe'.

    Signed-off-by: Lee Jones

    Lee Jones
     
  • There is no state machine in the AB to step up/down the charger
    current to avoid dips and spikes on VBUS and VBAT when charging
    is started. Instead this is implemented in SW.

    Signed-off-by: Johan Bjornstedt
    Signed-off-by: Mattias Wallin
    Signed-off-by: Lee Jones
    Reviewed-by: Karl KOMIEROWSKI

    Johan Bjornstedt
     

29 Nov, 2012

2 commits