mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Walleij <linus.walleij@linaro.org>,
	Lee Jones <lee.jones@linaro.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>,
	"Rafał Miłecki" <rafal@milecki.pl>
Subject: linux-next: manual merge of the pinctrl tree with the mfd tree
Date: Fri, 15 Oct 2021 17:06:03 +1100	[thread overview]
Message-ID: <20211015170603.578fc6c2@canb.auug.org.au> (raw)

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

Hi all,

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

  Documentation/devicetree/bindings/mfd/brcm,cru.yaml

between commits:

  de80ebd88b9e ("dt-bindings: mfd: brcm,cru: Add clkset syscon")
  dcc24e936da2 ("dt-bindings: mfd: brcm,cru: Add USB 2.0 PHY")

from the mfd tree and commit:

  0398adaec341 ("Revert "dt-bindings: pinctrl: bcm4708-pinmux: rework binding to use syscon"")

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 Documentation/devicetree/bindings/mfd/brcm,cru.yaml
index 262284ae80f1,28ac60acf4ac..000000000000
--- a/Documentation/devicetree/bindings/mfd/brcm,cru.yaml
+++ b/Documentation/devicetree/bindings/mfd/brcm,cru.yaml
@@@ -39,12 -36,9 +36,15 @@@ patternProperties
    '^clock-controller@[a-f0-9]+$':
      $ref: ../clock/brcm,iproc-clocks.yaml
  
 +  '^phy@[a-f0-9]+$':
 +    $ref: ../phy/bcm-ns-usb2-phy.yaml
 +
+   '^pin-controller@[a-f0-9]+$':
+     $ref: ../pinctrl/brcm,ns-pinmux.yaml
+ 
 +  '^syscon@[a-f0-9]+$':
 +    $ref: syscon.yaml
 +
    '^thermal@[a-f0-9]+$':
      $ref: ../thermal/brcm,ns-thermal.yaml
  
@@@ -80,23 -73,10 +80,24 @@@ examples
                                   "iprocfast", "sata1", "sata2";
          };
  
 +        phy@164 {
 +            compatible = "brcm,ns-usb2-phy";
 +            reg = <0x164 0x4>;
 +            brcm,syscon-clkset = <&clkset>;
 +            clocks = <&genpll BCM_NSP_GENPLL_USB_PHY_REF_CLK>;
 +            clock-names = "phy-ref-clk";
 +            #phy-cells = <0>;
 +        };
 +
 +        clkset: syscon@180 {
 +            compatible = "brcm,cru-clkset", "syscon";
 +            reg = <0x180 0x4>;
 +        };
 +
-         pinctrl {
+         pin-controller@1c0 {
              compatible = "brcm,bcm4708-pinmux";
-             offset = <0x1c0>;
+             reg = <0x1c0 0x24>;
+             reg-names = "cru_gpio_control";
          };
  
          thermal@2c0 {

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

             reply	other threads:[~2021-10-15  6:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-15  6:06 Stephen Rothwell [this message]
2021-10-26  6:27 ` Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20211015170603.578fc6c2@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rafal@milecki.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®