linux-next: manual merge of the pinctrl tree with the arm-soc tree

linux-next: manual merge of the pinctrl tree with the arm-soc tree

[Stephen Rothwell]

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

Hi all,

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

  drivers/pinctrl/Kconfig
  drivers/pinctrl/Makefile

between commit:

  ec648f6b7686 ("pinctrl: starfive: Add pinctrl driver for StarFive SoCs")

from the arm-soc tree and commits:

  12422af8194d ("pinctrl: Add Intel Thunder Bay pinctrl driver")
  b124c8bd50c7 ("pinctrl: Sort Kconfig and Makefile entries alphabetically")

from the pinctrl 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/pinctrl/Kconfig
index 0d5b61e4c21e,c27c9ee89f0e..000000000000
--- a/drivers/pinctrl/Kconfig
+++ b/drivers/pinctrl/Kconfig
diff --cc drivers/pinctrl/Makefile
index f5bdd6b209a6,6be6c3fc6663..000000000000
--- a/drivers/pinctrl/Makefile
+++ b/drivers/pinctrl/Makefile
@@@ -30,26 -39,16 +39,17 @@@ obj-$(CONFIG_PINCTRL_OXNAS)	+= pinctrl-
  obj-$(CONFIG_PINCTRL_PALMAS)	+= pinctrl-palmas.o
  obj-$(CONFIG_PINCTRL_PIC32)	+= pinctrl-pic32.o
  obj-$(CONFIG_PINCTRL_PISTACHIO)	+= pinctrl-pistachio.o
+ obj-$(CONFIG_PINCTRL_RK805)	+= pinctrl-rk805.o
  obj-$(CONFIG_PINCTRL_ROCKCHIP)	+= pinctrl-rockchip.o
  obj-$(CONFIG_PINCTRL_SINGLE)	+= pinctrl-single.o
- obj-$(CONFIG_PINCTRL_SX150X)	+= pinctrl-sx150x.o
- obj-$(CONFIG_ARCH_TEGRA)	+= tegra/
- obj-$(CONFIG_PINCTRL_XWAY)	+= pinctrl-xway.o
- obj-$(CONFIG_PINCTRL_LANTIQ)	+= pinctrl-lantiq.o
- obj-$(CONFIG_PINCTRL_LPC18XX)	+= pinctrl-lpc18xx.o
- obj-$(CONFIG_PINCTRL_TB10X)	+= pinctrl-tb10x.o
+ obj-$(CONFIG_PINCTRL_STMFX) 	+= pinctrl-stmfx.o
  obj-$(CONFIG_PINCTRL_ST) 	+= pinctrl-st.o
 +obj-$(CONFIG_PINCTRL_STARFIVE)	+= pinctrl-starfive.o
- obj-$(CONFIG_PINCTRL_STMFX) 	+= pinctrl-stmfx.o
- obj-$(CONFIG_PINCTRL_ZYNQ)	+= pinctrl-zynq.o
+ obj-$(CONFIG_PINCTRL_SX150X)	+= pinctrl-sx150x.o
+ obj-$(CONFIG_PINCTRL_TB10X)	+= pinctrl-tb10x.o
+ obj-$(CONFIG_PINCTRL_THUNDERBAY) += pinctrl-thunderbay.o
  obj-$(CONFIG_PINCTRL_ZYNQMP)	+= pinctrl-zynqmp.o
- obj-$(CONFIG_PINCTRL_INGENIC)	+= pinctrl-ingenic.o
- obj-$(CONFIG_PINCTRL_RK805)	+= pinctrl-rk805.o
- obj-$(CONFIG_PINCTRL_OCELOT)	+= pinctrl-ocelot.o
- obj-$(CONFIG_PINCTRL_MICROCHIP_SGPIO)	+= pinctrl-microchip-sgpio.o
- obj-$(CONFIG_PINCTRL_EQUILIBRIUM)   += pinctrl-equilibrium.o
- obj-$(CONFIG_PINCTRL_K210)	+= pinctrl-k210.o
- obj-$(CONFIG_PINCTRL_KEEMBAY)	+= pinctrl-keembay.o
+ obj-$(CONFIG_PINCTRL_ZYNQ)	+= pinctrl-zynq.o
  
  obj-y				+= actions/
  obj-$(CONFIG_ARCH_ASPEED)	+= aspeed/

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

