From: Hariprasad Kelam <hkelam@marvell.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kuba@kernel.org>, <davem@davemloft.net>, <sgoutham@marvell.com>,
<gakula@marvell.com>, <sbhatta@marvell.com>,
<naveenm@marvell.com>, <edumazet@google.com>, <pabeni@redhat.com>,
<andrew+netdev@lunn.ch>, <bbhushan2@marvell.com>
Subject: Re: Query regarding Phy loopback support
Date: Sun, 21 Sep 2025 23:14:55 +0530 [thread overview]
Message-ID: <aNA5l3JEl5JMHfZM@test-OptiPlex-Tower-Plus-7010> (raw)
In-Reply-To: <3b76cc60-f0c5-478b-b26c-e951a71d3d0b@lunn.ch>
On 2025-09-16 at 22:13:20, Andrew Lunn (andrew@lunn.ch) wrote:
> On Tue, Sep 16, 2025 at 04:48:56PM +0530, Hariprasad Kelam wrote:
> > We're looking for a standard way to configure PHY loopback on a network
> > interface using common Linux tools like ethtool, ip, or devlink.
> >
> > Currently, ethtool -k eth0 loopback on enables a generic loopback, but it
> > doesn't specify if it's an internal, external, or PHY loopback.
> > Need suggestions to implement this feature in a standard way.
>
> What actually do you mean by PHY loopback?
The Octeon silicon series supports both MAC (RPM) and PHY (GSERM) loopback
modes for testing.
We are seeking a solution to support the following loopback types:
MAC Level
Far-end loopback: Ingress data is routed back to egress data (MAC-to-MAC).
Near-end external loopback: Egress traffic is routed back to ingress traffic at the PCS layer.
PHY Level
Near-end digital loopback
Near-end analog loopback
Far-end digital loopback
Far-end analog loopback
We need suggestions on how to enable and manage these specific modes.
Thanks,
Hariprasad k
next prev parent reply other threads:[~2025-09-21 17:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 11:18 Query regarding Phy loopback support Hariprasad Kelam
2025-09-16 16:43 ` Andrew Lunn
2025-09-21 17:44 ` Hariprasad Kelam [this message]
2025-09-21 18:42 ` Andrew Lunn
2025-09-22 15:14 ` Maxime Chevallier
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=aNA5l3JEl5JMHfZM@test-OptiPlex-Tower-Plus-7010 \
--to=hkelam@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=bbhushan2@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naveenm@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.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