From: Pratyush Yadav <p.yadav@ti.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: Pratyush Yadav <p.yadav@ti.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Swapnil Jakhade <sjakhade@cadence.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-phy@lists.infradead.org>
Subject: [PATCH v7 4/4] phy: dt-bindings: Add Cadence D-PHY Rx bindings
Date: Mon, 27 Dec 2021 16:25:45 +0530 [thread overview]
Message-ID: <20211227105545.4852-5-p.yadav@ti.com> (raw)
In-Reply-To: <20211227105545.4852-1-p.yadav@ti.com>
The Rx mode DPHY is different from Tx mode DPHY. Add a separate binding
for it.
Signed-off-by: Pratyush Yadav <p.yadav@ti.com>
---
(no changes since v6)
Changes in v6:
- Add a new binding for DPHY Rx.
.../devicetree/bindings/phy/cdns,dphy-rx.yaml | 42 +++++++++++++++++++
1 file changed, 42 insertions(+)
create mode 100644 Documentation/devicetree/bindings/phy/cdns,dphy-rx.yaml
diff --git a/Documentation/devicetree/bindings/phy/cdns,dphy-rx.yaml b/Documentation/devicetree/bindings/phy/cdns,dphy-rx.yaml
new file mode 100644
index 000000000000..07be031d82e6
--- /dev/null
+++ b/Documentation/devicetree/bindings/phy/cdns,dphy-rx.yaml
@@ -0,0 +1,42 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/phy/cdns,dphy-rx.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Cadence DPHY Rx Device Tree Bindings
+
+maintainers:
+ - Pratyush Yadav <p.yadav@ti.com>
+
+properties:
+ compatible:
+ items:
+ - const: cdns,dphy-rx
+
+ reg:
+ maxItems: 1
+
+ "#phy-cells":
+ const: 0
+
+ power-domains:
+ maxItems: 1
+
+required:
+ - compatible
+ - reg
+ - "#phy-cells"
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/soc/ti,sci_pm_domain.h>
+
+ dphy0: phy@4580000 {
+ compatible = "cdns,dphy-rx";
+ reg = <0x4580000 0x1100>;
+ #phy-cells = <0>;
+ power-domains = <&k3_pds 147 TI_SCI_PD_EXCLUSIVE>;
+ };
--
2.33.1.835.ge9e5ba39a7
next prev parent reply other threads:[~2021-12-27 10:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 10:55 [PATCH v7 0/4] Rx mode support for Cadence DPHY Pratyush Yadav
2021-12-27 10:55 ` [PATCH v7 1/4] phy: cadence: Add Cadence D-PHY Rx driver Pratyush Yadav
2021-12-29 23:30 ` Laurent Pinchart
2021-12-31 10:28 ` Pratyush Yadav
2022-01-04 11:11 ` kernel test robot
2022-01-05 5:27 ` kernel test robot
2021-12-27 10:55 ` [PATCH v7 2/4] phy: dt-bindings: Convert Cadence DPHY binding to YAML Pratyush Yadav
2021-12-27 10:55 ` [PATCH v7 3/4] phy: dt-bindings: cdns,dphy: add power-domains property Pratyush Yadav
2021-12-27 10:55 ` Pratyush Yadav [this message]
2021-12-27 16:57 ` [PATCH v7 4/4] phy: dt-bindings: Add Cadence D-PHY Rx bindings Rob Herring
2021-12-27 20:48 ` Pratyush Yadav
2021-12-29 23:14 ` Laurent Pinchart
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=20211227105545.4852-5-p.yadav@ti.com \
--to=p.yadav@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=paul.kocialkowski@bootlin.com \
--cc=robh+dt@kernel.org \
--cc=sjakhade@cadence.com \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=vigneshr@ti.com \
--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).