linux-next: manual merge of the pinctrl tree with the arm-soc tree

[Stephen Rothwell]

[-- Attachment #1.1: Type: text/plain, Size: 2798 bytes --]

Hi all,

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

  drivers/pinctrl/Kconfig
  drivers/pinctrl/Makefile

between commit:

  ec648f6b7686 ("pinctrl: starfive: Add pinctrl driver for StarFive SoCs")

from the arm-soc tree and commits:

  12422af8194d ("pinctrl: Add Intel Thunder Bay pinctrl driver")
  b124c8bd50c7 ("pinctrl: Sort Kconfig and Makefile entries alphabetically")

from the pinctrl 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/pinctrl/Kconfig
index 0d5b61e4c21e,c27c9ee89f0e..000000000000
--- a/drivers/pinctrl/Kconfig
+++ b/drivers/pinctrl/Kconfig
diff --cc drivers/pinctrl/Makefile
index f5bdd6b209a6,6be6c3fc6663..000000000000
--- a/drivers/pinctrl/Makefile
+++ b/drivers/pinctrl/Makefile
@@@ -30,26 -39,16 +39,17 @@@ obj-$(CONFIG_PINCTRL_OXNAS)	+= pinctrl-
  obj-$(CONFIG_PINCTRL_PALMAS)	+= pinctrl-palmas.o
  obj-$(CONFIG_PINCTRL_PIC32)	+= pinctrl-pic32.o
  obj-$(CONFIG_PINCTRL_PISTACHIO)	+= pinctrl-pistachio.o
+ obj-$(CONFIG_PINCTRL_RK805)	+= pinctrl-rk805.o
  obj-$(CONFIG_PINCTRL_ROCKCHIP)	+= pinctrl-rockchip.o
  obj-$(CONFIG_PINCTRL_SINGLE)	+= pinctrl-single.o
- obj-$(CONFIG_PINCTRL_SX150X)	+= pinctrl-sx150x.o
- obj-$(CONFIG_ARCH_TEGRA)	+= tegra/
- obj-$(CONFIG_PINCTRL_XWAY)	+= pinctrl-xway.o
- obj-$(CONFIG_PINCTRL_LANTIQ)	+= pinctrl-lantiq.o
- obj-$(CONFIG_PINCTRL_LPC18XX)	+= pinctrl-lpc18xx.o
- obj-$(CONFIG_PINCTRL_TB10X)	+= pinctrl-tb10x.o
+ obj-$(CONFIG_PINCTRL_STMFX) 	+= pinctrl-stmfx.o
  obj-$(CONFIG_PINCTRL_ST) 	+= pinctrl-st.o
 +obj-$(CONFIG_PINCTRL_STARFIVE)	+= pinctrl-starfive.o
- obj-$(CONFIG_PINCTRL_STMFX) 	+= pinctrl-stmfx.o
- obj-$(CONFIG_PINCTRL_ZYNQ)	+= pinctrl-zynq.o
+ obj-$(CONFIG_PINCTRL_SX150X)	+= pinctrl-sx150x.o
+ obj-$(CONFIG_PINCTRL_TB10X)	+= pinctrl-tb10x.o
+ obj-$(CONFIG_PINCTRL_THUNDERBAY) += pinctrl-thunderbay.o
  obj-$(CONFIG_PINCTRL_ZYNQMP)	+= pinctrl-zynqmp.o
- obj-$(CONFIG_PINCTRL_INGENIC)	+= pinctrl-ingenic.o
- obj-$(CONFIG_PINCTRL_RK805)	+= pinctrl-rk805.o
- obj-$(CONFIG_PINCTRL_OCELOT)	+= pinctrl-ocelot.o
- obj-$(CONFIG_PINCTRL_MICROCHIP_SGPIO)	+= pinctrl-microchip-sgpio.o
- obj-$(CONFIG_PINCTRL_EQUILIBRIUM)   += pinctrl-equilibrium.o
- obj-$(CONFIG_PINCTRL_K210)	+= pinctrl-k210.o
- obj-$(CONFIG_PINCTRL_KEEMBAY)	+= pinctrl-keembay.o
+ obj-$(CONFIG_PINCTRL_ZYNQ)	+= pinctrl-zynq.o
  
  obj-y				+= actions/
  obj-$(CONFIG_ARCH_ASPEED)	+= aspeed/

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

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

Re: linux-next: manual merge of the pinctrl tree with the arm-soc tree

[Arnd Bergmann]

On Fri, Dec 17, 2021 at 7:29 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> Today's linux-next merge of the pinctrl tree got conflicts in:
>
>   drivers/pinctrl/Kconfig
>   drivers/pinctrl/Makefile
>
> between commit:
>
>   ec648f6b7686 ("pinctrl: starfive: Add pinctrl driver for StarFive SoCs")
>
> from the arm-soc tree and commits:
>
>   12422af8194d ("pinctrl: Add Intel Thunder Bay pinctrl driver")
>   b124c8bd50c7 ("pinctrl: Sort Kconfig and Makefile entries alphabetically")
>
> from the pinctrl 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.

Thanks, looks good. There are potentially three or four new SoC families
in the arm/newsoc branch (this is the first one I merged), so I expect to see
a few additional conflicts like this against pinctrl/clk/irqchip, but
they should
all be trivial.

        Arnd

Re: linux-next: manual merge of the pinctrl tree with the arm-soc tree

[Arnd Bergmann]

On Fri, Dec 17, 2021 at 7:29 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> Today's linux-next merge of the pinctrl tree got conflicts in:
>
>   drivers/pinctrl/Kconfig
>   drivers/pinctrl/Makefile
>
> between commit:
>
>   ec648f6b7686 ("pinctrl: starfive: Add pinctrl driver for StarFive SoCs")
>
> from the arm-soc tree and commits:
>
>   12422af8194d ("pinctrl: Add Intel Thunder Bay pinctrl driver")
>   b124c8bd50c7 ("pinctrl: Sort Kconfig and Makefile entries alphabetically")
>
> from the pinctrl 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.

Thanks, looks good. There are potentially three or four new SoC families
in the arm/newsoc branch (this is the first one I merged), so I expect to see
a few additional conflicts like this against pinctrl/clk/irqchip, but
they should
all be trivial.

        Arnd

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

Re: linux-next: manual merge of the pinctrl tree with the arm-soc tree

[Andy Shevchenko]

On Fri, Dec 17, 2021 at 12:29 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> Today's linux-next merge of the pinctrl tree got conflicts in:
>
>   drivers/pinctrl/Kconfig
>   drivers/pinctrl/Makefile
>
> between commit:
>
>   ec648f6b7686 ("pinctrl: starfive: Add pinctrl driver for StarFive SoCs")
>
> from the arm-soc tree and commits:
>
>   12422af8194d ("pinctrl: Add Intel Thunder Bay pinctrl driver")
>   b124c8bd50c7 ("pinctrl: Sort Kconfig and Makefile entries alphabetically")
>
> from the pinctrl 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.

Thanks!
To me it seems like a correct fix.

> diff --cc drivers/pinctrl/Kconfig
> index 0d5b61e4c21e,c27c9ee89f0e..000000000000
> --- a/drivers/pinctrl/Kconfig
> +++ b/drivers/pinctrl/Kconfig
> diff --cc drivers/pinctrl/Makefile
> index f5bdd6b209a6,6be6c3fc6663..000000000000
> --- a/drivers/pinctrl/Makefile
> +++ b/drivers/pinctrl/Makefile
> @@@ -30,26 -39,16 +39,17 @@@ obj-$(CONFIG_PINCTRL_OXNAS)        += pinctrl-
>   obj-$(CONFIG_PINCTRL_PALMAS)  += pinctrl-palmas.o
>   obj-$(CONFIG_PINCTRL_PIC32)   += pinctrl-pic32.o
>   obj-$(CONFIG_PINCTRL_PISTACHIO)       += pinctrl-pistachio.o
> + obj-$(CONFIG_PINCTRL_RK805)   += pinctrl-rk805.o
>   obj-$(CONFIG_PINCTRL_ROCKCHIP)        += pinctrl-rockchip.o
>   obj-$(CONFIG_PINCTRL_SINGLE)  += pinctrl-single.o
> - obj-$(CONFIG_PINCTRL_SX150X)  += pinctrl-sx150x.o
> - obj-$(CONFIG_ARCH_TEGRA)      += tegra/
> - obj-$(CONFIG_PINCTRL_XWAY)    += pinctrl-xway.o
> - obj-$(CONFIG_PINCTRL_LANTIQ)  += pinctrl-lantiq.o
> - obj-$(CONFIG_PINCTRL_LPC18XX) += pinctrl-lpc18xx.o
> - obj-$(CONFIG_PINCTRL_TB10X)   += pinctrl-tb10x.o
> + obj-$(CONFIG_PINCTRL_STMFX)   += pinctrl-stmfx.o
>   obj-$(CONFIG_PINCTRL_ST)      += pinctrl-st.o
>  +obj-$(CONFIG_PINCTRL_STARFIVE)        += pinctrl-starfive.o
> - obj-$(CONFIG_PINCTRL_STMFX)   += pinctrl-stmfx.o
> - obj-$(CONFIG_PINCTRL_ZYNQ)    += pinctrl-zynq.o
> + obj-$(CONFIG_PINCTRL_SX150X)  += pinctrl-sx150x.o
> + obj-$(CONFIG_PINCTRL_TB10X)   += pinctrl-tb10x.o
> + obj-$(CONFIG_PINCTRL_THUNDERBAY) += pinctrl-thunderbay.o
>   obj-$(CONFIG_PINCTRL_ZYNQMP)  += pinctrl-zynqmp.o
> - obj-$(CONFIG_PINCTRL_INGENIC) += pinctrl-ingenic.o
> - obj-$(CONFIG_PINCTRL_RK805)   += pinctrl-rk805.o
> - obj-$(CONFIG_PINCTRL_OCELOT)  += pinctrl-ocelot.o
> - obj-$(CONFIG_PINCTRL_MICROCHIP_SGPIO) += pinctrl-microchip-sgpio.o
> - obj-$(CONFIG_PINCTRL_EQUILIBRIUM)   += pinctrl-equilibrium.o
> - obj-$(CONFIG_PINCTRL_K210)    += pinctrl-k210.o
> - obj-$(CONFIG_PINCTRL_KEEMBAY) += pinctrl-keembay.o
> + obj-$(CONFIG_PINCTRL_ZYNQ)    += pinctrl-zynq.o
>
>   obj-y                         += actions/
>   obj-$(CONFIG_ARCH_ASPEED)     += aspeed/



-- 
With Best Regards,
Andy Shevchenko

Re: linux-next: manual merge of the pinctrl tree with the arm-soc tree

[Andy Shevchenko]

On Fri, Dec 17, 2021 at 12:29 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> Today's linux-next merge of the pinctrl tree got conflicts in:
>
>   drivers/pinctrl/Kconfig
>   drivers/pinctrl/Makefile
>
> between commit:
>
>   ec648f6b7686 ("pinctrl: starfive: Add pinctrl driver for StarFive SoCs")
>
> from the arm-soc tree and commits:
>
>   12422af8194d ("pinctrl: Add Intel Thunder Bay pinctrl driver")
>   b124c8bd50c7 ("pinctrl: Sort Kconfig and Makefile entries alphabetically")
>
> from the pinctrl 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.

Thanks!
To me it seems like a correct fix.

> diff --cc drivers/pinctrl/Kconfig
> index 0d5b61e4c21e,c27c9ee89f0e..000000000000
> --- a/drivers/pinctrl/Kconfig
> +++ b/drivers/pinctrl/Kconfig
> diff --cc drivers/pinctrl/Makefile
> index f5bdd6b209a6,6be6c3fc6663..000000000000
> --- a/drivers/pinctrl/Makefile
> +++ b/drivers/pinctrl/Makefile
> @@@ -30,26 -39,16 +39,17 @@@ obj-$(CONFIG_PINCTRL_OXNAS)        += pinctrl-
>   obj-$(CONFIG_PINCTRL_PALMAS)  += pinctrl-palmas.o
>   obj-$(CONFIG_PINCTRL_PIC32)   += pinctrl-pic32.o
>   obj-$(CONFIG_PINCTRL_PISTACHIO)       += pinctrl-pistachio.o
> + obj-$(CONFIG_PINCTRL_RK805)   += pinctrl-rk805.o
>   obj-$(CONFIG_PINCTRL_ROCKCHIP)        += pinctrl-rockchip.o
>   obj-$(CONFIG_PINCTRL_SINGLE)  += pinctrl-single.o
> - obj-$(CONFIG_PINCTRL_SX150X)  += pinctrl-sx150x.o
> - obj-$(CONFIG_ARCH_TEGRA)      += tegra/
> - obj-$(CONFIG_PINCTRL_XWAY)    += pinctrl-xway.o
> - obj-$(CONFIG_PINCTRL_LANTIQ)  += pinctrl-lantiq.o
> - obj-$(CONFIG_PINCTRL_LPC18XX) += pinctrl-lpc18xx.o
> - obj-$(CONFIG_PINCTRL_TB10X)   += pinctrl-tb10x.o
> + obj-$(CONFIG_PINCTRL_STMFX)   += pinctrl-stmfx.o
>   obj-$(CONFIG_PINCTRL_ST)      += pinctrl-st.o
>  +obj-$(CONFIG_PINCTRL_STARFIVE)        += pinctrl-starfive.o
> - obj-$(CONFIG_PINCTRL_STMFX)   += pinctrl-stmfx.o
> - obj-$(CONFIG_PINCTRL_ZYNQ)    += pinctrl-zynq.o
> + obj-$(CONFIG_PINCTRL_SX150X)  += pinctrl-sx150x.o
> + obj-$(CONFIG_PINCTRL_TB10X)   += pinctrl-tb10x.o
> + obj-$(CONFIG_PINCTRL_THUNDERBAY) += pinctrl-thunderbay.o
>   obj-$(CONFIG_PINCTRL_ZYNQMP)  += pinctrl-zynqmp.o
> - obj-$(CONFIG_PINCTRL_INGENIC) += pinctrl-ingenic.o
> - obj-$(CONFIG_PINCTRL_RK805)   += pinctrl-rk805.o
> - obj-$(CONFIG_PINCTRL_OCELOT)  += pinctrl-ocelot.o
> - obj-$(CONFIG_PINCTRL_MICROCHIP_SGPIO) += pinctrl-microchip-sgpio.o
> - obj-$(CONFIG_PINCTRL_EQUILIBRIUM)   += pinctrl-equilibrium.o
> - obj-$(CONFIG_PINCTRL_K210)    += pinctrl-k210.o
> - obj-$(CONFIG_PINCTRL_KEEMBAY) += pinctrl-keembay.o
> + obj-$(CONFIG_PINCTRL_ZYNQ)    += pinctrl-zynq.o
>
>   obj-y                         += actions/
>   obj-$(CONFIG_ARCH_ASPEED)     += aspeed/



-- 
With Best Regards,
Andy Shevchenko

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

Re: linux-next: manual merge of the pinctrl tree with the arm-soc tree

[Andy Shevchenko]

On Tue, Dec 06, 2022 at 12:13:36PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next merge of the pinctrl tree got a conflict in:
> 
>   drivers/soc/fsl/qe/gpio.c
> 
> between commits:
> 
>   84582f9ed090 ("soc: fsl: qe: Avoid using gpio_to_desc()")
>   66310b5a0fc1 ("soc: fsl: qe: request pins non-exclusively")
> 
> from the arm-soc tree and commit:
> 
>   c9eb6e546a23 ("soc: fsl: qe: Switch to use fwnode instead of of_node")
> 
> from the pinctrl 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.

That's correct fix in my opinion. Thank you!

How to avoid conflict and why it's there I have explained here:
https://lore.kernel.org/linux-arm-kernel/Y43ij5rwNLOaztch@smile.fi.intel.com/

-- 
With Best Regards,
Andy Shevchenko

Re: linux-next: manual merge of the pinctrl tree with the arm-soc tree

[Andy Shevchenko]

On Tue, Dec 06, 2022 at 12:13:36PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next merge of the pinctrl tree got a conflict in:
> 
>   drivers/soc/fsl/qe/gpio.c
> 
> between commits:
> 
>   84582f9ed090 ("soc: fsl: qe: Avoid using gpio_to_desc()")
>   66310b5a0fc1 ("soc: fsl: qe: request pins non-exclusively")
> 
> from the arm-soc tree and commit:
> 
>   c9eb6e546a23 ("soc: fsl: qe: Switch to use fwnode instead of of_node")
> 
> from the pinctrl 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.

That's correct fix in my opinion. Thank you!

How to avoid conflict and why it's there I have explained here:
https://lore.kernel.org/linux-arm-kernel/Y43ij5rwNLOaztch@smile.fi.intel.com/

-- 
With Best Regards,
Andy Shevchenko



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

linux-next: manual merge of the pinctrl tree with the arm-soc tree

[Stephen Rothwell]

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

Hi all,

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

  drivers/soc/fsl/qe/gpio.c

between commits:

  84582f9ed090 ("soc: fsl: qe: Avoid using gpio_to_desc()")
  66310b5a0fc1 ("soc: fsl: qe: request pins non-exclusively")

from the arm-soc tree and commit:

  c9eb6e546a23 ("soc: fsl: qe: Switch to use fwnode instead of of_node")

from the pinctrl 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/soc/fsl/qe/gpio.c
index 1440922341d8,9abb45ab138b..000000000000
--- a/drivers/soc/fsl/qe/gpio.c
+++ b/drivers/soc/fsl/qe/gpio.c
@@@ -13,11 -13,14 +13,13 @@@
  #include <linux/err.h>
  #include <linux/io.h>
  #include <linux/of.h>
 -#include <linux/of_gpio.h>
 +#include <linux/of_gpio.h>	/* for of_mm_gpio_chip */
 +#include <linux/gpio/consumer.h>
  #include <linux/gpio/driver.h>
 -/* FIXME: needed for gpio_to_chip() get rid of this */
 -#include <linux/gpio.h>
  #include <linux/slab.h>
  #include <linux/export.h>
+ #include <linux/property.h>
+ 
  #include <soc/fsl/qe/qe.h>
  
  struct qe_gpio_chip {
@@@ -187,16 -181,8 +189,16 @@@ struct qe_pin *qe_pin_request(struct de
  		goto err0;
  	}
  
 +	qe_pin->controller = gpiochip_get_data(gc);
 +	/*
 +	 * FIXME: this gets the local offset on the gpio_chip so that the driver
 +	 * can manipulate pin control settings through its custom API. The real
 +	 * solution is to create a real pin control driver for this.
 +	 */
 +	qe_pin->num = gpio_num - gc->base;
 +
- 	if (!of_device_is_compatible(gc->of_node, "fsl,mpc8323-qe-pario-bank")) {
+ 	if (!fwnode_device_is_compatible(gc->fwnode, "fsl,mpc8323-qe-pario-bank")) {
 -		pr_debug("%s: tried to get a non-qe pin\n", __func__);
 +		dev_dbg(dev, "%s: tried to get a non-qe pin\n", __func__);
  		err = -EINVAL;
  		goto err0;
  	}

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

linux-next: manual merge of the pinctrl tree with the arm-soc tree

[Stephen Rothwell]

[-- Attachment #1.1: Type: text/plain, Size: 2199 bytes --]

Hi all,

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

  drivers/soc/fsl/qe/gpio.c

between commits:

  84582f9ed090 ("soc: fsl: qe: Avoid using gpio_to_desc()")
  66310b5a0fc1 ("soc: fsl: qe: request pins non-exclusively")

from the arm-soc tree and commit:

  c9eb6e546a23 ("soc: fsl: qe: Switch to use fwnode instead of of_node")

from the pinctrl 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/soc/fsl/qe/gpio.c
index 1440922341d8,9abb45ab138b..000000000000
--- a/drivers/soc/fsl/qe/gpio.c
+++ b/drivers/soc/fsl/qe/gpio.c
@@@ -13,11 -13,14 +13,13 @@@
  #include <linux/err.h>
  #include <linux/io.h>
  #include <linux/of.h>
 -#include <linux/of_gpio.h>
 +#include <linux/of_gpio.h>	/* for of_mm_gpio_chip */
 +#include <linux/gpio/consumer.h>
  #include <linux/gpio/driver.h>
 -/* FIXME: needed for gpio_to_chip() get rid of this */
 -#include <linux/gpio.h>
  #include <linux/slab.h>
  #include <linux/export.h>
+ #include <linux/property.h>
+ 
  #include <soc/fsl/qe/qe.h>
  
  struct qe_gpio_chip {
@@@ -187,16 -181,8 +189,16 @@@ struct qe_pin *qe_pin_request(struct de
  		goto err0;
  	}
  
 +	qe_pin->controller = gpiochip_get_data(gc);
 +	/*
 +	 * FIXME: this gets the local offset on the gpio_chip so that the driver
 +	 * can manipulate pin control settings through its custom API. The real
 +	 * solution is to create a real pin control driver for this.
 +	 */
 +	qe_pin->num = gpio_num - gc->base;
 +
- 	if (!of_device_is_compatible(gc->of_node, "fsl,mpc8323-qe-pario-bank")) {
+ 	if (!fwnode_device_is_compatible(gc->fwnode, "fsl,mpc8323-qe-pario-bank")) {
 -		pr_debug("%s: tried to get a non-qe pin\n", __func__);
 +		dev_dbg(dev, "%s: tried to get a non-qe pin\n", __func__);
  		err = -EINVAL;
  		goto err0;
  	}

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

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

linux-next: manual merge of the pinctrl tree with the arm-soc tree

[Stephen Rothwell]

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

Hi all,

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

  MAINTAINERS

between commit:

  b82621ac8450 ("soc: loongson: add GUTS driver for loongson-2 platforms")

from the arm-soc tree and commit:

  457ff9fb29d7 ("dt-bindings: pinctrl: add loongson-2 pinctrl")

from the pinctrl 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 MAINTAINERS
index ec383d27e762,f76107c24949..000000000000
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@@ -12097,13 -12013,14 +12097,21 @@@ F:	drivers/*/*loongarch
  F:	Documentation/loongarch/
  F:	Documentation/translations/zh_CN/loongarch/
  
 +LOONGSON-2 SOC SERIES GUTS DRIVER
 +M:	Yinbo Zhu <zhuyinbo@loongson.cn>
 +L:	loongarch@lists.linux.dev
 +S:	Maintained
 +F:	Documentation/devicetree/bindings/hwinfo/loongson,ls2k-chipid.yaml
 +F:	drivers/soc/loongson/loongson2_guts.c
 +
+ LOONGSON-2 SOC SERIES PINCTRL DRIVER
+ M:	zhanghongchen <zhanghongchen@loongson.cn>
+ M:	Yinbo Zhu <zhuyinbo@loongson.cn>
+ L:	linux-gpio@vger.kernel.org
+ S:	Maintained
+ F:	Documentation/devicetree/bindings/pinctrl/loongson,ls2k-pinctrl.yaml
+ F:	drivers/pinctrl/pinctrl-loongson2.c
+ 
  LSILOGIC MPT FUSION DRIVERS (FC/SAS/SPI)
  M:	Sathya Prakash <sathya.prakash@broadcom.com>
  M:	Sreekanth Reddy <sreekanth.reddy@broadcom.com>

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

linux-next: manual merge of the pinctrl tree with the arm-soc tree

[Stephen Rothwell]

[-- Attachment #1.1: Type: text/plain, Size: 1681 bytes --]

Hi all,

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

  MAINTAINERS

between commit:

  b82621ac8450 ("soc: loongson: add GUTS driver for loongson-2 platforms")

from the arm-soc tree and commit:

  457ff9fb29d7 ("dt-bindings: pinctrl: add loongson-2 pinctrl")

from the pinctrl 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 MAINTAINERS
index ec383d27e762,f76107c24949..000000000000
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@@ -12097,13 -12013,14 +12097,21 @@@ F:	drivers/*/*loongarch
  F:	Documentation/loongarch/
  F:	Documentation/translations/zh_CN/loongarch/
  
 +LOONGSON-2 SOC SERIES GUTS DRIVER
 +M:	Yinbo Zhu <zhuyinbo@loongson.cn>
 +L:	loongarch@lists.linux.dev
 +S:	Maintained
 +F:	Documentation/devicetree/bindings/hwinfo/loongson,ls2k-chipid.yaml
 +F:	drivers/soc/loongson/loongson2_guts.c
 +
+ LOONGSON-2 SOC SERIES PINCTRL DRIVER
+ M:	zhanghongchen <zhanghongchen@loongson.cn>
+ M:	Yinbo Zhu <zhuyinbo@loongson.cn>
+ L:	linux-gpio@vger.kernel.org
+ S:	Maintained
+ F:	Documentation/devicetree/bindings/pinctrl/loongson,ls2k-pinctrl.yaml
+ F:	drivers/pinctrl/pinctrl-loongson2.c
+ 
  LSILOGIC MPT FUSION DRIVERS (FC/SAS/SPI)
  M:	Sathya Prakash <sathya.prakash@broadcom.com>
  M:	Sreekanth Reddy <sreekanth.reddy@broadcom.com>

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

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

linux-next: manual merge of the pinctrl tree with the arm-soc tree

[Stephen Rothwell]

Hi Linus,

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

  arch/arm/mach-exynos/suspend.c

between commit:

  b4765037fc8c ("ARM: EXYNOS: Constify list of retention registers")

from the arm-soc tree and commit:

  07731019c59c ("pinctrl: samsung: Move retention control from mach-exynos to the pinctrl driver")

from the pinctrl tree.

I fixed it up (the latter removed the code updated by the former, so I
just did that) 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

linux-next: manual merge of the pinctrl tree with the arm-soc tree

[Stephen Rothwell]

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

Hi Linus,

Today's linux-next merge of the pinctrl tree got a conflict in
arch/arm/boot/dts/ste-nomadik-stn8815.dtsi between commit 2096eb80e446
("ARM: nomadik: move GPIO I2C to S8815 board file") and 43c4034963d6
("ARM: nomadik: set up MCDATDIR2") from the arm-soc tree and commits
68d41f23ce8d ("pinctrl: nomadik: force-convert to generic mux
bindings") and 1637d480f873 ("pinctrl: nomadik: force-convert to
generic config bindings") from the pinctrl tree.

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

I also added this merge fix patch:

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Mon, 10 Nov 2014 17:30:59 +1100
Subject: [PATCH] pinctrl: nomadik: fix up for binding changes

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 arch/arm/boot/dts/ste-nomadik-s8815.dts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/boot/dts/ste-nomadik-s8815.dts b/arch/arm/boot/dts/ste-nomadik-s8815.dts
index 7a7e2443503f..85d3b95dfdba 100644
--- a/arch/arm/boot/dts/ste-nomadik-s8815.dts
+++ b/arch/arm/boot/dts/ste-nomadik-s8815.dts
@@ -43,7 +43,7 @@
 		gpioi2c {
 			gpioi2c_default_mode: gpioi2c_default {
 				gpioi2c_default_cfg {
-					ste,pins = "GPIO73_C21", "GPIO74_C20";
+					pins = "GPIO73_C21", "GPIO74_C20";
 					ste,input = <0>;
 				};
 			};
-- 
2.1.3

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

diff --cc arch/arm/boot/dts/ste-nomadik-stn8815.dtsi
index f435ff20aefe,c8b4a93180f8..000000000000
--- a/arch/arm/boot/dts/ste-nomadik-stn8815.dtsi
+++ b/arch/arm/boot/dts/ste-nomadik-stn8815.dtsi
@@@ -116,8 -116,8 +116,8 @@@
  		mmcsd {
  			mmcsd_default_mux: mmcsd_mux {
  				mmcsd_default_mux {
- 					ste,function = "mmcsd";
- 					ste,pins = "mmcsd_a_1", "mmcsd_b_1";
+ 					function = "mmcsd";
 -					groups = "mmcsd_a_1";
++					groups = "mmcsd_a_1", "mmcsd_b_1";
  				};
  			};
  			mmcsd_default_mode: mmcsd_default {
@@@ -127,9 -127,9 +127,9 @@@
  					ste,output = <0>;
  				};
  				mmcsd_default_cfg2 {
 -					/* MCCMDDIR, MCDAT0DIR, MCDAT31DIR */
 +					/* MCCMDDIR, MCDAT0DIR, MCDAT31DIR, MCDATDIR2 */
- 					ste,pins = "GPIO10_C11", "GPIO15_A12",
+ 					pins = "GPIO10_C11", "GPIO15_A12",
 -					"GPIO16_C13";
 +					"GPIO16_C13", "GPIO23_D15";
  					ste,output = <1>;
  				};
  				mmcsd_default_cfg3 {

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