devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Mason <jon.mason@broadcom.com>
To: David Miller <davem@davemloft.net>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Florian Fainelli <f.fainelli@gmail.com>
Cc: rafal@milecki.pl, bcm-kernel-feedback-list@broadcom.com,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH v4 2/7] Documentation: devicetree: add PHY lane swap binding
Date: Tue,  1 Nov 2016 16:04:37 -0400	[thread overview]
Message-ID: <1478030682-27012-3-git-send-email-jon.mason@broadcom.com> (raw)
In-Reply-To: <1478030682-27012-1-git-send-email-jon.mason@broadcom.com>

Add the documentation for PHY lane swapping.  This is a boolean entry to
notify the phy device drivers that the TX/RX lanes need to be swapped.

Signed-off-by: Jon Mason <jon.mason@broadcom.com>
---
 Documentation/devicetree/bindings/net/phy.txt | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/Documentation/devicetree/bindings/net/phy.txt b/Documentation/devicetree/bindings/net/phy.txt
index bc1c3c8..3dce607 100644
--- a/Documentation/devicetree/bindings/net/phy.txt
+++ b/Documentation/devicetree/bindings/net/phy.txt
@@ -35,6 +35,9 @@ Optional Properties:
 - broken-turn-around: If set, indicates the PHY device does not correctly
   release the turn around line low at the end of a MDIO transaction.
 
+- enet-phy-lane-swap: If set, indicates the PHY device requires swapping the
+  TX/RX lanes to function properly.
+
 Example:
 
 ethernet-phy@0 {
-- 
2.7.4

  parent reply	other threads:[~2016-11-01 20:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-01 20:04 [PATCH v4 0/7] add NS2 support to bgmac Jon Mason
2016-11-01 20:04 ` [PATCH v4 1/7] net: phy: broadcom: add bcm54xx_auxctl_read Jon Mason
2016-11-01 20:04 ` Jon Mason [this message]
     [not found]   ` <1478030682-27012-3-git-send-email-jon.mason-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2016-11-01 20:48     ` [PATCH v4 2/7] Documentation: devicetree: add PHY lane swap binding Andrew Lunn
     [not found]       ` <20161101204826.GA21010-g2DYL2Zd6BY@public.gmane.org>
2016-11-01 20:59         ` Jon Mason
2016-11-01 21:01           ` Scott Branden
2016-11-01 21:09             ` Andrew Lunn
2016-11-01 20:04 ` [PATCH v4 3/7] net: phy: broadcom: Add BCM54810 PHY entry Jon Mason
2016-11-01 20:04 ` [PATCH v4 4/7] Documentation: devicetree: net: add NS2 bindings to amac Jon Mason
     [not found] ` <1478030682-27012-1-git-send-email-jon.mason-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2016-11-01 20:04   ` [PATCH v4 5/7] net: ethernet: bgmac: device tree phy enablement Jon Mason
2016-11-01 20:04 ` [PATCH v4 6/7] net: ethernet: bgmac: add NS2 support Jon Mason
2016-11-01 20:34   ` Scott Branden
2016-11-01 21:05     ` Jon Mason
2016-11-02 16:53       ` Jon Mason
2016-11-01 20:04 ` [PATCH v4 7/7] arm64: dts: NS2: add AMAC ethernet support Jon Mason

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=1478030682-27012-3-git-send-email-jon.mason@broadcom.com \
    --to=jon.mason@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=netdev@vger.kernel.org \
    --cc=rafal@milecki.pl \
    --cc=robh+dt@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).