From: Dan Murphy <dmurphy@ti.com>
To: <andrew@lunn.ch>, <f.fainelli@gmail.com>, <hkallweit1@gmail.com>,
<bunk@kernel.org>
Cc: <netdev@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <grygorii.strashko@ti.com>,
Dan Murphy <dmurphy@ti.com>
Subject: [PATCH net-master 0/1] DP83867 Speed optimization feature
Date: Fri, 31 Jan 2020 09:11:09 -0600 [thread overview]
Message-ID: <20200131151110.31642-1-dmurphy@ti.com> (raw)
Hello
Speed optimization, also known as link downshift, enables fallback to 100M
operation after multiple consecutive failed attempts at Gigabit link
establishment. Such a case could occur if cabling with only four wires
were connected instead of the standard cabling with eight wires.
Speed optimization also supports fallback to 10M if link establishment fails
in Gigabit and in 100M mode.
Speed optimization can be enabled via strap or via register configuration.
The 48 pin devices do not have the ability to strap this feature and the PHY
team suggested to enable this bit for all use cases.
Dan
Dan Murphy (1):
net: phy: dp83867: Add speed optimization feature
drivers/net/phy/dp83867.c | 48 +++++++++++++++++++++++++++++++++++++++
1 file changed, 48 insertions(+)
--
2.25.0
next reply other threads:[~2020-01-31 15:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 15:11 Dan Murphy [this message]
2020-01-31 15:11 ` [PATCH net-master 1/1] net: phy: dp83867: Add speed optimization feature Dan Murphy
2020-01-31 17:10 ` Jakub Kicinski
2020-01-31 17:14 ` Dan Murphy
2020-01-31 18:11 ` Jakub Kicinski
2020-01-31 18:36 ` Dan Murphy
2020-01-31 17:49 ` Florian Fainelli
2020-01-31 18:29 ` Dan Murphy
2020-01-31 18:42 ` Florian Fainelli
2020-01-31 19:14 ` Dan Murphy
2020-01-31 19:29 ` Florian Fainelli
2020-01-31 19:54 ` Dan Murphy
2020-01-31 20:02 ` Florian Fainelli
2020-01-31 20:10 ` Dan Murphy
2020-01-31 20:56 ` Heiner Kallweit
2020-02-01 1:30 ` Dan Murphy
2020-02-01 4:57 ` Florian Fainelli
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=20200131151110.31642-1-dmurphy@ti.com \
--to=dmurphy@ti.com \
--cc=andrew@lunn.ch \
--cc=bunk@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=grygorii.strashko@ti.com \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.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).