mfd: add support for max77650 PMIC
Subsystems (8)
v9 cover mfd: add support for max77650 PMIC
From: Bartosz Golaszewski <[email protected]>
This series adds support for max77650 ultra low-power PMIC. It provides the core mfd driver and a set of five sub-drivers for the regulator, power supply, gpio, leds and input subsystems.
Patches 1-4 add the DT binding documents. Patch 5 documents mfd_add_devices(). Patches 6-10 add all drivers. Last patch adds a MAINTAINERS entry for this device.
The regulator part is already upstream.
v1 -> v2:
=========
General:
- use C++ style comments for the SPDX license identifier and the copyright header
- s/MODULE_LICENSE("GPL")/MODULE_LICENSE("GPL v2")/
- lookup the virtual interrupt numbers in the MFD driver, setup resources for child devices and use platform_get_irq_byname() in sub-drivers
- picked up review tags
- use devm_request_any_context_irq() for interrupt requests
LEDs:
- changed the max77650_leds_ prefix to max77650_led_
- drop the max77650_leds structure as the only field it held was the regmap pointer, move said pointer to struct max77650_led
- change the driver name to "max77650-led"
- drop the last return value check and return the result of regmap_write() directly
- change the labeling scheme to one consistent with other LED drivers
ONKEY:
- drop the key reporting helper and call the input functions directly from interrupt handlers
- rename the rv local variable to error
- drop parent device asignment
Regulator:
- drop the unnecessary init_data lookup from the driver code
- drop unnecessary include
Charger:
- disable the charger on driver remove
- change the power supply type to POWER_SUPPLY_TYPE_USB
GPIO:
- drop interrupt support until we have correct implementation of hierarchical irqs in gpiolib
v2 -> v3:
=========
General:
- dropped regulator patches as they're already in Mark Brown's branch
LED:
- fix the compatible string in the DT binding example
- use the max_brightness property
- use a common prefix ("MAX77650_LED") for all defines in the driver
MFD:
- add the MODULE_DEVICE_TABLE()
- add a sentinel to the of_device_id array
- constify the pointers to irq names
- use an enum instead of defines for interrupt indexes
v3 -> v4:
=========
GPIO:
- as discussed with Linus Walleij: the gpio-controller is now part of the core mfd module (we don't spawn a sub-node anymore), the binding document for GPIO has been dropped, the GPIO properties have been defined in the binding document for the mfd core, the interrupt functionality has been reintroduced with the irq directly passed from the mfd part
- due to the above changes the Reviewed-by tag from Linus was dropped
v4 -> v5:
=========
General:
- add a patch documenting mfd_add_devices()
MFD:
- pass the regmap irq_chip irq domain to mfd over mfd_add_devices so that the hw interrupts from resources can be correctly mapped to virtual irqs
- remove the enum listing cell indexes
- extend Kconfig help
- add a link to the programming manual
- use REGMAP_IRQ_REG() for regmap interrupts (except for GPI which has is composed of two hw interrupts for rising and falling edge)
- add error messages in probe
- use PLATFORM_DEVID_NONE constant in devm_mfd_add_devices()
- set irq_base to 0 in regmap_add_irq_chip() as other users to, it's only relevant if it's > 0
Charger:
- use non-maxim specific property names for minimum input voltage and current limit
- code shrink by using the enable/disable charger helpers everywhere
- use more descriptive names for constants
Onkey:
- use EV_SW event type for slide mode
LED:
- remove stray " from Kconfig help
v5 -> v6:
=========
MFD:
- remove stray spaces in the binding document
- rename the example dt node
- remove unnecessary interrupt-parent property from the bindings
LED:
- add a missing dependency on LEDS_CLASS to Kconfig
Onkey:
- use boolean for the slide button property
Charger:
- fix the property names in DT example
- make constants even more readable
v6 -> v7:
=========
Charger:
- rename the current limit property to current-limit-microamp
v7 -> v8:
=========
General:
- collected acks from Lee
- changed the documentation for mfd_add_devices() as suggested by Lee
- rebased on top of v5.1-rc3
v8 > v9:
========
General:
- collected new tags
- rebased on top of v5.1-rc4
MFD:
- various improvements in error messages
- coding style tweaks
Charger:
- named the two optional properties in a more descriptive way, so that we can make them generic for charger bindings if more potential users appear
Bartosz Golaszewski (11):
dt-bindings: mfd: add DT bindings for max77650
dt-bindings: power: supply: add DT bindings for max77650
dt-bindings: leds: add DT bindings for max77650
dt-bindings: input: add DT bindings for max77650
mfd: core: document mfd_add_devices()
mfd: max77650: new core mfd driver
power: supply: max77650: add support for battery charger
gpio: max77650: add GPIO support
leds: max77650: add LEDs support
input: max77650: add onkey support
MAINTAINERS: add an entry for max77650 mfd driver
.../bindings/input/max77650-onkey.txt | 26 ++ .../bindings/leds/leds-max77650.txt | 57 +++ .../devicetree/bindings/mfd/max77650.txt | 46 +++ .../power/supply/max77650-charger.txt | 28 ++ MAINTAINERS | 14 + drivers/gpio/Kconfig | 7 + drivers/gpio/Makefile | 1 + drivers/gpio/gpio-max77650.c | 190 +++++++++ drivers/input/misc/Kconfig | 9 + drivers/input/misc/Makefile | 1 + drivers/input/misc/max77650-onkey.c | 121 ++++++ drivers/leds/Kconfig | 6 + drivers/leds/Makefile | 1 + drivers/leds/leds-max77650.c | 147 +++++++ drivers/mfd/Kconfig | 14 + drivers/mfd/Makefile | 1 + drivers/mfd/max77650.c | 232 +++++++++++ drivers/mfd/mfd-core.c | 13 + drivers/power/supply/Kconfig | 7 + drivers/power/supply/Makefile | 1 + drivers/power/supply/max77650-charger.c | 368 ++++++++++++++++++ include/linux/mfd/max77650.h | 59 +++ 22 files changed, 1349 insertions(+) create mode 100644 Documentation/devicetree/bindings/input/max77650-onkey.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-max77650.txt create mode 100644 Documentation/devicetree/bindings/mfd/max77650.txt create mode 100644 Documentation/devicetree/bindings/power/supply/max77650-charger.txt create mode 100644 drivers/gpio/gpio-max77650.c create mode 100644 drivers/input/misc/max77650-onkey.c create mode 100644 drivers/leds/leds-max77650.c create mode 100644 drivers/mfd/max77650.c create mode 100644 drivers/power/supply/max77650-charger.c create mode 100644 include/linux/mfd/max77650.h
Signature · 1 line
2.21.0
PATCH v9 1/11 dt-bindings: mfd: add DT bindings for max77650
From: Bartosz Golaszewski <[email protected]>
Add a DT binding document for max77650 ultra-low power PMIC. This describes the core mfd device and the GPIO module.
--- .../devicetree/bindings/mfd/max77650.txt | 46 +++++++++++++++++++ 1 file changed, 46 insertions(+) create mode 100644 Documentation/devicetree/bindings/mfd/max77650.txt
Documentation/devicetree/bindings/mfd/max77650.txt new file +46 -0
@@ -0,0 +1,46 @@ +MAX77650 ultra low-power PMIC from Maxim Integrated. + +Required properties: +------------------- +- compatible: Must be "maxim,max77650" +- reg: I2C device address. +- interrupts: The interrupt on the parent the controller is + connected to. +- interrupt-controller: Marks the device node as an interrupt controller. +- #interrupt-cells: Must be <2>. + +- gpio-controller: Marks the device node as a gpio controller. +- #gpio-cells: Must be <2>. The first cell is the pin number and + the second cell is used to specify the gpio active + state. + +Optional properties: +-------------------- +gpio-line-names: Single string containing the name of the GPIO line. + +The GPIO-controller module is represented as part of the top-level PMIC +node. The device exposes a single GPIO line. + +For device-tree bindings of other sub-modules (regulator, power supply, +LEDs and onkey) refer to the binding documents under the respective +sub-system directories. + +For more details on GPIO bindings, please refer to the generic GPIO DT +binding document <devicetree/bindings/gpio/gpio.txt>. + +Example: +-------- + + pmic@48 { + compatible = "maxim,max77650"; + reg = <0x48>; + + interrupt-controller; + interrupt-parent = <&gpio2>; + #interrupt-cells = <2>; + interrupts = <3 IRQ_TYPE_LEVEL_LOW>; + + gpio-controller; + #gpio-cells = <2>; + gpio-line-names = "max77650-charger"; + };
Signature · 1 line
2.21.0
PATCH v9 2/11 dt-bindings: power: supply: add DT bindings for max77650
In reply to Bartosz GolaszewskiFrom: Bartosz Golaszewski <[email protected]>
Add the DT binding document for the battery charger module of max77650.
--- .../power/supply/max77650-charger.txt | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 Documentation/devicetree/bindings/power/supply/max77650-charger.txt
Documentation/devicetree/bindings/power/supply/max77650-charger.txt new file +28 -0
@@ -0,0 +1,28 @@ +Battery charger driver for MAX77650 PMIC from Maxim Integrated. + +This module is part of the MAX77650 MFD device. For more details +see Documentation/devicetree/bindings/mfd/max77650.txt. + +The charger is represented as a sub-node of the PMIC node on the device tree. + +Required properties: +-------------------- +- compatible: Must be "maxim,max77650-charger" + +Optional properties: +-------------------- +- input-voltage-min-microvolt: Minimum CHGIN regulation voltage. Must be one + of: 4000000, 4100000, 4200000, 4300000, + 4400000, 4500000, 4600000, 4700000. +- input-current-limit-microamp: CHGIN input current limit (in microamps). Must + be one of: 95000, 190000, 285000, 380000, + 475000. + +Example: +-------- + + charger { + compatible = "maxim,max77650-charger"; + min-microvolt = <4200000>; + curr-lim-microamp = <285000>; + };
Signature · 1 line
2.21.0
Sebastian Reichel
maintainerRe: [PATCH v9 02/11] dt-bindings: power: supply: add DT bindings for max77650
Hi,
Quoted 25 lines · Bartosz Golaszewski
From: Bartosz Golaszewski <[email protected]>
Add the DT binding document for the battery charger module of max77650.
Signed-off-by Bartosz Golaszewski <[email protected]>--- .../power/supply/max77650-charger.txt | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 Documentation/devicetree/bindings/power/supply/max77650-charger.txtDocumentation/devicetree/bindings/power/supply/max77650-charger.txt new file +9
-0@@ -0,0 +1,28 @@ +Battery charger driver for MAX77650 PMIC from Maxim Integrated. + +This module is part of the MAX77650 MFD device. For more details +see Documentation/devicetree/bindings/mfd/max77650.txt. + +The charger is represented as a sub-node of the PMIC node on the device tree. + +Required properties: +--------------------
Documentation/devicetree/bindings/power/supply/max77650-charger.txt line 19
Quoted 10 lines
Documentation/devicetree/bindings/power/supply/max77650-charger.txt new file +10
-0+- compatible: Must be "maxim,max77650-charger" + +Optional properties: +-------------------- +- input-voltage-min-microvolt: Minimum CHGIN regulation voltage. Must be one + of: 4000000, 4100000, 4200000, 4300000, + 4400000, 4500000, 4600000, 4700000. +- input-current-limit-microamp: CHGIN input current limit (in microamps). Must + be one of: 95000, 190000, 285000, 380000, + 475000.
The binding looks good to me.
Documentation/devicetree/bindings/power/supply/max77650-charger.txt line 28
Quoted 8 lines
Documentation/devicetree/bindings/power/supply/max77650-charger.txt new file +8
-0+Example: +-------- + + charger { + compatible = "maxim,max77650-charger"; + min-microvolt = <4200000>; + curr-lim-microamp = <285000>; + };
The example does not match the binding.
-- Sebastian
PATCH v9 3/11 dt-bindings: leds: add DT bindings for max77650
In reply to Bartosz GolaszewskiFrom: Bartosz Golaszewski <[email protected]>
Add the DT binding document for the LEDs module of max77650.
--- .../bindings/leds/leds-max77650.txt | 57 +++++++++++++++++++ 1 file changed, 57 insertions(+) create mode 100644 Documentation/devicetree/bindings/leds/leds-max77650.txt
Documentation/devicetree/bindings/leds/leds-max77650.txt new file +57 -0
@@ -0,0 +1,57 @@ +LED driver for MAX77650 PMIC from Maxim Integrated. + +This module is part of the MAX77650 MFD device. For more details +see Documentation/devicetree/bindings/mfd/max77650.txt. + +The LED controller is represented as a sub-node of the PMIC node on +the device tree. + +This device has three current sinks. + +Required properties: +-------------------- +- compatible: Must be "maxim,max77650-led" +- #address-cells: Must be <1>. +- #size-cells: Must be <0>. + +Each LED is represented as a sub-node of the LED-controller node. Up to +three sub-nodes can be defined. + +Required properties of the sub-node: +------------------------------------ + +- reg: Must be <0>, <1> or <2>. + +Optional properties of the sub-node: +------------------------------------ + +- label: See Documentation/devicetree/bindings/leds/common.txt +- linux,default-trigger: See Documentation/devicetree/bindings/leds/common.txt + +For more details, please refer to the generic GPIO DT binding document +<devicetree/bindings/gpio/gpio.txt>. + +Example: +-------- + + leds { + compatible = "maxim,max77650-led"; + #address-cells = <1>; + #size-cells = <0>; + + led@0 { + reg = <0>; + label = "blue:usr0"; + }; + + led@1 { + reg = <1>; + label = "red:usr1"; + linux,default-trigger = "heartbeat"; + }; + + led@2 { + reg = <2>; + label = "green:usr2"; + }; + };
Signature · 1 line
2.21.0
PATCH v9 4/11 dt-bindings: input: add DT bindings for max77650
In reply to Bartosz GolaszewskiFrom: Bartosz Golaszewski <[email protected]>
Add the DT binding document for the onkey module of max77650.
--- .../bindings/input/max77650-onkey.txt | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 Documentation/devicetree/bindings/input/max77650-onkey.txt
Documentation/devicetree/bindings/input/max77650-onkey.txt new file +26 -0
@@ -0,0 +1,26 @@ +Onkey driver for MAX77650 PMIC from Maxim Integrated. + +This module is part of the MAX77650 MFD device. For more details +see Documentation/devicetree/bindings/mfd/max77650.txt. + +The onkey controller is represented as a sub-node of the PMIC node on +the device tree. + +Required properties: +-------------------- +- compatible: Must be "maxim,max77650-onkey". + +Optional properties: +- linux,code: The key-code to be reported when the key is pressed. + Defaults to KEY_POWER. +- maxim,onkey-slide: The system's button is a slide switch, not the default + push button. + +Example: +-------- + + onkey { + compatible = "maxim,max77650-onkey"; + linux,code = <KEY_END>; + maxim,onkey-slide; + };
Signature · 1 line
2.21.0
PATCH v9 5/11 mfd: core: document mfd_add_devices()
In reply to Bartosz GolaszewskiFrom: Bartosz Golaszewski <[email protected]>
Add a kernel doc for mfd_add_devices().
--- drivers/mfd/mfd-core.c | 13 +++++++++++++ 1 file changed, 13 insertions(+)
drivers/mfd/mfd-core.c +13 -0
@@ -269,6 +269,19 @@ static int mfd_add_device(struct device *parent, int id,return ret; } +/** +* mfd_add_devices - register child devices +* +* @parent: Pointer to parent device. +* @id: Can be PLATFORM_DEVID_AUTO to let the Platform API take care +* of device numbering, or will be added to a device's cell_id. +* @cells: Array of (struct mfd_cell)s describing child devices. +* @n_devs: Number of child devices to register. +* @mem_base: Parent register range resource for child devices. +* @irq_base: Base of the range of virtual interrupt numbers allocated for +* this MFD device. Unused if @domain is specified. +* @domain: Interrupt domain to create mappings for hardware interrupts. +*/ int mfd_add_devices(struct device *parent, int id, const struct mfd_cell *cells, int n_devs, struct resource *mem_base,
Signature · 1 line
2.21.0
PATCH v9 6/11 mfd: max77650: new core mfd driver
In reply to Bartosz GolaszewskiFrom: Bartosz Golaszewski <[email protected]>
Add the core mfd driver for max77650 PMIC. We define five sub-devices for which the drivers will be added in subsequent patches.
--- drivers/mfd/Kconfig | 14 +++ drivers/mfd/Makefile | 1 + drivers/mfd/max77650.c | 232 +++++++++++++++++++++++++++++++++++ include/linux/mfd/max77650.h | 59 +++++++++ 4 files changed, 306 insertions(+) create mode 100644 drivers/mfd/max77650.c create mode 100644 include/linux/mfd/max77650.h
drivers/mfd/Kconfig +14 -0
@@ -733,6 +733,20 @@ config MFD_MAX77620 provides common support for accessing the device; additional drivers must be enabled in order to use the functionality of the device. +config MFD_MAX77650 + tristate "Maxim MAX77650/77651 PMIC Support" + depends on I2C + depends on OF || COMPILE_TEST + select MFD_CORE + select REGMAP_I2C + help + Say Y here to add support for Maxim Semiconductor MAX77650 and + MAX77651 Power Management ICs. This is the core multifunction + driver for interacting with the device. The module name is + 'max77650'. Additional drivers can be enabled in order to use + the following functionalities of the device: GPIO, regulator, + charger, LED, onkey. + config MFD_MAX77686 tristate "Maxim Semiconductor MAX77686/802 PMIC Support" depends on I2C
drivers/mfd/Makefile +1 -0
@@ -155,6 +155,7 @@ obj-$(CONFIG_MFD_DA9150) += da9150-core.o obj-$(CONFIG_MFD_MAX14577) += max14577.o obj-$(CONFIG_MFD_MAX77620) += max77620.o +obj-$(CONFIG_MFD_MAX77650) += max77650.o obj-$(CONFIG_MFD_MAX77686) += max77686.o obj-$(CONFIG_MFD_MAX77693) += max77693.o obj-$(CONFIG_MFD_MAX77843) += max77843.o
drivers/mfd/max77650.c new file +232 -0
232 lines not on this page · raw message
include/linux/mfd/max77650.h new file +59 -0
59 lines not on this page · raw message
Signature · 1 line
2.21.0
PATCH v9 7/11 power: supply: max77650: add support for battery charger
In reply to Bartosz GolaszewskiFrom: Bartosz Golaszewski <[email protected]>
Add basic support for the battery charger for max77650 PMIC.
--- drivers/power/supply/Kconfig | 7 + drivers/power/supply/Makefile | 1 + drivers/power/supply/max77650-charger.c | 368 ++++++++++++++++++++++++ 3 files changed, 376 insertions(+) create mode 100644 drivers/power/supply/max77650-charger.c
drivers/power/supply/Kconfig +7 -0
@@ -499,6 +499,13 @@ config CHARGER_DETECTOR_MAX14656 Revision 1.2 and can be found e.g. in Kindle 4/5th generation readers and certain LG devices. +config CHARGER_MAX77650 + tristate "Maxim MAX77650 battery charger driver" + depends on MFD_MAX77650 + help + Say Y to enable support for the battery charger control of MAX77650 + PMICs. + config CHARGER_MAX77693 tristate "Maxim MAX77693 battery charger driver" depends on MFD_MAX77693
drivers/power/supply/Makefile +1 -0
@@ -70,6 +70,7 @@ obj-$(CONFIG_CHARGER_MANAGER) += charger-manager.o obj-$(CONFIG_CHARGER_LTC3651) += ltc3651-charger.o obj-$(CONFIG_CHARGER_MAX14577) += max14577_charger.o obj-$(CONFIG_CHARGER_DETECTOR_MAX14656) += max14656_charger_detector.o +obj-$(CONFIG_CHARGER_MAX77650) += max77650-charger.o obj-$(CONFIG_CHARGER_MAX77693) += max77693_charger.o obj-$(CONFIG_CHARGER_MAX8997) += max8997_charger.o obj-$(CONFIG_CHARGER_MAX8998) += max8998_charger.o
drivers/power/supply/max77650-charger.c new file +368 -0
368 lines not on this page · raw message
Signature · 1 line
2.21.0
Re: [PATCH v9 07/11] power: supply: max77650: add support for battery charger
Hi,
Quoted 7 lines · Bartosz Golaszewski
From: Bartosz Golaszewski <[email protected]>
Add basic support for the battery charger for max77650 PMIC.
Signed-off-by Bartosz Golaszewski <[email protected]>Reviewed-by Linus Walleij <[email protected]>---
-- Sebastian
Quoted 413 lines
drivers/power/supply/Kconfig | 7 + drivers/power/supply/Makefile | 1 + drivers/power/supply/max77650-charger.c | 368 ++++++++++++++++++++++++ 3 files changed, 376 insertions(+) create mode 100644 drivers/power/supply/max77650-charger.cdrivers/power/supply/Kconfig +7
-0@@ -499,6 +499,13 @@ config CHARGER_DETECTOR_MAX14656 Revision 1.2 and can be found e.g. in Kindle 4/5th generation readers and certain LG devices. +config CHARGER_MAX77650 + tristate "Maxim MAX77650 battery charger driver" + depends on MFD_MAX77650 + help + Say Y to enable support for the battery charger control of MAX77650 + PMICs. + config CHARGER_MAX77693 tristate "Maxim MAX77693 battery charger driver" depends on MFD_MAX77693drivers/power/supply/Makefile +1
-0@@ -70,6 +70,7 @@ obj-$(CONFIG_CHARGER_MANAGER) += charger-manager.o obj-$(CONFIG_CHARGER_LTC3651) += ltc3651-charger.o obj-$(CONFIG_CHARGER_MAX14577) += max14577_charger.o obj-$(CONFIG_CHARGER_DETECTOR_MAX14656) += max14656_charger_detector.o +obj-$(CONFIG_CHARGER_MAX77650) += max77650-charger.o obj-$(CONFIG_CHARGER_MAX77693) += max77693_charger.o obj-$(CONFIG_CHARGER_MAX8997) += max8997_charger.o obj-$(CONFIG_CHARGER_MAX8998) += max8998_charger.odrivers/power/supply/max77650-charger.c new file +368
-0@@ -0,0 +1,368 @@ +// SPDX-License-Identifier: GPL-2.0 +// +// Copyright (C) 2018 BayLibre SAS +// Author: Bartosz Golaszewski <[email protected]> +// +// Battery charger driver for MAXIM 77650/77651 charger/power-supply. + +#include <linux/i2c.h> +#include <linux/interrupt.h> +#include <linux/mfd/max77650.h> +#include <linux/module.h> +#include <linux/platform_device.h> +#include <linux/power_supply.h> +#include <linux/regmap.h> + +#define MAX77650_CHARGER_ENABLED BIT(0) +#define MAX77650_CHARGER_DISABLED 0x00 +#define MAX77650_CHARGER_CHG_EN_MASK BIT(0) + +#define MAX77650_CHG_DETAILS_MASK GENMASK(7, 4) +#define MAX77650_CHG_DETAILS_BITS (_reg) \ + (((_reg) & MAX77650_CHG_DETAILS_MASK) >> 4) + +/* Charger is OFF. */ +#define MAX77650_CHG_OFF 0x00 +/* Charger is in prequalification mode. */ +#define MAX77650_CHG_PREQ 0x01 +/* Charger is in fast-charge constant current mode. */ +#define MAX77650_CHG_ON_CURR 0x02 +/* Charger is in JEITA modified fast-charge constant-current mode. */ +#define MAX77650_CHG_ON_CURR_JEITA 0x03 +/* Charger is in fast-charge constant-voltage mode. */ +#define MAX77650_CHG_ON_VOLT 0x04 +/* Charger is in JEITA modified fast-charge constant-voltage mode. */ +#define MAX77650_CHG_ON_VOLT_JEITA 0x05 +/* Charger is in top-off mode. */ +#define MAX77650_CHG_ON_TOPOFF 0x06 +/* Charger is in JEITA modified top-off mode. */ +#define MAX77650_CHG_ON_TOPOFF_JEITA 0x07 +/* Charger is done. */ +#define MAX77650_CHG_DONE 0x08 +/* Charger is JEITA modified done. */ +#define MAX77650_CHG_DONE_JEITA 0x09 +/* Charger is suspended due to a prequalification timer fault. */ +#define MAX77650_CHG_SUSP_PREQ_TIM_FAULT 0x0a +/* Charger is suspended due to a fast-charge timer fault. */ +#define MAX77650_CHG_SUSP_FAST_CHG_TIM_FAULT 0x0b +/* Charger is suspended due to a battery temperature fault. */ +#define MAX77650_CHG_SUSP_BATT_TEMP_FAULT 0x0c + +#define MAX77650_CHGIN_DETAILS_MASK GENMASK(3, 2) +#define MAX77650_CHGIN_DETAILS_BITS (_reg) \ + (((_reg) & MAX77650_CHGIN_DETAILS_MASK) >> 2) + +#define MAX77650_CHGIN_UNDERVOLTAGE_LOCKOUT 0x00 +#define MAX77650_CHGIN_OVERVOLTAGE_LOCKOUT 0x01 +#define MAX77650_CHGIN_OKAY 0x11 + +#define MAX77650_CHARGER_CHG_MASK BIT(1) +#define MAX77650_CHARGER_CHG_CHARGING (_reg) \ + (((_reg) & MAX77650_CHARGER_CHG_MASK) > 1) + +#define MAX77650_CHARGER_VCHGIN_MIN_MASK 0xc0 +#define MAX77650_CHARGER_VCHGIN_MIN_SHIFT (_val) ((_val) << 5) + +#define MAX77650_CHARGER_ICHGIN_LIM_MASK 0x1c +#define MAX77650_CHARGER_ICHGIN_LIM_SHIFT (_val) ((_val) << 2) + +struct max77650_charger_data { +struct regmap *map; +struct device *dev; +}; + +static enum power_supply_property max77650_charger_properties[] = { +POWER_SUPPLY_PROP_STATUS , +POWER_SUPPLY_PROP_ONLINE , +POWER_SUPPLY_PROP_CHARGE_TYPE +}; + +static const unsigned int max77650_charger_vchgin_min_table[] = { +4000000 ,4100000 ,4200000 ,4300000 ,4400000 ,4500000 ,4600000 ,4700000 +}; + +static const unsigned int max77650_charger_ichgin_lim_table[] = { +95000 ,190000 ,285000 ,380000 ,475000 +}; + +static int max77650_charger_set_vchgin_min (struct max77650_charger_data *chg, +unsigned int val) +{ +int i, rv; + +for (i =0 ; i <ARRAY_SIZE (max77650_charger_vchgin_min_table); i++) { +if (val == max77650_charger_vchgin_min_table[i]) { + rv =regmap_update_bits (chg->map, +MAX77650_REG_CNFG_CHG_B , +MAX77650_CHARGER_VCHGIN_MIN_MASK , +MAX77650_CHARGER_VCHGIN_MIN_SHIFT (i)); +if (rv) +return rv; + +return 0 ; + } + } + +return -EINVAL ; +} + +static int max77650_charger_set_ichgin_lim (struct max77650_charger_data *chg, +unsigned int val) +{ +int i, rv; + +for (i =0 ; i <ARRAY_SIZE (max77650_charger_ichgin_lim_table); i++) { +if (val == max77650_charger_ichgin_lim_table[i]) { + rv =regmap_update_bits (chg->map, +MAX77650_REG_CNFG_CHG_B , +MAX77650_CHARGER_ICHGIN_LIM_MASK , +MAX77650_CHARGER_ICHGIN_LIM_SHIFT (i)); +if (rv) +return rv; + +return 0 ; + } + } + +return -EINVAL ; +} + +static int max77650_charger_enable (struct max77650_charger_data *chg) +{ +int rv; + + rv =regmap_update_bits (chg->map, +MAX77650_REG_CNFG_CHG_B , +MAX77650_CHARGER_CHG_EN_MASK , +MAX77650_CHARGER_ENABLED ); +if (rv) +dev_err (chg->dev,"unable to enable the charger: %d\n" , rv); + +return rv; +} + +static int max77650_charger_disable (struct max77650_charger_data *chg) +{ +int rv; + + rv =regmap_update_bits (chg->map, +MAX77650_REG_CNFG_CHG_B , +MAX77650_CHARGER_CHG_EN_MASK , +MAX77650_CHARGER_DISABLED ); +if (rv) +dev_err (chg->dev,"unable to disable the charger: %d\n" , rv); + +return rv; +} + +static irqreturn_t max77650_charger_check_status (int irq,void *data) +{ +struct max77650_charger_data *chg = data; +int rv, reg; + + rv =regmap_read (chg->map,MAX77650_REG_STAT_CHG_B , ®); +if (rv) { +dev_err (chg->dev, +"unable to read the charger status: %d\n" , rv); +return IRQ_HANDLED ; + } + +switch (MAX77650_CHGIN_DETAILS_BITS (reg)) { +case MAX77650_CHGIN_UNDERVOLTAGE_LOCKOUT : +dev_err (chg->dev,"undervoltage lockout detected, disabling charger\n" ); +max77650_charger_disable (chg); +break ; +case MAX77650_CHGIN_OVERVOLTAGE_LOCKOUT : +dev_err (chg->dev,"overvoltage lockout detected, disabling charger\n" ); +max77650_charger_disable (chg); +break ; +case MAX77650_CHGIN_OKAY : +max77650_charger_enable (chg); +break ; +default : +/* May be 0x10 - debouncing */ +break ; + } + +return IRQ_HANDLED ; +} + +static int max77650_charger_get_property (struct power_supply *psy, +enum power_supply_property psp, +union power_supply_propval *val) +{ +struct max77650_charger_data *chg =power_supply_get_drvdata (psy); +int rv, reg; + +switch (psp) { +case POWER_SUPPLY_PROP_STATUS : + rv =regmap_read (chg->map,MAX77650_REG_STAT_CHG_B , ®); +if (rv) +return rv; + +if (MAX77650_CHARGER_CHG_CHARGING (reg)) { + val->intval =POWER_SUPPLY_STATUS_CHARGING ; +break ; + } + +switch (MAX77650_CHG_DETAILS_BITS (reg)) { +case MAX77650_CHG_OFF : +case MAX77650_CHG_SUSP_PREQ_TIM_FAULT : +case MAX77650_CHG_SUSP_FAST_CHG_TIM_FAULT : +case MAX77650_CHG_SUSP_BATT_TEMP_FAULT : + val->intval =POWER_SUPPLY_STATUS_NOT_CHARGING ; +break ; +case MAX77650_CHG_PREQ : +case MAX77650_CHG_ON_CURR : +case MAX77650_CHG_ON_CURR_JEITA : +case MAX77650_CHG_ON_VOLT : +case MAX77650_CHG_ON_VOLT_JEITA : +case MAX77650_CHG_ON_TOPOFF : +case MAX77650_CHG_ON_TOPOFF_JEITA : + val->intval =POWER_SUPPLY_STATUS_CHARGING ; +break ; +case MAX77650_CHG_DONE : + val->intval =POWER_SUPPLY_STATUS_FULL ; +break ; +default : + val->intval =POWER_SUPPLY_STATUS_UNKNOWN ; + } +break ; +case POWER_SUPPLY_PROP_ONLINE : + rv =regmap_read (chg->map,MAX77650_REG_STAT_CHG_B , ®); +if (rv) +return rv; + + val->intval =MAX77650_CHARGER_CHG_CHARGING (reg); +break ; +case POWER_SUPPLY_PROP_CHARGE_TYPE : + rv =regmap_read (chg->map,MAX77650_REG_STAT_CHG_B , ®); +if (rv) +return rv; + +if (!MAX77650_CHARGER_CHG_CHARGING (reg)) { + val->intval =POWER_SUPPLY_CHARGE_TYPE_NONE ; +break ; + } + +switch (MAX77650_CHG_DETAILS_BITS (reg)) { +case MAX77650_CHG_PREQ : +case MAX77650_CHG_ON_CURR : +case MAX77650_CHG_ON_CURR_JEITA : +case MAX77650_CHG_ON_VOLT : +case MAX77650_CHG_ON_VOLT_JEITA : + val->intval =POWER_SUPPLY_CHARGE_TYPE_FAST ; +break ; +case MAX77650_CHG_ON_TOPOFF : +case MAX77650_CHG_ON_TOPOFF_JEITA : + val->intval =POWER_SUPPLY_CHARGE_TYPE_TRICKLE ; +break ; +default : + val->intval =POWER_SUPPLY_CHARGE_TYPE_UNKNOWN ; + } +break ; +default : +return -EINVAL ; + } + +return 0 ; +} + +static const struct power_supply_desc max77650_battery_desc = { + .name ="max77650" , + .type =POWER_SUPPLY_TYPE_USB , + .get_property = max77650_charger_get_property, + .properties = max77650_charger_properties, + .num_properties =ARRAY_SIZE (max77650_charger_properties), +}; + +static int max77650_charger_probe (struct platform_device *pdev) +{ +struct power_supply_config pscfg = {}; +struct max77650_charger_data *chg; +struct power_supply *battery; +struct device *dev, *parent; +int rv, chg_irq, chgin_irq; +unsigned int prop; + + dev = &pdev->dev; + parent = dev->parent; + + chg =devm_kzalloc (dev,sizeof (*chg),GFP_KERNEL ); +if (!chg) +return -ENOMEM ; + +platform_set_drvdata (pdev, chg); + + chg->map =dev_get_regmap (parent,NULL ); +if (!chg->map) +return -ENODEV ; + + chg->dev = dev; + + pscfg.of_node = dev->of_node; + pscfg.drv_data = chg; + + chg_irq =platform_get_irq_byname (pdev,"CHG" ); +if (chg_irq <0 ) +return chg_irq; + + chgin_irq =platform_get_irq_byname (pdev,"CHGIN" ); +if (chgin_irq <0 ) +return chgin_irq; + + rv =devm_request_any_context_irq (dev, chg_irq, + max77650_charger_check_status, +IRQF_ONESHOT ,"chg" , chg); +if (rv <0 ) +return rv; + + rv =devm_request_any_context_irq (dev, chgin_irq, + max77650_charger_check_status, +IRQF_ONESHOT ,"chgin" , chg); +if (rv <0 ) +return rv; + + battery =devm_power_supply_register (dev, + &max77650_battery_desc, &pscfg); +if (IS_ERR (battery)) +return PTR_ERR (battery); + + rv =of_property_read_u32 (dev->of_node, +"input-voltage-min-microvolt" , &prop); +if (rv ==0 ) { + rv =max77650_charger_set_vchgin_min (chg, prop); +if (rv) +return rv; + } + + rv =of_property_read_u32 (dev->of_node, +"input-current-limit-microamp" , &prop); +if (rv ==0 ) { + rv =max77650_charger_set_ichgin_lim (chg, prop); +if (rv) +return rv; + } + +return max77650_charger_enable (chg); +} + +static int max77650_charger_remove (struct platform_device *pdev) +{ +struct max77650_charger_data *chg =platform_get_drvdata (pdev); + +return max77650_charger_disable (chg); +} + +static struct platform_driver max77650_charger_driver = { + .driver = { + .name ="max77650-charger" , + }, + .probe = max77650_charger_probe, + .remove = max77650_charger_remove, +}; +module_platform_driver (max77650_charger_driver); + +MODULE_DESCRIPTION ("MAXIM 77650/77651 charger driver" ); +MODULE_AUTHOR ("Bartosz Golaszewski <[email protected]>" ); +MODULE_LICENSE ("GPL v2" );Signature · 1 line
2.21.0
PATCH v9 8/11 gpio: max77650: add GPIO support
In reply to Bartosz GolaszewskiFrom: Bartosz Golaszewski <[email protected]>
Add GPIO support for max77650 mfd device. This PMIC exposes a single GPIO line.
--- drivers/gpio/Kconfig | 7 ++ drivers/gpio/Makefile | 1 + drivers/gpio/gpio-max77650.c | 190 +++++++++++++++++++++++++++++++++++ 3 files changed, 198 insertions(+) create mode 100644 drivers/gpio/gpio-max77650.c
drivers/gpio/Kconfig +7 -0
@@ -1112,6 +1112,13 @@ config GPIO_MAX77620 driver also provides interrupt support for each of the gpios. Say yes here to enable the max77620 to be used as gpio controller. +config GPIO_MAX77650 + tristate "Maxim MAX77650/77651 GPIO support" + depends on MFD_MAX77650 + help + GPIO driver for MAX77650/77651 PMIC from Maxim Semiconductor. + These chips have a single pin that can be configured as GPIO. + config GPIO_MSIC bool "Intel MSIC mixed signal gpio support" depends on (X86 || COMPILE_TEST) && MFD_INTEL_MSIC
drivers/gpio/Makefile +1 -0
@@ -80,6 +80,7 @@ obj-$(CONFIG_GPIO_MAX7300) += gpio-max7300.o obj-$(CONFIG_GPIO_MAX7301) += gpio-max7301.o obj-$(CONFIG_GPIO_MAX732X) += gpio-max732x.o obj-$(CONFIG_GPIO_MAX77620) += gpio-max77620.o +obj-$(CONFIG_GPIO_MAX77650) += gpio-max77650.o obj-$(CONFIG_GPIO_MB86S7X) += gpio-mb86s7x.o obj-$(CONFIG_GPIO_MENZ127) += gpio-menz127.o obj-$(CONFIG_GPIO_MERRIFIELD) += gpio-merrifield.o
drivers/gpio/gpio-max77650.c new file +190 -0
190 lines not on this page · raw message
Signature · 1 line
2.21.0
PATCH v9 9/11 leds: max77650: add LEDs support
In reply to Bartosz GolaszewskiFrom: Bartosz Golaszewski <[email protected]>
This adds basic support for LEDs for the max77650 PMIC. The device has three current sinks for driving LEDs.
--- drivers/leds/Kconfig | 6 ++ drivers/leds/Makefile | 1 + drivers/leds/leds-max77650.c | 147 +++++++++++++++++++++++++++++++++++ 3 files changed, 154 insertions(+) create mode 100644 drivers/leds/leds-max77650.c
drivers/leds/Kconfig +6 -0
@@ -608,6 +608,12 @@ config LEDS_TLC591XX This option enables support for Texas Instruments TLC59108 and TLC59116 LED controllers. +config LEDS_MAX77650 + tristate "LED support for Maxim MAX77650 PMIC" + depends on LEDS_CLASS && MFD_MAX77650 + help + LEDs driver for MAX77650 family of PMICs from Maxim Integrated. + config LEDS_MAX77693 tristate "LED support for MAX77693 Flash" depends on LEDS_CLASS_FLASH
drivers/leds/Makefile +1 -0
@@ -61,6 +61,7 @@ obj-$(CONFIG_LEDS_MC13783) += leds-mc13783.o obj-$(CONFIG_LEDS_NS2) += leds-ns2.o obj-$(CONFIG_LEDS_NETXBIG) += leds-netxbig.o obj-$(CONFIG_LEDS_ASIC3) += leds-asic3.o +obj-$(CONFIG_LEDS_MAX77650) += leds-max77650.o obj-$(CONFIG_LEDS_MAX77693) += leds-max77693.o obj-$(CONFIG_LEDS_MAX8997) += leds-max8997.o obj-$(CONFIG_LEDS_LM355x) += leds-lm355x.o
drivers/leds/leds-max77650.c new file +147 -0
147 lines not on this page · raw message
Signature · 1 line
2.21.0
PATCH v9 10/11 input: max77650: add onkey support
In reply to Bartosz GolaszewskiFrom: Bartosz Golaszewski <[email protected]>
Add support for the push- and slide-button events for max77650.
--- drivers/input/misc/Kconfig | 9 +++ drivers/input/misc/Makefile | 1 + drivers/input/misc/max77650-onkey.c | 121 ++++++++++++++++++++++++++++ 3 files changed, 131 insertions(+) create mode 100644 drivers/input/misc/max77650-onkey.c
drivers/input/misc/Kconfig +9 -0
@@ -190,6 +190,15 @@ config INPUT_M68K_BEEP tristate "M68k Beeper support" depends on M68K +config INPUT_MAX77650_ONKEY + tristate "Maxim MAX77650 ONKEY support" + depends on MFD_MAX77650 + help + Support the ONKEY of the MAX77650 PMIC as an input device. + + To compile this driver as a module, choose M here: the module + will be called max77650-onkey. + config INPUT_MAX77693_HAPTIC tristate "MAXIM MAX77693/MAX77843 haptic controller support" depends on (MFD_MAX77693 || MFD_MAX77843) && PWM
drivers/input/misc/Makefile +1 -0
@@ -43,6 +43,7 @@ obj-$(CONFIG_INPUT_IXP4XX_BEEPER) += ixp4xx-beeper.o obj-$(CONFIG_INPUT_KEYSPAN_REMOTE) += keyspan_remote.o obj-$(CONFIG_INPUT_KXTJ9) += kxtj9.o obj-$(CONFIG_INPUT_M68K_BEEP) += m68kspkr.o +obj-$(CONFIG_INPUT_MAX77650_ONKEY) += max77650-onkey.o obj-$(CONFIG_INPUT_MAX77693_HAPTIC) += max77693-haptic.o obj-$(CONFIG_INPUT_MAX8925_ONKEY) += max8925_onkey.o obj-$(CONFIG_INPUT_MAX8997_HAPTIC) += max8997_haptic.o
drivers/input/misc/max77650-onkey.c new file +121 -0
121 lines not on this page · raw message
Signature · 1 line
2.21.0
PATCH v9 11/11 MAINTAINERS: add an entry for max77650 mfd driver
In reply to Bartosz GolaszewskiFrom: Bartosz Golaszewski <[email protected]>
I plan on extending this set of drivers so add myself as maintainer.
--- MAINTAINERS | 14 ++++++++++++++ 1 file changed, 14 insertions(+)
MAINTAINERS +14 -0
@@ -9407,6 +9407,20 @@ S: Maintained F: Documentation/devicetree/bindings/sound/max9860.txt F: sound/soc/codecs/max9860.* +MAXIM MAX77650 PMIC MFD DRIVER +M: Bartosz Golaszewski <[email protected]> +L: [email protected] +S: Maintained +F: Documentation/devicetree/bindings/*/*max77650.txt +F: Documentation/devicetree/bindings/*/max77650*.txt +F: include/linux/mfd/max77650.h +F: drivers/mfd/max77650.c +F: drivers/regulator/max77650-regulator.c +F: drivers/power/supply/max77650-charger.c +F: drivers/input/misc/max77650-onkey.c +F: drivers/leds/leds-max77650.c +F: drivers/gpio/gpio-max77650.c + MAXIM MAX77802 PMIC REGULATOR DEVICE DRIVER M: Javier Martinez Canillas <[email protected]> L: [email protected]
Signature · 1 line
2.21.0