From: Simon Horman <horms@kernel.org>
To: Raju Rangoju <Raju.Rangoju@amd.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, Shyam-sundar.S-k@amd.com,
Sudheesh Mavila <sudheesh.mavila@amd.com>
Subject: Re: [PATCH v4 net-next 2/2] amd-xgbe: add support for Crater ethernet device
Date: Wed, 7 Feb 2024 19:09:46 +0000 [thread overview]
Message-ID: <20240207190946.GM1297511@kernel.org> (raw)
In-Reply-To: <20240205204900.2442500-3-Raju.Rangoju@amd.com>
On Tue, Feb 06, 2024 at 02:19:00AM +0530, Raju Rangoju wrote:
> Add the necessary support to enable Crater ethernet device. Since the
> BAR1 address cannot be used to access the XPCS registers on Crater, use
> the smn functions.
>
> Some of the ethernet add-in-cards have dual PHY but share a single MDIO
> line (between the ports). In such cases, link inconsistencies are
> noticed during the heavy traffic and during reboot stress tests. Using
> smn calls helps avoid such race conditions.
>
> Suggested-by: Sudheesh Mavila <sudheesh.mavila@amd.com>
> Signed-off-by: Raju Rangoju <Raju.Rangoju@amd.com>
> ---
> drivers/net/ethernet/amd/xgbe/xgbe-common.h | 5 +
> drivers/net/ethernet/amd/xgbe/xgbe-dev.c | 57 ++++++++
> drivers/net/ethernet/amd/xgbe/xgbe-pci.c | 33 ++++-
> drivers/net/ethernet/amd/xgbe/xgbe-smn.h | 139 ++++++++++++++++++++
> drivers/net/ethernet/amd/xgbe/xgbe.h | 7 +
> 5 files changed, 240 insertions(+), 1 deletion(-)
> create mode 100644 drivers/net/ethernet/amd/xgbe/xgbe-smn.h
Hi Raju,
This patch seems to be doing a lot.
* Add support for XGBE_RN_PCI_DEVICE_ID to xgbe_pci_probe()
* Add fallback implementations of amd_smn_(write|read)()
* Add XGBE_XPCS_ACCESS_V3 support to xgbe_(read|write)_mmd_regs()
* Add XGBE_XPCS_ACCESS_V3 support to xgbe_pci_probe()
* Add support for PCI_VDEVICE(AMD, 0x1641)
So a similar theme to my comment on patch 1/1,
I wonder if it could be broken up into separate patches.
I will also say that I am surprised to see this driver using
full licence preambles rather than SPDX headers. I assume that
is due to direction from legal. And if so, I accept that you may not
be in a position to change this. But my comment stands.
...
next prev parent reply other threads:[~2024-02-07 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 20:48 [PATCH v4 net-next 0/2] amd-xgbe: add support for AMD Crater Raju Rangoju
2024-02-05 20:48 ` [PATCH v4 net-next 1/2] amd-xgbe: reorganize the code of XPCS access Raju Rangoju
2024-02-07 19:06 ` Simon Horman
2024-02-05 20:49 ` [PATCH v4 net-next 2/2] amd-xgbe: add support for Crater ethernet device Raju Rangoju
2024-02-07 19:09 ` Simon Horman [this message]
2024-02-12 11:57 ` Raju Rangoju
2024-02-17 16:03 ` Simon Horman
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=20240207190946.GM1297511@kernel.org \
--to=horms@kernel.org \
--cc=Raju.Rangoju@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sudheesh.mavila@amd.com \
/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).