From: Dan Murphy <dmurphy@ti.com>
To: <andrew@lunn.ch>, <f.fainelli@gmail.com>, <hkallweit1@gmail.com>,
<davem@davemloft.net>, <robh@kernel.org>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>, Dan Murphy <dmurphy@ti.com>
Subject: [PATCH net-next v4 0/4] RGMII Internal delay common property
Date: Wed, 27 May 2020 11:49:30 -0500 [thread overview]
Message-ID: <20200527164934.28651-1-dmurphy@ti.com> (raw)
Hello
The RGMII internal delay is a common setting found in most RGMII capable PHY
devices. It was found that many vendor specific device tree properties exist
to do the same function. This creates a common property to be used for PHY's
that have tunable internal delays for the Rx and Tx paths.
Dan Murphy (4):
dt-bindings: net: Add tx and rx internal delays
net: phy: Add a helper to return the index for of the internal delay
dt-bindings: net: Add RGMII internal delay for DP83869
net: dp83869: Add RGMII internal delay configuration
.../bindings/net/ethernet-controller.yaml | 14 ++++
.../devicetree/bindings/net/ti,dp83869.yaml | 16 ++++
drivers/net/phy/dp83869.c | 82 ++++++++++++++++++-
drivers/net/phy/phy_device.c | 51 ++++++++++++
include/linux/phy.h | 2 +
5 files changed, 162 insertions(+), 3 deletions(-)
--
2.26.2
next reply other threads:[~2020-05-27 16:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 16:49 Dan Murphy [this message]
2020-05-27 16:49 ` [PATCH net-next v4 1/4] dt-bindings: net: Add tx and rx internal delays Dan Murphy
2020-05-29 18:25 ` Rob Herring
2020-05-29 19:24 ` Dan Murphy
2020-05-29 20:58 ` Rob Herring
2020-05-27 16:49 ` [PATCH net-next v4 2/4] net: phy: Add a helper to return the index for of the internal delay Dan Murphy
2020-05-27 16:49 ` [PATCH net-next v4 3/4] dt-bindings: net: Add RGMII internal delay for DP83869 Dan Murphy
2020-05-29 19:03 ` Rob Herring
2020-05-29 19:20 ` Dan Murphy
2020-05-27 16:49 ` [PATCH net-next v4 4/4] net: dp83869: Add RGMII internal delay configuration Dan Murphy
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=20200527164934.28651-1-dmurphy@ti.com \
--to=dmurphy@ti.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh@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).