netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: Stefan Eichenberger <eichest@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
	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: Sat, 14 Sep 2024 16:21:36 +0200	[thread overview]
Message-ID: <20240914142136.GC64607@ragnatech.se> (raw)
In-Reply-To: <ZuWW4UOtOGI_KmSg@eichest-laptop>

Hello,

On 2024-09-14 16:00:01 +0200, Stefan Eichenberger wrote:
> Hi Niklas and Andrew,
> 
> I was able to do a first basic test on my setup. I'm using the MV88Q2110
> and connecting it to a Göpel media converter that I use as a reference.

Thanks for testing this work.

> However, with your patch applied, I can't get a link. When I set a fixed
> link speed of 1GBit/s and the media converter is configured as the
> master, I can normally do: 
> ethtool -s end1 speed 1000 master-slave forced-slave
> After that, the link came up. However, with the changes made, I can't do
> this anymore. Can you reproduce this in your setup?

Without this patch I can't bring up a 1GBit/s link at all, I can only 
setup a 100 MBit/s link with,

    ethtool -s eth1 speed 100 master-slave forced-slave

If I do the same with speed set to a 1000 I never get a link. That's why 
autoneg is a such a boon for me, as with that I do get a 1 Gbit/s link.

As you have the MV88Q2110 datasheets, can you check the register writes 
in mv88q2110_init_seq0 and mv88q2110_init_seq1 for sanity? Maybe 
something is not quiet right there, I have only been able to reveres 
engineer support for autoneg so it's quiet likely.

> What is your setup
> like? Are you connecting two MV88Q2110 physically to each other?

Yes, I hair-pin two MV88Q2110 together.

> out
> of office again next week, afterwards I should be able to do some more
> testing again. I think being able to set fixed link speeds is a must for
> this PHY.

I'm also at LPC next week but I will do some more testing on this and 
see if I can reproduce your finding with a 100 speed link.

-- 
Kind Regards,
Niklas Söderlund

  reply	other threads:[~2024-09-14 14:21 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 [this message]
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

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=20240914142136.GC64607@ragnatech.se \
    --to=niklas.soderlund+renesas@ragnatech.se \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dima.fedrau@gmail.com \
    --cc=edumazet@google.com \
    --cc=eichest@gmail.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=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;
as well as URLs for NNTP newsgroup(s).