From: Stefan Eichenberger <eichest@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Russell King" <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Dimitri Fedrau" <dima.fedrau@gmail.com>,
"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>,
netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [net-next 3/3] net: phy: marvell-88q2xxx: Enable auto negotiation for mv88q2110
Date: Wed, 25 Sep 2024 13:56:39 +0200 [thread overview]
Message-ID: <ZvP6d2YNKKxJPGvQ@eichest-laptop> (raw)
In-Reply-To: <cfb43b2c-79f3-48b7-8466-e7f52d20ee56@lunn.ch>
Hi Andrew and Niklas,
On Sat, Sep 14, 2024 at 04:50:02PM +0200, Andrew Lunn wrote:
> > master, I can normally do:
> > ethtool -s end1 speed 1000 master-slave forced-slave
>
> You might want to try adding 'autoneg off'
>
> If the new default is to perform autoneg, speed 1000 tells it to try
> to autoneg only advertising 1000. If the link partner is not actually
> performing autoneg, it will never succeed.
>
> This is the regression i was talking about. For this device, due to
> its history, we might want to default to autoneg off.
>
> Andrew
You were right about the autoneg off. I wasn't able to turn it off in my
first trial because when autoneg is not working I also have to set the
duplex mode. So the following four things worked:
ethtool -s end1 autoneg off duplex full speed 1000 master-slave forced-slave
ethtool -s end1 autoneg off duplex full speed 1000 master-slave forced-master
ethtool -s end1 autoneg off duplex full speed 100 master-slave forced-slave
ethtool -s end1 autoneg off duplex full speed 100 master-slave forced-master
So for our use case everything is working fine now and we can live with
the fact that autoneg is the default.
Tested with a mv88q2110 device.
Tested-by: Stefan Eichenberger <eichest@gmail.com>
Thanks,
Stefan
prev parent reply other threads:[~2024-09-25 11:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 13:39 [net-next 0/3] net: phy: marvell-88q2xxx: Enable auto negotiation for mv88q2110 Niklas Söderlund
2024-09-06 13:39 ` [net-next 1/3] net: phy: marvell-88q2xxx: Align soft reset for mv88q2110 and mv88q2220 Niklas Söderlund
2024-09-10 20:21 ` Andrew Lunn
2024-09-12 16:51 ` Dimitri Fedrau
2024-09-25 12:22 ` Stefan Eichenberger
2024-09-06 13:39 ` [net-next 2/3] net: phy: marvell-88q2xxx: Make register writer function generic Niklas Söderlund
2024-09-06 20:18 ` Andrew Lunn
2024-09-10 20:21 ` Andrew Lunn
2024-09-12 16:52 ` Dimitri Fedrau
2024-09-25 12:23 ` Stefan Eichenberger
2024-09-06 13:39 ` [net-next 3/3] net: phy: marvell-88q2xxx: Enable auto negotiation for mv88q2110 Niklas Söderlund
2024-09-06 20:36 ` Andrew Lunn
2024-09-06 21:39 ` Niklas Söderlund
2024-09-10 16:32 ` Andrew Lunn
2024-09-10 18:02 ` Stefan Eichenberger
2024-09-10 20:18 ` Andrew Lunn
2024-09-10 20:23 ` Andrew Lunn
2024-09-14 14:00 ` Stefan Eichenberger
2024-09-14 14:21 ` Niklas Söderlund
2024-09-14 14:43 ` Andrew Lunn
2024-09-25 13:04 ` Stefan Eichenberger
2024-10-05 11:08 ` Niklas Söderlund
2024-09-14 14:50 ` Andrew Lunn
2024-09-25 11:56 ` Stefan Eichenberger [this message]
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=ZvP6d2YNKKxJPGvQ@eichest-laptop \
--to=eichest@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dima.fedrau@gmail.com \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=pabeni@redhat.com \
--cc=yoshihiro.shimoda.uh@renesas.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