11 Feb, 2020

1 commit

  • commit 1112ba02ff1190ca9c15a912f9269e54b46d2d82 upstream.

    The watchdog driver compatible is "dlg,da9062-watchdog" and not
    "dlg,da9062-wdt". Therefore the mfd-core can't populate the of_node and
    fwnode. As result the watchdog driver can't parse the devicetree.

    Fixes: 9b40b030c4ad ("mfd: da9062: Supply core driver")
    Signed-off-by: Marco Felsch
    Acked-by: Guenter Roeck
    Reviewed-by: Adam Thomson
    Signed-off-by: Lee Jones
    Signed-off-by: Greg Kroah-Hartman

    Marco Felsch
     

31 May, 2019

1 commit

  • Based on 3 normalized pattern(s):

    this program is free software you can redistribute it and or modify
    it under the terms of the gnu general public license as published by
    the free software foundation either version 2 of the license or at
    your option any later version this program is distributed in the
    hope that it will be useful but without any warranty without even
    the implied warranty of merchantability or fitness for a particular
    purpose see the gnu general public license for more details

    this program is free software you can redistribute it and or modify
    it under the terms of the gnu general public license as published by
    the free software foundation either version 2 of the license or at
    your option any later version [author] [kishon] [vijay] [abraham]
    [i] [kishon]@[ti] [com] this program is distributed in the hope that
    it will be useful but without any warranty without even the implied
    warranty of merchantability or fitness for a particular purpose see
    the gnu general public license for more details

    this program is free software you can redistribute it and or modify
    it under the terms of the gnu general public license as published by
    the free software foundation either version 2 of the license or at
    your option any later version [author] [graeme] [gregory]
    [gg]@[slimlogic] [co] [uk] [author] [kishon] [vijay] [abraham] [i]
    [kishon]@[ti] [com] [based] [on] [twl6030]_[usb] [c] [author] [hema]
    [hk] [hemahk]@[ti] [com] this program is distributed in the hope
    that it will be useful but without any warranty without even the
    implied warranty of merchantability or fitness for a particular
    purpose see the gnu general public license for more details

    extracted by the scancode license scanner the SPDX license identifier

    GPL-2.0-or-later

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

    Signed-off-by: Thomas Gleixner
    Reviewed-by: Allison Randal
    Reviewed-by: Richard Fontana
    Reviewed-by: Kate Stewart
    Cc: linux-spdx@vger.kernel.org
    Link: https://lkml.kernel.org/r/20190527070033.202006027@linutronix.de
    Signed-off-by: Greg Kroah-Hartman

    Thomas Gleixner
     

16 May, 2018

1 commit

  • Replace multi-line entries in the regmap_range arrays with single
    line macros: regmap_reg_range(). This will leave the static structure
    array entries for regmap_range unaltered. It will significantly reduce
    the line count in the DA9062/61 core file.

    Signed-off-by: Steve Twiss
    Signed-off-by: Lee Jones

    Steve Twiss
     

22 Aug, 2017

1 commit


06 Jul, 2017

2 commits

  • Remove the register DA9062AA_BBAT_CONT (0x0C5) from the DA9061 chip model
    regmap access ranges. This applies to both da9061_aa_readable_ranges[]
    and da9061_aa_writeable_ranges[].

    This change is to correct the DA9061 chip model and align it with the
    latest DA9061 Datasheet.

    This register previously appeared in the DA9061 Datasheet, Revision 3.2,
    01-Mar-2016 and has been removed from later DA9061 datasheet from Dialog,
    Revision 3.3, 04-Apr-2017.

    Signed-off-by: Steve Twiss
    Signed-off-by: Lee Jones

    Steve Twiss
     
  • Remove the register DA9062AA_BBAT_CONT (0x0C5) from the DA9061 chip model
    regmap access ranges. This applies to both da9061_aa_readable_ranges[]
    and da9061_aa_writeable_ranges[].

    This change is to correct the DA9061 chip model and align it with the
    latest DA9061 Datasheet.

    This register previously appeared in the DA9061 Datasheet, Revision 3.2,
    01-Mar-2016 and has been removed from later DA9061 datasheet from Dialog,
    Revision 3.3, 04-Apr-2017.

    Signed-off-by: Steve Twiss
    Signed-off-by: Lee Jones

    Steve Twiss
     

27 Apr, 2017

1 commit

  • MFD support for DA9061 is provided as part of the DA9062 device driver.

    The registers header file adds two new chip variant IDs defined in DA9061
    and DA9062 hardware. The core header file adds new software enumerations
    for listing the valid DA9061 IRQs and a da9062_compatible_types enumeration
    for distinguishing between DA9061/62 devices in software.

    The core source code adds a new .compatible of_device_id entry. This is
    extended from DA9062 to support both "dlg,da9061" and "dlg,da9062". The
    .data entry now holds a reference to the enumerated device type.

    A new regmap_irq_chip model is added for DA9061 and this supports the new
    list of regmap_irq entries. A new mfd_cell da9061_devs[] array lists the
    new sub system components for DA9061. Support is added for a new DA9061
    regmap_config which lists the correct readable, writable and volatile
    ranges for this chip.

    The probe function uses the device tree compatible string to switch on the
    da9062_compatible_types and configure the correct mfd cells, irq chip and
    regmap config.

    Kconfig is updated to reflect support for DA9061 and DA9062 PMICs.

    Signed-off-by: Steve Twiss
    Signed-off-by: Lee Jones

    Steve Twiss
     

16 Mar, 2016

1 commit

  • Add an updated set of registers listed in the core regmap_range volatile
    ranges defined for the DA9062.

    These new registers contain bits that cannot be considered under the full
    control of software. Under various conditions the hardware will set and/or
    automatically clear bit(s) contained in these registers.

    When using a cached version of regmap, the volatility of these registers must
    be identified otherwise the regmap operations may not ensure the registers
    are explicitly altered.

    As well as updating the list of volatile registers, this change will fix a
    corner case discovered in the DA9063 ONKEY which is used by the DA9062 core.

    In the ONKEY case, the CONTROL_B register is now listed as volatile in the
    regmap_range because it contains the bit field NONKEY_LOCK. This bit can be
    altered by hardware, in which case regmap must be notified of its ability
    to be manpiulated outside of software control.

    Signed-off-by: Steve Twiss
    Signed-off-by: Lee Jones

    Steve Twiss
     

31 Oct, 2015

1 commit


11 Aug, 2015

3 commits