31 May, 2019

1 commit

  • Based on 1 normalized pattern(s):

    license terms gnu general public license v2

    extracted by the scancode license scanner the SPDX license identifier

    GPL-2.0-only

    has been chosen to replace the boilerplate/reference in 37 file(s).

    Signed-off-by: Thomas Gleixner
    Reviewed-by: Steve Winslow
    Reviewed-by: Alexios Zavras
    Reviewed-by: Richard Fontana
    Reviewed-by: Allison Randal
    Cc: linux-spdx@vger.kernel.org
    Link: https://lkml.kernel.org/r/20190528170027.724130665@linutronix.de
    Signed-off-by: Greg Kroah-Hartman

    Thomas Gleixner
     

15 Apr, 2019

3 commits


12 Jul, 2016

1 commit

  • There is only one instance of ab8500_regulator_platform_data, and it's
    safe to assume we won't ever merge another one, so it's rather pointless
    to pass it through multiple levels of platform data pointers.

    This moves the structure and everything referenced by it into the
    driver that uses it.

    Signed-off-by: Arnd Bergmann
    Acked-by: Mark Brown
    Signed-off-by: Linus Walleij

    Arnd Bergmann
     

20 Oct, 2014

1 commit


01 Oct, 2013

1 commit


26 Jun, 2013

1 commit


11 Jun, 2013

2 commits

  • Here we use the OF regulator match facility to collect and populate
    initialisation data from Device Tree if we're booting with it enabled.

    Signed-off-by: Lee Jones
    Signed-off-by: Mark Brown

    Lee Jones
     
  • Some platforms don't support the AB8500 external regulators, so instead
    of having a list of is_() calls prior to calling
    ab8500_ext_regulator_init() from ab8500_regulator_probe(), we can only
    register as a platform device on platforms which require them. It means
    we also have more control over them when booting with Device Tree.

    Signed-off-by: Lee Jones
    Signed-off-by: Mark Brown

    Lee Jones
     

08 Jun, 2013

1 commit

  • When registering regulators which have a single voltage through Device
    Tree, the framework insists that the specified voltage is actually set.
    Well in order to do that we need to provide this call-back, where we
    check that the value is sane and return without error. Not that the
    selector isn't populated, but in our case list_voltage doesn't actually
    use it, so we're good.

    Signed-off-by: Lee Jones
    Signed-off-by: Mark Brown

    Lee Jones
     

17 Apr, 2013

2 commits


12 Apr, 2013

1 commit


08 Apr, 2013

3 commits

  • The implementation of ab8500_ext_fixed_get_voltage is identical to
    ab8500_ext_list_voltage. We can avoid the duplicate implementation by just
    remove get_voltage. For fixed regulator, regulator core will call
    list_voltage(rdev, 0) to get voltage if both get_voltage get_voltage_sel are
    not implemented.

    Signed-off-by: Axel Lin
    Acked-by: Lee Jones
    Signed-off-by: Mark Brown

    Axel Lin
     
  • This code was added by commit 0fe17e20a6
    "regulator: ab8500-ext: Add support for AB9540 regulators"
    and commit bd44e2cb "regulator: ab8500: Also check for AB8505 based platforms"

    The original patch[1] is to set info->desc.ops = &ab9540_ext_regulator_ops.

    However, ab9540_ext_regulator_ops is identical to ab8500_ext_regulator_ops[2].
    Thus we can complete remove the unnecessary checking for ab9540 and ab8540.

    [1] https://lkml.org/lkml/2013/3/28/333
    [2] https://lkml.org/lkml/2013/4/1/178

    Signed-off-by: Axel Lin
    Acked-by: Lee Jones
    Signed-off-by: Mark Brown

    Axel Lin
     
  • The intention of this patch is to simplify the code.

    Maintain the is_enabled flag is not trivial, it not only needs to set/clear the
    flag in disable()/enable() but also needs to set the flag in is_enable() to get
    initial status. The only benefit of keeping is_enabled flag is just save a
    register read when set_mode(). Remove is_enabled flag makes the code simpler.

    Signed-off-by: Axel Lin
    Acked-by: Lee Jones
    Signed-off-by: Mark Brown

    Axel Lin
     

03 Apr, 2013

3 commits


01 Apr, 2013

1 commit


30 Mar, 2013

2 commits

  • Support for HW request is added in the external regulator
    driver. A flag in the board configuration can be set to
    let HW control the regulator when there is no SW request.
    This means that the regulator will be put in high power
    mode when there is a SW request and in HW-request mode
    otherwise.

    Signed-off-by: Bengt Jonsson
    Signed-off-by: Lee Jones
    Reviewed-by: Mattias NILSSON
    Reviewed-by: Jonas ABERG
    Signed-off-by: Mark Brown

    Bengt Jonsson
     
  • The ABx500 is capable of controlling three external regulator supplies.
    Most commonly on and off are supported, but if an external regulator
    chipset or power supply supports high-power and low-power mode settings,
    we can control those too.

    Signed-off-by: Lee Jones
    Signed-off-by: Mark Brown

    Lee Jones