Add support for different configurations of charger's registers so the
same driver could be used on other devices (e.g. MAX77843).
Signed-off-by: Krzysztof Kozlowski
Acked-by: Mark Brown
---
drivers/regulator/max77693.c | 39 +++
1 file changed, 27 insertions
This prepares for merging some of the drivers between max77693 and
max77843 so the child MFD driver can be attached to any parent MFD main
driver.
Move the state container to common header file. Additionally add
consistent 'i2c' prefixes to its members (of 'struct i2c_client' type).
Signed-off-by
Clean up the max77693 private header file by removing:
1. Left-overs from previous way of interrupt handling (driver uses
regmap_irq_chip).
2. Unused members of struct 'max77693_dev' related to interrupts in
extcon driver.
Signed-off-by: Krzysztof Kozlowski
[for extcon]
Acked-by: Chanwoo Ch
Store the device type (obtained from i2c_device_id) as an enum and add a
default type of unknown to distinguish from case when this is not set
at all.
Signed-off-by: Krzysztof Kozlowski
---
include/linux/mfd/max77693-private.h | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
di
Add MAX77693 prefix to some of the defines used in max77693 extcon
driver so the max77693-private.h can be included simultaneously with
max77843-private.h.
Additionally use BIT() macro in header.
Signed-off-by: Krzysztof Kozlowski
---
drivers/extcon/extcon-max77693.c | 72 +
Switch to the same definition of state container as in MAX77693 drivers.
This will allow usage of one regulator driver in both devices: MAX77693
and MAX77843.
Signed-off-by: Krzysztof Kozlowski
---
drivers/extcon/extcon-max77843.c | 17 +
drivers/input/misc/max77843-haptic.c
Add MAX77843_MUIC prefix to some of the defines used in max77843 extcon
driver so the max77693-private.h can be included simultaneously with
max77843-private.h.
Signed-off-by: Krzysztof Kozlowski
Acked-by: Lee Jones
---
drivers/extcon/extcon-max77843.c | 49 +++
include/linux/mfd/m
The max77693 regulator driver supports Maxim 77843 device so remove the
max77843 driver.
Signed-off-by: Krzysztof Kozlowski
---
drivers/regulator/Kconfig| 8 --
drivers/regulator/Makefile | 1 -
drivers/regulator/max77843.c | 203 ---
3 files cha
The charger and safeout part of MAX77843 is almost the same as MAX77693.
>From regulator point of view the only differences are the constraints
and register values related to these constraints. Now the max77693
regulator driver can be used for MAX77843.
Signed-off-by: Krzysztof Kozlowski
Acked-by
Hi,
The patchset merges max77843 regulator driver into max77693.
I am asking for review and acks from multiple subsystems: extcon,
input, mfd, power and regulator.
Changes since v1
1. Drop patch "regulator: max77693: Use core code for charger's
is_enabled" because Mark Brown
On Saturday, May 23, 2015 at 06:41:50 PM, Dmitry Torokhov wrote:
> On May 23, 2015 9:38:54 AM PDT, Marek Vasut wrote:
> >On Saturday, May 23, 2015 at 12:58:32 AM, Dmitry Torokhov wrote:
> >> The STMPE MFD is only used with device tree configured systems (and
> >
> >STMPE
> >
> >> MFD core depends
On May 23, 2015 9:38:54 AM PDT, Marek Vasut wrote:
>On Saturday, May 23, 2015 at 12:58:32 AM, Dmitry Torokhov wrote:
>> The STMPE MFD is only used with device tree configured systems (and
>STMPE
>> MFD core depends on OF), so force the configuration to come from
>device
>> tree only.
>>
>> Signed
On Saturday, May 23, 2015 at 12:58:32 AM, Dmitry Torokhov wrote:
> The STMPE MFD is only used with device tree configured systems (and STMPE
> MFD core depends on OF), so force the configuration to come from device
> tree only.
>
> Signed-off-by: Dmitry Torokhov
> ---
Hi!
[...]
> @@ -351,14 +3
Hi,
On Wed, Apr 29, 2015 at 07:58:30PM +0900, Krzysztof Kozlowski wrote:
> This prepares for merging some of the drivers between max77693 and
> max77843 so the child MFD driver can be attached to any parent MFD main
> driver.
>
> Move the state container to common header file. Additionally add
>
Am 23.05.2015 um 00:58 schrieb Dmitry Torokhov:
> The STMPE MFD is only used with device tree configured systems (and STMPE
> MFD core depends on OF), so force the configuration to come from device
> tree only.
>
> Signed-off-by: Dmitry Torokhov
> ---
>
> Not tested as no device, please give it
Hi Dmitry,
On Sat, May 23, 2015 at 1:32 AM, Dmitry Torokhov
wrote:
> On Thu, May 21, 2015 at 01:42:24PM +0200, Geert Uytterhoeven wrote:
>> This is a resent of a series by Laurent Pinchart to fix OF matching for
>> the adxl34x driver.
> Applied and sorry for the delay.
Thanks a lot!
Gr{oetje,e
16 matches
Mail list logo