From: Lukasz Majewski <lukma@denx.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Simon Horman <simon.horman@corigine.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Eric Dumazet <edumazet@google.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] phy: smsc: Implement .aneg_done callback for LAN8720Ai
Date: Wed, 12 Apr 2023 13:25:40 +0200 [thread overview]
Message-ID: <20230412132540.5a45564d@wsk> (raw)
In-Reply-To: <aa6415be-e99b-46df-bb3b-d2c732a33f31@lunn.ch>
[-- Attachment #1: Type: text/plain, Size: 1947 bytes --]
Hi Andrew,
> On Thu, Apr 06, 2023 at 03:48:43PM +0200, Simon Horman wrote:
> > On Thu, Apr 06, 2023 at 03:11:27PM +0200, Lukasz Majewski wrote:
> > > The LAN8720Ai has special bit (12) in the PHY SPECIAL
> > > CONTROL/STATUS REGISTER (dec 31) to indicate if the
> > > AutoNeg is finished.
> > >
> > > Signed-off-by: Lukasz Majewski <lukma@denx.de>
> >
> > Hi Lukasz,
> >
> > I think you need to rebase this on net-next.
> >
> > If you repost please also include 'net-next' in the subject:
> > [PATCH net-next v2].
> >
> > And a note about the changes between v1 and v2.
>
> This actually seems like a fix. So it should probably be based on net,
> and have a Fixes: tag.
I've rebased it on the newest vanila kernel.
And this patch come from the work on LAN8720Ai based system (speed up
of the boot time).
It turned out that this IC has a dedicated bit (in vendor specific
register) to show explicitly if auto neg is done.
>
> Lukasz, how does this bit differ to the one in BMSR?
In the BMSR - bit 5 (Auto Negotiate Complete) - shows the same kind of
information.
The only difference is that this bit is described as "Auto
Negotiate Complete" and the bit in this patch indicates "Auto
Negotiation Done".
> Is the BMSR bit
> broken?
This bit works as expected.
> Is there an errata for this?
No, errata doesn't mention it.
I just was wondering if shall we do use the "vendor specific"
indication bit or the "standard one" from BMSR register.
I try to figure out why SMSC put bit from this patch in the SoC...
> It would be good to describe the
> problem you see which this patch fixes.
>
> Andrew
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-04-12 11:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 13:11 [PATCH] phy: smsc: Implement .aneg_done callback for LAN8720Ai Lukasz Majewski
2023-04-06 13:48 ` Simon Horman
2023-04-06 14:19 ` Andrew Lunn
2023-04-12 11:25 ` Lukasz Majewski [this message]
2023-04-12 13:34 ` Andrew Lunn
2023-04-12 14:12 ` Lukasz Majewski
2023-04-12 13:47 ` Russell King (Oracle)
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=20230412132540.5a45564d@wsk \
--to=lukma@denx.de \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.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).