All of lore.kernel.org
 help / color / mirror / Atom feed
From: <kostap@marvell.com>
To: <linux-arm-kernel@lists.infradead.org>
Cc: tmn505@gmail.com, andrew@lunn.ch, jaz@semihalf.com,
	gregory.clement@bootlin.com, nadavh@marvell.com,
	robh+dt@kernel.org, Konstantin Porotchkin <kostap@marvell.com>,
	stefanc@marvell.com, mw@semihalf.com, bpeled@marvell.com,
	sebastian.hesselbarth@gmail.com
Subject: [PATCH v3 1/4] Documentation/bindings: phy: update references to cp11x
Date: Mon, 21 Dec 2020 18:38:23 +0200	[thread overview]
Message-ID: <20201221163827.6679-2-kostap@marvell.com> (raw)
In-Reply-To: <20201221163827.6679-1-kostap@marvell.com>

From: Grzegorz Jaszczyk <jaz@semihalf.com>

The cp11x references in dts has changed, reflect it in comphy
documentation.

Signed-off-by: Grzegorz Jaszczyk <jaz@semihalf.com>
Signed-off-by: Konstantin Porotchkin <kostap@marvell.com>
---
 Documentation/devicetree/bindings/phy/phy-mvebu-comphy.txt | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/Documentation/devicetree/bindings/phy/phy-mvebu-comphy.txt b/Documentation/devicetree/bindings/phy/phy-mvebu-comphy.txt
index 8c60e6985950..5ffd0f55d010 100644
--- a/Documentation/devicetree/bindings/phy/phy-mvebu-comphy.txt
+++ b/Documentation/devicetree/bindings/phy/phy-mvebu-comphy.txt
@@ -42,22 +42,22 @@ Required properties (child nodes):
 
 Examples:
 
-	cpm_comphy: phy@120000 {
+	CP11X_LABEL(comphy): phy@120000 {
 		compatible = "marvell,comphy-cp110";
 		reg = <0x120000 0x6000>;
-		marvell,system-controller = <&cpm_syscon0>;
-		clocks = <&CP110_LABEL(clk) 1 5>, <&CP110_LABEL(clk) 1 6>,
-			 <&CP110_LABEL(clk) 1 18>;
+		marvell,system-controller = <&CP11X_LABEL(syscon0)>;
+		clocks = <&CP11X_LABEL(clk) 1 5>, <&CP11X_LABEL(clk) 1 6>,
+			 <&CP11X_LABEL(clk) 1 18>;
 		clock-names = "mg_clk", "mg_core_clk", "axi_clk";
 		#address-cells = <1>;
 		#size-cells = <0>;
 
-		cpm_comphy0: phy@0 {
+		CP11X_LABEL(comphy0): phy@0 {
 			reg = <0>;
 			#phy-cells = <1>;
 		};
 
-		cpm_comphy1: phy@1 {
+		CP11X_LABEL(comphy1): phy@1 {
 			reg = <1>;
 			#phy-cells = <1>;
 		};
-- 
2.17.1


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

  reply	other threads:[~2020-12-21 16:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-21 16:38 [PATCH v3 0/4] DTS updates for Marvell Armada CN913x platforms kostap
2020-12-21 16:38 ` kostap [this message]
2020-12-21 16:38 ` [PATCH v3 2/4] arch/arm64/boot/dts/marvell: fix NAND partitioning scheme kostap
2020-12-21 16:38 ` [PATCH v3 3/4] arm64: dts: cn913x: add device trees for topology B boards kostap
2020-12-21 17:07   ` Andrew Lunn
2020-12-21 17:42     ` [EXT] " Stefan Chulski
2020-12-21 17:46       ` Marcin Wojtas
2020-12-21 18:28         ` Stefan Chulski
2020-12-21 16:38 ` [PATCH v3 4/4] arm64: dts: add support for Marvell cn9130-crb platform kostap

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=20201221163827.6679-2-kostap@marvell.com \
    --to=kostap@marvell.com \
    --cc=andrew@lunn.ch \
    --cc=bpeled@marvell.com \
    --cc=gregory.clement@bootlin.com \
    --cc=jaz@semihalf.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mw@semihalf.com \
    --cc=nadavh@marvell.com \
    --cc=robh+dt@kernel.org \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=stefanc@marvell.com \
    --cc=tmn505@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.