From: Andrew Lunn <andrew@lunn.ch>
To: Masahiko KIMOTO <masahiko.kimoto@cybertrust.co.jp>
Cc: f.fainelli@gmail.com, fugang.duan@nxp.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
hiraku.toyooka@cybertrust.co.jp
Subject: Re: [RFC PATCH 0/1] net: phy: skip autoneg of ethernet(fec) on network boot
Date: Mon, 9 Jul 2018 16:41:06 +0200 [thread overview]
Message-ID: <20180709144106.GJ10376@lunn.ch> (raw)
In-Reply-To: <20180709.182902.1637265651643155858.kimoto@cybertrust.co.jp>
On Mon, Jul 09, 2018 at 06:29:02PM +0900, Masahiko KIMOTO wrote:
> Hello Florian,
>
> > I completely acknowledge and support the use case, but your
> > implementation is definitively not the way to go. In my experience the
> > problem is usually that there may be a disagreement on the
> > Pause/Asym_Pause advertisement bits and that alone is responsible for
> > triggering a re-negotiation. Can yo check if that is the case here?
>
> Thank you for your support.
>
> Concening the problem about PAUSE/Asym_PAUSE advertisement you pointed out,
> I could not understand your consideration.
>
> Would you tell me more detail about it?
Hi Masahiko
You said that the PHY is being configured 3 times, and might be doing
auto-neg three times. Often a phy will not actually perform auto-neg,
or do it much faster, if the advertised bits do not change with each
re-configuration.
So check how u-boot is configuring what is advertised, and look at
what Linux is configuring. In particularly, look at the pause
configuration. If pause is configured different in u-boot and Linux,
try to make it the same. Things might go faster than.
Andrew
next prev parent reply other threads:[~2018-07-09 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1530857230-31124-1-git-send-email-masahiko.kimoto@cybertrust.co.jp>
2018-07-06 18:41 ` [RFC PATCH 0/1] net: phy: skip autoneg of ethernet(fec) on network boot Florian Fainelli
2018-07-09 9:29 ` Masahiko KIMOTO
2018-07-09 14:41 ` Andrew Lunn [this message]
2018-07-10 1:52 ` Masahiko KIMOTO
2018-07-17 1:47 ` Masahiko KIMOTO
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=20180709144106.GJ10376@lunn.ch \
--to=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=fugang.duan@nxp.com \
--cc=hiraku.toyooka@cybertrust.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiko.kimoto@cybertrust.co.jp \
--cc=netdev@vger.kernel.org \
/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).