All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH v4 01/22] dt-bindings: net: Add the old DT bindings for "fixed-link"
Date: Sun, 14 Mar 2021 20:14:45 +0800	[thread overview]
Message-ID: <20210314121506.18303-2-bmeng.cn@gmail.com> (raw)
In-Reply-To: <20210314121506.18303-1-bmeng.cn@gmail.com>

Per the upstream Linux kernel doc:

  Documentation/devicetree/bindings/net/ethernet-controller.yaml

There are two ways to describe a fixed PHY attached to an Ethernet
device. This updates our dt-bindings doc to add the old DT bindings.

Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Ramon Fried <rfried.dev@gmail.com>
Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>

---

(no changes since v3)

Changes in v3:
- mention that U-Boot deliberately ignores the 'phy_id' and
  unconditionally uses PHY_FIXED_ID

 doc/device-tree-bindings/net/fixed-link.txt | 48 +++++++++++++++------
 1 file changed, 36 insertions(+), 12 deletions(-)

diff --git a/doc/device-tree-bindings/net/fixed-link.txt b/doc/device-tree-bindings/net/fixed-link.txt
index 5829bd81a2..5efeeb6fc5 100644
--- a/doc/device-tree-bindings/net/fixed-link.txt
+++ b/doc/device-tree-bindings/net/fixed-link.txt
@@ -5,21 +5,37 @@ Some Ethernet MACs have a "fixed link", and are not connected to a
 normal MDIO-managed PHY device. For those situations, a Device Tree
 binding allows to describe a "fixed link".
 
-Such a fixed link situation is described by creating a 'fixed-link'
-sub-node of the Ethernet MAC device node, with the following
-properties:
-
-* 'speed' (integer, mandatory), to indicate the link speed. Accepted
-  values are 10, 100 and 1000
-* 'full-duplex' (boolean, optional), to indicate that full duplex is
-  used. When absent, half duplex is assumed.
-* 'pause' (boolean, optional), to indicate that pause should be
-  enabled.
-* 'asym-pause' (boolean, optional), to indicate that asym_pause should
-  be enabled.
+Note there are two ways to describe a fixed PHY attached to an
+Ethernet device:
+
+- The new DT binding, where 'fixed-link' is a sub-node of the Ethernet
+  MAC device node, with the following properties:
+
+  * 'speed' (integer, mandatory), to indicate the link speed. Accepted
+    values are 10, 100 and 1000
+  * 'full-duplex' (boolean, optional), to indicate that full duplex is
+    used. When absent, half duplex is assumed.
+  * 'pause' (boolean, optional), to indicate that pause should be
+    enabled.
+  * 'asym-pause' (boolean, optional), to indicate that asym_pause should
+    be enabled.
+
+- The old DT binding, where 'fixed-link' is a property with 5 cells
+  encoding various information about the fixed PHY, in the form of
+  <phy_id, full-duplex, speed, pause, asym-pause>.
+
+  * 'phy_id', emulated PHY ID, choose any but unique to the all specified
+    fixed-links. Note U-Boot deliberately ignores the 'phy_id' and
+    unconditionally uses PHY_FIXED_ID.
+  * 'full-duplex', 0 for half duplex or 1 for full duplex
+  * 'speed', link speed in Mbits/sec, accepts only 10, 100 and 1000
+  * 'pause', 0 for no pause, 1 for pause
+  * 'asym-pause', 0 for no asymmetric pause, 1 for asymmetric pause
 
 Examples:
 
