From: Andrew Lunn <andrew@lunn.ch>
To: Claudiu Manoil <claudiu.manoil@nxp.com>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Ondrej Spacek <ondrej.spacek@nxp.com>
Subject: Re: [PATCH, net] phy: aquantia: Fix AN when higher speeds than 1G are not advertised
Date: Sun, 12 Jun 2022 23:25:07 +0200 [thread overview]
Message-ID: <YqZZs7EAcAFpQpXU@lunn.ch> (raw)
In-Reply-To: <AM9PR04MB8397DE1463E47F5AF8574A5F96A89@AM9PR04MB8397.eurprd04.prod.outlook.com>
> I understand the situation is not ideal. What I could do is to provide some
> logs showing that writing the correct configuration to 7.20h does not yield
> the desired result, to have some sort of detailed evidence about the issue.
> But I cannot do that until Tuesday at the earliest.
> As for documentation, there's an App Note about configuring advertising
> via the vendor specific 0xC400 reg but I don't think it's public. Not sure if
> we can use that.
> Meanwhile, it would be great if you or someone else could confirm the
> issue on a different platform.
I don't have any boards with these PHYs.
If there is a vendor document saying it has to be configured via
vendor registers, thats enough for me. But should the generic code be
removed, are those bits documented as reserved?
Andrew
next prev parent reply other threads:[~2022-06-12 21:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 8:40 [PATCH, net] phy: aquantia: Fix AN when higher speeds than 1G are not advertised Claudiu Manoil
2022-06-11 14:59 ` Andrew Lunn
2022-06-11 18:13 ` Claudiu Manoil
2022-06-11 23:20 ` Andrew Lunn
2022-06-12 18:47 ` Claudiu Manoil
2022-06-12 21:25 ` Andrew Lunn [this message]
2022-06-14 14:08 ` Claudiu Manoil
2022-06-17 4:00 ` patchwork-bot+netdevbpf
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=YqZZs7EAcAFpQpXU@lunn.ch \
--to=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=ondrej.spacek@nxp.com \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.