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>, Rob Herring <robh+dt@kernel.org>
Cc: "Krzysztof Kozlowski" <krzk@kernel.org>,
	"Simon Arlott" <simon@octiron.net>,
	"Álvaro Fernández Rojas" <noltari@gmail.com>,
	"Al Cooper" <alcooperx@gmail.com>,
	"Florian Fainelli" <f.fainelli@gmail.com>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	bcm-kernel-feedback-list@broadcom.com,
	"Rafał Miłecki" <rafal@milecki.pl>
Subject: [PATCH 1/2] dt-bindings: phy: Add binding for BCM4908 USB PHYs
Date: Wed,  2 Dec 2020 21:46:48 +0100	[thread overview]
Message-ID: <20201202204649.25314-1-zajec5@gmail.com> (raw)

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

BCM4908 SoCs have USB 2.0 PHY and USB 3.0 PHY attached to the MDIO bus.
Those bindings allow describing them.

Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
---
 .../bindings/phy/bcm4908-usb-phy.yaml         | 52 +++++++++++++++++++
 1 file changed, 52 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/phy/bcm4908-usb-phy.yaml

diff --git a/Documentation/devicetree/bindings/phy/bcm4908-usb-phy.yaml b/Documentation/devicetree/bindings/phy/bcm4908-usb-phy.yaml
new file mode 100644
index 000000000000..2bf5dcb58c1e
--- /dev/null
+++ b/Documentation/devicetree/bindings/phy/bcm4908-usb-phy.yaml
@@ -0,0 +1,52 @@
+# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/phy/bcm4908-usb-phy.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Broadcom BCM4908 USB PHYs
+
+description: >
+  This binding describes USB PHYs used in BCM4908 family SoCs.
+
+maintainers:
+  - Rafał Miłecki <rafal@milecki.pl>
+
+properties:
+  compatible:
+    enum:
+      - brcm,bcm4908-usb2-phy
+      - brcm,bcm4908-usb3-phy
+
+  reg:
+    items:
+      - description: PHY MDIO address
+
+  "#phy-cells":
+    const: 0
+
+required:
+  - compatible
+  - reg
+  - "#phy-cells"
+
+additionalProperties: false
+
+examples:
+  - |
+    mdio {
+        #address-cells = <1>;
+        #size-cells = <0>;
+
+        phy@0 {
+            compatible = "brcm,bcm4908-usb2-phy";
+            reg = <0x0>;
+            #phy-cells = <0>;
+        };
+
+        phy@1 {
+            compatible = "brcm,bcm4908-usb3-phy";
+            reg = <0x1>;
+            #phy-cells = <0>;
+        };
+    };
-- 
2.26.2


             reply	other threads:[~2020-12-02 20:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02 20:46 Rafał Miłecki [this message]
2020-12-02 20:46 ` [PATCH 2/2] phy: phy-bcm4908-usb: Add drivers for USB PHYs Rafał Miłecki
2020-12-07 22:08 ` [PATCH 1/2] dt-bindings: phy: Add binding for BCM4908 " Rafał Miłecki

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=20201202204649.25314-1-zajec5@gmail.com \
    --to=zajec5@gmail.com \
    --cc=alcooperx@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=kishon@ti.com \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=noltari@gmail.com \
    --cc=rafal@milecki.pl \
    --cc=robh+dt@kernel.org \
    --cc=simon@octiron.net \
    --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).