From: jon.mason@broadcom•com (Jon Mason)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v4 2/7] Documentation: devicetree: add PHY lane swap binding
Date: Tue, 1 Nov 2016 16:59:14 -0400 [thread overview]
Message-ID: <20161101205913.GA27191@broadcom.com> (raw)
In-Reply-To: <20161101204826.GA21010@lunn.ch>
On Tue, Nov 01, 2016 at 09:48:26PM +0100, Andrew Lunn wrote:
> > +- enet-phy-lane-swap: If set, indicates the PHY device requires swapping the
> > + TX/RX lanes to function properly.
>
> Is 'requires' the right word here? The PHY performs the actual swap of
> the Tx/Rx lanes.
What I'm trying to say here is that without the lane swapping, the PHY
will not function properly. Thus, those PHYs require this parameter
to work. I am open to suggestions to reword the sentence to make it
clearer.
Thanks,
Jon
>
> Andrew
next prev parent reply other threads:[~2016-11-01 20:59 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 ` [PATCH v4 2/7] Documentation: devicetree: add PHY lane swap binding Jon Mason
2016-11-01 20:48 ` Andrew Lunn
2016-11-01 20:59 ` Jon Mason [this message]
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
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=20161101205913.GA27191@broadcom.com \
--to=jon.mason@broadcom$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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