From: Raju Rangoju <Raju.Rangoju@amd•com>
To: <thomas.lendacky@amd•com>, <Shyam-sundar.S-k@amd•com>,
<davem@davemloft•net>, <kuba@kernel•org>
Cc: <netdev@vger•kernel.org>, <rrangoju@amd•com>,
Raju Rangoju <Raju.Rangoju@amd•com>
Subject: [PATCH net 0/3] amd-xgbe: Miscellaneous fixes
Date: Thu, 6 Oct 2022 19:24:37 +0530 [thread overview]
Message-ID: <20221006135440.3680563-1-Raju.Rangoju@amd.com> (raw)
Here are some of the fixes for XGBE:
(1) Fix the rrc for Yellow carp devices. CDR workaround path
is disabled for YC devices, receiver reset cycle is not
needed in such cases.
(2) Enable PLL_CTL for fixed PHY modes only. Driver does not
implement SW RRCM for Autoneg Off configuration, hence PLL
is needed for fixed PHY modes only.
(3) Fix the SFP compliance codes check for DAC cables. Some of
the passive cables have non-zero data at offset 3 and 6 in
SFP EEPROM data. So, fix the sfp compliance codes check.
Raju Rangoju (3):
amd-xgbe: Yellow carp devices do not need rrc
amd-xgbe: enable PLL_CTL for fixed PHY modes only
amd-xgbe: fix the SFP compliance codes check for DAC cables
drivers/net/ethernet/amd/xgbe/xgbe-pci.c | 5 ++++
drivers/net/ethernet/amd/xgbe/xgbe-phy-v2.c | 33 ++++++++++++---------
drivers/net/ethernet/amd/xgbe/xgbe.h | 11 +++++++
3 files changed, 35 insertions(+), 14 deletions(-)
--
2.25.1
next reply other threads:[~2022-10-06 13:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 13:54 Raju Rangoju [this message]
2022-10-06 13:54 ` [PATCH net 1/3] amd-xgbe: Yellow carp devices do not need rrc Raju Rangoju
2022-10-06 14:32 ` Tom Lendacky
2022-10-07 0:26 ` Jakub Kicinski
2022-10-08 18:27 ` Raju Rangoju
2022-10-06 13:54 ` [PATCH net 2/3] amd-xgbe: enable PLL_CTL for fixed PHY modes only Raju Rangoju
2022-10-06 14:47 ` Tom Lendacky
2022-10-06 17:23 ` Raju Rangoju
2022-10-06 13:54 ` [PATCH net 3/3] amd-xgbe: fix the SFP compliance codes check for DAC cables Raju Rangoju
2022-10-06 15:00 ` Tom Lendacky
[not found] ` <9a8552c2-0a23-ea1d-9d1c-56b7a6c75487@amd.com>
2022-10-06 19:04 ` Tom Lendacky
[not found] ` <77d8ea25-3557-cd6f-f732-20a046b29661@amd.com>
2022-10-07 14:27 ` Tom Lendacky
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=20221006135440.3680563-1-Raju.Rangoju@amd.com \
--to=raju.rangoju@amd$(echo .)com \
--cc=Shyam-sundar.S-k@amd$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=rrangoju@amd$(echo .)com \
--cc=thomas.lendacky@amd$(echo .)com \
/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