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>
Subject: Re: [PATCH net-next v7 6/6] net: phy: DP83822: Add ability to advertise Fiber connection
Date: Wed, 17 Jun 2020 13:27:08 -0500 [thread overview]
Message-ID: <4efcd835-e4e2-ddfa-d0f8-9f29f574eb9e@ti.com> (raw)
In-Reply-To: <20200617182019.6790-7-dmurphy@ti.com>
All
On 6/17/20 1:20 PM, Dan Murphy wrote:
> The DP83822 can be configured to use the RGMII interface. There are
> independent fixed 3.5ns clock shift (aka internal delay) for the TX and RX
> paths. This allow either one to be set if the MII interface is RGMII and
> the value is set in the firmware node.
$subject is wrong. I used the 83822 fiber patch as my base as it had
90% of the work done that I needed for the
internal delay. I will fix it in v8 after review comments.
Dan
next prev parent reply other threads:[~2020-06-17 18:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 18:20 [PATCH net-next v7 0/6] RGMII Internal delay common property Dan Murphy
2020-06-17 18:20 ` [PATCH net-next v7 1/6] dt-bindings: net: Add tx and rx internal delays Dan Murphy
2020-06-18 1:43 ` Andrew Lunn
2020-06-18 2:01 ` Andrew Lunn
2020-06-18 13:44 ` Dan Murphy
2020-06-17 18:20 ` [PATCH net-next v7 2/6] net: phy: Add a helper to return the index for of the internal delay Dan Murphy
2020-06-18 1:51 ` Andrew Lunn
2020-06-18 13:41 ` Dan Murphy
2020-06-17 18:20 ` [PATCH net-next v7 3/6] dt-bindings: net: Add RGMII internal delay for DP83869 Dan Murphy
2020-06-17 18:20 ` [PATCH net-next v7 4/6] net: dp83869: Add RGMII internal delay configuration Dan Murphy
2020-06-17 18:20 ` [PATCH net-next v7 5/6] dt-bindings: net: dp83822: Add TI dp83822 phy Dan Murphy
2020-07-09 20:30 ` Rob Herring
2020-06-17 18:20 ` [PATCH net-next v7 6/6] net: phy: DP83822: Add ability to advertise Fiber connection Dan Murphy
2020-06-17 18:27 ` Dan Murphy [this message]
2020-06-18 0:00 ` Jakub Kicinski
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=4efcd835-e4e2-ddfa-d0f8-9f29f574eb9e@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).