linux-next: manual merge of the battery tree with the mfd tree

linux-next: manual merge of the battery tree with the mfd tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1616 bytes --]

Hi Anton,

Today's linux-next merge of the battery tree got a conflict in
include/linux/mfd/88pm860x.h between commit a70abacb06b8 ("mfd: 88pm860x:
Use REG resource in regulator") from the mfd tree and commit a830d28b48bf
("power_supply: Enable battery-charger for 88pm860x") from the battery
tree.

I fixed it up (see below) and can carry the fix as necessary (no action
is required).

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

diff --cc include/linux/mfd/88pm860x.h
index d515e5c,b7c5a3c..0000000
--- a/include/linux/mfd/88pm860x.h
+++ b/include/linux/mfd/88pm860x.h
@@@ -359,22 -460,8 +440,23 @@@ struct pm860x_platform_data 
  	struct pm860x_rtc_pdata		*rtc;
  	struct pm860x_touch_pdata	*touch;
  	struct pm860x_power_pdata	*power;
+ 	struct charger_desc		*chg_desc;
 -	struct regulator_init_data	*regulator;
 +	struct regulator_init_data	*buck1;
 +	struct regulator_init_data	*buck2;
 +	struct regulator_init_data	*buck3;
 +	struct regulator_init_data	*ldo1;
 +	struct regulator_init_data	*ldo2;
 +	struct regulator_init_data	*ldo3;
 +	struct regulator_init_data	*ldo4;
 +	struct regulator_init_data	*ldo5;
 +	struct regulator_init_data	*ldo6;
 +	struct regulator_init_data	*ldo7;
 +	struct regulator_init_data	*ldo8;
 +	struct regulator_init_data	*ldo9;
 +	struct regulator_init_data	*ldo10;
 +	struct regulator_init_data	*ldo12;
 +	struct regulator_init_data	*ldo_vibrator;
 +	struct regulator_init_data	*ldo14;
  
  	unsigned short	companion_addr;	/* I2C address of companion chip */
  	int		i2c_port;	/* Controlled by GI2C or PI2C */

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

linux-next: manual merge of the battery tree with the mfd tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]

Hi all,

Today's linux-next merge of the battery tree got a conflict in:

  drivers/power/supply/rt5033_charger.c

between commit:

  12cc585f36b8 ("power: supply: rt5033_charger: Add cable detection and USB OTG supply")

from the mfd tree and commit:

  2ce8284c3115 ("power: Explicitly include correct DT includes")

from the battery tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc drivers/power/supply/rt5033_charger.c
index e0303ca5a8db,c0c516f22c66..000000000000
--- a/drivers/power/supply/rt5033_charger.c
+++ b/drivers/power/supply/rt5033_charger.c
@@@ -6,11 -6,8 +6,11 @@@
   * Author: Beomho Seo <beomho.seo@samsung.com>
   */
  
+ #include <linux/mod_devicetable.h>
 +#include <linux/devm-helpers.h>
 +#include <linux/extcon.h>
  #include <linux/module.h>
 +#include <linux/mutex.h>
- #include <linux/of_device.h>
  #include <linux/platform_device.h>
  #include <linux/power_supply.h>
  #include <linux/regmap.h>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: manual merge of the battery tree with the mfd tree

[Sebastian Reichel]

[-- Attachment #1: Type: text/plain, Size: 2626 bytes --]

Hi Stephen,

On Fri, Jun 28, 2019 at 01:45:45PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next merge of the battery tree got conflicts in:
> 
>   drivers/power/supply/Kconfig
>   drivers/power/supply/Makefile
> 
> between commit:
> 
>   f8c7f7ddd8ef ("power: supply: Initial support for ROHM BD70528 PMIC charger block")
> 
> from the mfd tree and commit:
> 
>   0736343e4c56 ("power_supply: wilco_ec: Add charging config driver")
> 
> from the battery tree.
> 
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging.  You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.

This one should no longer appear on next tree update, since I
dropped 0736343e4c56.

-- Sebastian

> 
> -- 
> Cheers,
> Stephen Rothwell
> 
> diff --cc drivers/power/supply/Kconfig
> index 4a3cd679295b,4c01598f5ccb..000000000000
> --- a/drivers/power/supply/Kconfig
> +++ b/drivers/power/supply/Kconfig
> @@@ -689,13 -702,13 +703,22 @@@ config CHARGER_UCS100
>   	  Say Y to enable support for Microchip UCS1002 Programmable
>   	  USB Port Power Controller with Charger Emulation.
>   
>  +config CHARGER_BD70528
>  +	tristate "ROHM bd70528 charger driver"
>  +	depends on MFD_ROHM_BD70528
>  +	default n
>  +	help
>  +	 Say Y here to enable support for getting battery status
>  +	 information and altering charger configurations from charger
>  +	 block of the ROHM BD70528 Power Management IC.
>  +
> + config CHARGER_WILCO
> + 	tristate "Wilco EC based charger for ChromeOS"
> + 	depends on WILCO_EC
> + 	help
> + 	  Say Y here to enable control of the charging routines performed
> + 	  by the Embedded Controller on the Chromebook named Wilco. Further
> + 	  information can be found in
> + 	  Documentation/ABI/testing/sysfs-class-power-wilco
> + 
>   endif # POWER_SUPPLY
> diff --cc drivers/power/supply/Makefile
> index 346a8ef5f348,d2263e1e2b6f..000000000000
> --- a/drivers/power/supply/Makefile
> +++ b/drivers/power/supply/Makefile
> @@@ -90,4 -91,4 +91,5 @@@ obj-$(CONFIG_CHARGER_CROS_USBPD)	+= cro
>   obj-$(CONFIG_CHARGER_SC2731)	+= sc2731_charger.o
>   obj-$(CONFIG_FUEL_GAUGE_SC27XX)	+= sc27xx_fuel_gauge.o
>   obj-$(CONFIG_CHARGER_UCS1002)	+= ucs1002_power.o
>  +obj-$(CONFIG_CHARGER_BD70528)	+= bd70528-charger.o
> + obj-$(CONFIG_CHARGER_WILCO)	+= wilco-charger.o



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

linux-next: manual merge of the battery tree with the mfd tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 2304 bytes --]

