devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: Kishon Vijay Abraham I <kishon@ti.com>,
	Vinod Koul <vkoul@kernel.org>, Lee Jones <lee.jones@linaro.org>,
	Rob Herring <robh+dt@kernel.org>
Cc: linux-phy@lists.infradead.org,
	"Florian Fainelli" <f.fainelli@gmail.com>,
	"Chunfeng Yun" <chunfeng.yun@mediatek.com>,
	devicetree@vger.kernel.org, "Rafał Miłecki" <rafal@milecki.pl>
Subject: [PATCH 3/4] dt-bindings: mfd: brcm,cru: add USB 2.0 PHY
Date: Mon, 13 Sep 2021 10:00:23 +0200	[thread overview]
Message-ID: <20210913080024.6951-3-zajec5@gmail.com> (raw)
In-Reply-To: <20210913080024.6951-1-zajec5@gmail.com>

From: Rafał Miłecki <rafal@milecki.pl>

Northstar's USB 2.0 PHY is part of the CRU MFD.

Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
---
 .../devicetree/bindings/mfd/brcm,cru.yaml         | 15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/mfd/brcm,cru.yaml b/Documentation/devicetree/bindings/mfd/brcm,cru.yaml
index bf4e585d3c18..262284ae80f1 100644
--- a/Documentation/devicetree/bindings/mfd/brcm,cru.yaml
+++ b/Documentation/devicetree/bindings/mfd/brcm,cru.yaml
@@ -39,6 +39,9 @@ patternProperties:
   '^clock-controller@[a-f0-9]+$':
     $ref: ../clock/brcm,iproc-clocks.yaml
 
+  '^phy@[a-f0-9]+$':
+    $ref: ../phy/bcm-ns-usb2-phy.yaml
+
   '^syscon@[a-f0-9]+$':
     $ref: syscon.yaml
 
@@ -52,6 +55,7 @@ required:
 
 examples:
   - |
+    #include <dt-bindings/clock/bcm-nsp.h>
     cru-bus@1800c100 {
         compatible = "brcm,ns-cru", "simple-mfd";
         reg = <0x1800c100 0x1d0>;
@@ -76,7 +80,16 @@ examples:
                                  "iprocfast", "sata1", "sata2";
         };
 
-        syscon@180 {
+        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>;
         };
-- 
2.26.2


  parent reply	other threads:[~2021-09-13  8:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-13  8:00 [PATCH 1/4] dt-bindings: mfd: brcm,cru: add clkset syscon Rafał Miłecki
2021-09-13  8:00 ` [PATCH 2/4] dt-bindings: phy: brcm,ns-usb2-phy: bind just a PHY block Rafał Miłecki
2021-09-21 20:19   ` Rob Herring
2021-10-01 10:08   ` Vinod Koul
2021-09-13  8:00 ` Rafał Miłecki [this message]
2021-09-21 20:19   ` [PATCH 3/4] dt-bindings: mfd: brcm,cru: add USB 2.0 PHY Rob Herring
2021-09-22  7:57   ` Lee Jones
2021-09-23 15:01     ` Rob Herring
2021-09-23 20:06       ` Lee Jones
2021-09-13  8:00 ` [PATCH 4/4] phy: bcm-ns-usb2: support updated DT binding with PHY reg space Rafał Miłecki
2021-09-21 20:19 ` [PATCH 1/4] dt-bindings: mfd: brcm,cru: add clkset syscon Rob Herring
2021-09-22  7:57 ` Lee Jones

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=20210913080024.6951-3-zajec5@gmail.com \
    --to=zajec5@gmail.com \
    --cc=chunfeng.yun@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=kishon@ti.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=rafal@milecki.pl \
    --cc=robh+dt@kernel.org \
    --cc=vkoul@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).