From: Dan Murphy <dmurphy@ti.com>
To: <davem@davemloft.net>, <andrew@lunn.ch>, <f.fainelli@gmail.com>,
<hkallweit1@gmail.com>
Cc: <mkubecek@suse.cz>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Dan Murphy <dmurphy@ti.com>
Subject: [PATCH net-next v2 0/3] 100base Fx link modes
Date: Fri, 18 Sep 2020 14:14:50 -0500 [thread overview]
Message-ID: <20200918191453.13914-1-dmurphy@ti.com> (raw)
Hello
As per patch https://lore.kernel.org/patchwork/patch/1300241/ the link
modes for 100base FX full and half duplex modes did not exist. Adding these
link modes to the core and ethtool allow devices like the DP83822, DP83869 and
Broadcomm PHYs to properly advertise the correct mode for Fiber 100Mbps.
Corresponding user land ethtool patches are available but rely on these patches
to be applied first.
Dan
Dan Murphy (3):
ethtool: Add 100base-FX link mode entries
net: dp83869: Add ability to advertise Fiber connection
net: phy: dp83822: Update the fiber advertisement for speed
drivers/net/phy/dp83822.c | 13 +++++--
drivers/net/phy/dp83869.c | 73 ++++++++++++++++++++++++++++++++++++
drivers/net/phy/phy-core.c | 4 +-
include/uapi/linux/ethtool.h | 2 +
net/ethtool/common.c | 2 +
net/ethtool/linkmodes.c | 2 +
6 files changed, 92 insertions(+), 4 deletions(-)
--
2.28.0
next reply other threads:[~2020-09-18 19:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 19:14 Dan Murphy [this message]
2020-09-18 19:14 ` [PATCH net-next v2 1/3] ethtool: Add 100base-FX link mode entries Dan Murphy
2020-09-18 19:24 ` Andrew Lunn
2020-09-18 20:14 ` Florian Fainelli
2020-09-18 19:14 ` [PATCH net-next v2 2/3] net: dp83869: Add ability to advertise Fiber connection Dan Murphy
2020-09-18 19:27 ` Andrew Lunn
2020-09-18 20:16 ` Florian Fainelli
2020-09-18 19:14 ` [PATCH net-next v2 3/3] net: phy: dp83822: Update the fiber advertisement for speed Dan Murphy
2020-09-18 19:29 ` Andrew Lunn
2020-09-18 20:17 ` Florian Fainelli
2020-09-19 23:55 ` [PATCH net-next v2 0/3] 100base Fx link modes David Miller
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=20200918191453.13914-1-dmurphy@ti.com \
--to=dmurphy@ti.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mkubecek@suse.cz \
--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).