All of lore.kernel.org
 help / color / mirror / Atom feed
From: nhed+uboot at starry.com <nhed+uboot@starry.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 5/7] arm: dts: armada-cp110-*dtsi: add xmdio nodes
Date: Tue,  6 Aug 2019 11:51:42 -0400	[thread overview]
Message-ID: <20190806155144.19301-6-nhed+uboot@starry.com> (raw)
In-Reply-To: <20190806155144.19301-1-nhed+uboot@starry.com>

From: Nevo Hed <nhed+github@starry.com>

Based on upstream-linux
See https://github.com/torvalds/linux/commit/f66b2aff.

However made the XSMI register window 0x16 (22) bytes per my reading
of the functional spec.  Similar commits in Marvels own repo bump it
to 0x200 (512) bytes but I did not see the reasoning for that.

https://github.com/MarvellEmbeddedProcessors/u-boot-marvell/commit/4d932b4.

Also added device-name attributes to prevent ambiguity in the `mdio`
command.

Signed-off-by: Nevo Hed <nhed+github@starry.com>
---
 arch/arm/dts/armada-cp110-master.dtsi | 9 +++++++++
 arch/arm/dts/armada-cp110-slave.dtsi  | 9 +++++++++
 2 files changed, 18 insertions(+)

diff --git a/arch/arm/dts/armada-cp110-master.dtsi b/arch/arm/dts/armada-cp110-master.dtsi
index e4c17e9f4b..cd5c974482 100644
--- a/arch/arm/dts/armada-cp110-master.dtsi
+++ b/arch/arm/dts/armada-cp110-master.dtsi
@@ -99,6 +99,15 @@
 				device-name = "cpm-mdio";
 			};
 
+			cpm_xmdio: mdio at 12a600 {
+				#address-cells = <1>;
+				#size-cells = <0>;
+				compatible = "marvell,xmdio";
+				reg = <0x12a600 0x16>;
+				status = "disabled";
+				device-name = "cpm-xmdio";
+			};
+
 			cpm_syscon0: system-controller at 440000 {
 				compatible = "marvell,cp110-system-controller0",
 					     "syscon";
diff --git a/arch/arm/dts/armada-cp110-slave.dtsi b/arch/arm/dts/armada-cp110-slave.dtsi
index 2fbd7b5514..b426a4eb69 100644
--- a/arch/arm/dts/armada-cp110-slave.dtsi
+++ b/arch/arm/dts/armada-cp110-slave.dtsi
@@ -99,6 +99,15 @@
 				device-name = "cps-mdio";
 			};
 
+			cps_xmdio: mdio at 12a600 {
+				#address-cells = <1>;
+				#size-cells = <0>;
+				compatible = "marvell,xmdio";
+				reg = <0x12a600 0x16>;
+				status = "disabled";
+				device-name = "cps-xmdio";
+			};
+
 			cps_syscon0: system-controller at 440000 {
 				compatible = "marvell,cp110-system-controller0",
 					     "syscon";
-- 
2.21.0

  parent reply	other threads:[~2019-08-06 15:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06 15:51 [U-Boot] [PATCH v3 0/7] Switch MVPP2 to use new MVMDIO nhed+uboot at starry.com
2019-08-06 15:51 ` [U-Boot] [PATCH v3 1/7] net: mvpp2x: fix traffic stuck after PHY start error nhed+uboot at starry.com
2019-08-07 17:50   ` Ramon Fried
2019-08-14 15:59   ` Joe Hershberger
2019-08-06 15:51 ` [U-Boot] [PATCH v3 2/7] net: mvpp2: Replace SMI implementation with marvell MDIO API nhed+uboot at starry.com
2019-08-07 17:52   ` Ramon Fried
2019-08-06 15:51 ` [U-Boot] [PATCH v3 3/7] net: mvpp2: mark phy as invalid in case of missing appropriate driver nhed+uboot at starry.com
2019-08-07 17:52   ` Ramon Fried
2019-08-06 15:51 ` [U-Boot] [PATCH v3 4/7] net: mvpp2: no deref null nhed+uboot at starry.com
2019-08-07 14:57   ` Ramon Fried
2019-08-06 15:51 ` nhed+uboot at starry.com [this message]
2019-08-07 17:54   ` [U-Boot] [PATCH v3 5/7] arm: dts: armada-cp110-*dtsi: add xmdio nodes Ramon Fried
2019-08-14 15:55   ` Joe Hershberger
2019-08-06 15:51 ` [U-Boot] [PATCH v3 6/7] net: mvpp2: use new MVMDIO driver nhed+uboot at starry.com
2019-08-14 15:59   ` Joe Hershberger
2019-08-06 15:51 ` [U-Boot] [PATCH v3 7/7] net: mvpp2: MVPP2 now needs MVMDIO nhed+uboot at starry.com
2019-08-07 14:56   ` Ramon Fried
2019-08-14 15:49   ` Joe Hershberger

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=20190806155144.19301-6-nhed+uboot@starry.com \
    --to=nhed+uboot@starry.com \
    --cc=u-boot@lists.denx.de \
    /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.