+The new binding:
+
 ethernet at 0 {
 	...
 	fixed-link {
@@ -28,3 +44,11 @@ ethernet at 0 {
 	};
 	...
 };
+
+The old binding:
+
+ethernet at 0 {
+	...
+	fixed-link = <0 1 1000 0 0>;
+	...
+};
-- 
2.25.1

  reply	other threads:[~2021-03-14 12:14 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-14 12:14 [PATCH v4 00/22] ppc: qemu: Add eTSEC support Bin Meng
2021-03-14 12:14 ` Bin Meng
2021-03-14 12:14 ` Bin Meng [this message]
2021-03-14 12:14 ` [PATCH v4 02/22] of: extra: Introduce ofnode_phy_is_fixed_link() API Bin Meng
2021-03-14 12:14 ` [PATCH v4 03/22] dm: mdio: Use " Bin Meng
2021-03-14 12:14 ` [PATCH v4 04/22] net: phy: fixed: Be compatible with live OF tree Bin Meng
2021-03-14 12:14 ` [PATCH v4 05/22] net: phy: fixed: Drop #ifdef CONFIG_DM_ETH around phy_connect_fixed Bin Meng
2021-03-14 12:14 ` [PATCH v4 06/22] net: phy: xilinx: Be compatible with live OF tree Bin Meng
2021-04-23  7:35   ` Michal Simek
2021-04-23  9:14     ` Bin Meng
2021-04-23  9:23       ` Bin Meng
2021-04-23 11:52         ` Michal Simek
2021-03-14 12:14 ` [PATCH v4 07/22] net: phy: xilinx: Drop #ifdef CONFIG_DM_ETH around phy_connect_gmii2rgmii() Bin Meng
2021-03-14 12:14 ` [PATCH v4 08/22] net: phy: Simplify the logic of phy_connect_fixed() Bin Meng
2021-03-14 12:14 ` [PATCH v4 09/22] net: phy: fixed: Make driver ops static Bin Meng
2021-03-14 12:14 ` [PATCH v4 10/22] net: phy: fixed: Add the missing ending newline Bin Meng
2021-03-14 12:14 ` [PATCH v4 11/22] net: phy: fixed: Support the old DT binding Bin Meng
2021-03-14 12:14 ` [PATCH v4 12/22] net: tsec: Use dm_eth_phy_connect() directly for the DM case Bin Meng
2021-03-14 12:14 ` [PATCH v4 13/22] sandbox: Add a DSA sandbox driver and unit test Bin Meng
2021-03-14 12:14 ` [PATCH v4 14/22] test: dm: Add a case to test ofnode_phy_is_fixed_link() Bin Meng
2021-03-14 12:14 ` [PATCH v4 15/22] net: tsec: Use map_physmem() directly instead of dev_remap_addr() Bin Meng
2021-03-14 12:15 ` [PATCH v4 16/22] dt-bindings: net: Update Freescale TSEC to support "queue-group" Bin Meng
2021-03-14 12:15 ` [PATCH v4 17/22] net: tsec: Support <reg> property from the subnode "queue-group" Bin Meng
2021-03-14 12:15 ` [PATCH v4 18/22] dm: core: Correctly read <ranges> of simple-bus Bin Meng
2021-03-14 12:15 ` [PATCH v4 19/22] test: dm: Add a test case for simple-bus <ranges> Bin Meng
2021-03-14 12:15 ` [PATCH v4 20/22] ppc: qemu: Create a virtual memory mapping of the platform bus Bin Meng
2021-03-14 12:15 ` [PATCH v4 21/22] ppc: qemu: Enable eTSEC support Bin Meng
2021-04-14 11:54   ` Priyanka Jain
2021-04-14 12:46     ` Tom Rini
2021-04-14 13:00     ` Bin Meng
2021-03-14 12:15 ` [PATCH v4 22/22] doc: board: qemu-ppce500: Document eTSEC usage Bin Meng
2021-04-06  8:48 ` [PATCH v4 00/22] ppc: qemu: Add eTSEC support Bin Meng
2021-04-06  8:48   ` Bin Meng
2021-04-08 15:29   ` Priyanka Jain
2021-04-08 15:29     ` Priyanka Jain

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=20210314121506.18303-2-bmeng.cn@gmail.com \
    --to=bmeng.cn@gmail.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.