Hi all,

Today's linux-next merge of the battery tree got conflicts in:

  drivers/power/supply/Kconfig
  drivers/power/supply/Makefile

between commit:

  f8c7f7ddd8ef ("power: supply: Initial support for ROHM BD70528 PMIC charger block")

from the mfd tree and commit:

  0736343e4c56 ("power_supply: wilco_ec: Add charging config driver")

from the battery tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc drivers/power/supply/Kconfig
index 4a3cd679295b,4c01598f5ccb..000000000000
--- a/drivers/power/supply/Kconfig
+++ b/drivers/power/supply/Kconfig
@@@ -689,13 -702,13 +703,22 @@@ config CHARGER_UCS100
  	  Say Y to enable support for Microchip UCS1002 Programmable
  	  USB Port Power Controller with Charger Emulation.
  
 +config CHARGER_BD70528
 +	tristate "ROHM bd70528 charger driver"
 +	depends on MFD_ROHM_BD70528
 +	default n
 +	help
 +	 Say Y here to enable support for getting battery status
 +	 information and altering charger configurations from charger
 +	 block of the ROHM BD70528 Power Management IC.
 +
+ config CHARGER_WILCO
+ 	tristate "Wilco EC based charger for ChromeOS"
+ 	depends on WILCO_EC
+ 	help
+ 	  Say Y here to enable control of the charging routines performed
+ 	  by the Embedded Controller on the Chromebook named Wilco. Further
+ 	  information can be found in
+ 	  Documentation/ABI/testing/sysfs-class-power-wilco
+ 
  endif # POWER_SUPPLY
diff --cc drivers/power/supply/Makefile
index 346a8ef5f348,d2263e1e2b6f..000000000000
--- a/drivers/power/supply/Makefile
+++ b/drivers/power/supply/Makefile
@@@ -90,4 -91,4 +91,5 @@@ obj-$(CONFIG_CHARGER_CROS_USBPD)	+= cro
  obj-$(CONFIG_CHARGER_SC2731)	+= sc2731_charger.o
  obj-$(CONFIG_FUEL_GAUGE_SC27XX)	+= sc27xx_fuel_gauge.o
  obj-$(CONFIG_CHARGER_UCS1002)	+= ucs1002_power.o
 +obj-$(CONFIG_CHARGER_BD70528)	+= bd70528-charger.o
+ obj-$(CONFIG_CHARGER_WILCO)	+= wilco-charger.o

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

linux-next: manual merge of the battery tree with the mfd tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1656 bytes --]

Hi Anton,

Today's linux-next merge of the battery tree got a conflict in
include/linux/mfd/abx500/ab8500.h between commit 1d843a6c8c20 ("mfd:
ab8500-core: Allow the possibility to dump all AB8500 registers") from
the mfd tree and commit 0ed5107fa860 ("ab8500-charger: Do not touch
VBUSOVV bits") from the battery tree.

I fixed it up (see below) and can carry the fix as necessary (no action
is required).

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

diff --cc include/linux/mfd/abx500/ab8500.h
index fa7173d,b9a6a84..0000000
--- a/include/linux/mfd/abx500/ab8500.h
+++ b/include/linux/mfd/abx500/ab8500.h
@@@ -345,12 -346,23 +350,32 @@@ static inline int is_ab8500_2p0(struct 
  	return (is_ab8500(ab) && (ab->chip_id == AB8500_CUT2P0));
  }
  
+ static inline int is_ab8505_1p0_or_earlier(struct ab8500 *ab)
+ {
+ 	return (is_ab8505(ab) && (ab->chip_id <= AB8500_CUT1P0));
+ }
+ 
+ static inline int is_ab8505_2p0(struct ab8500 *ab)
+ {
+ 	return (is_ab8505(ab) && (ab->chip_id == AB8500_CUT2P0));
+ }
+ 
+ static inline int is_ab9540_1p0_or_earlier(struct ab8500 *ab)
+ {
+ 	return (is_ab9540(ab) && (ab->chip_id <= AB8500_CUT1P0));
+ }
+ 
+ static inline int is_ab9540_2p0(struct ab8500 *ab)
+ {
+ 	return (is_ab9540(ab) && (ab->chip_id == AB8500_CUT2P0));
+ }
++
 +#ifdef CONFIG_AB8500_DEBUG
 +void ab8500_dump_all_banks(struct device *dev);
 +void ab8500_debug_register_interrupt(int line);
 +#else
 +static inline void ab8500_dump_all_banks(struct device *dev) {}
 +static inline void ab8500_debug_register_interrupt(int line) {}
 +#endif
 +
  #endif /* MFD_AB8500_H */

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]