From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>, Madalin Bucur <madalin.bucur@oss.nxp.com>
Cc: davem@davemloft.net, f.fainelli@gmail.com, hkallweit1@gmail.com,
netdev@vger.kernel.org, ykaukab@suse.de
Subject: Re: FWD: [PATCH v2 0/2] net: phy: aquantia: indicate rate adaptation
Date: Mon, 27 Jan 2020 16:16:18 +0000 [thread overview]
Message-ID: <20200127161618.GY25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <20200127151351.GG13647@lunn.ch>
Andrew, thanks for the heads up.
Madalin, please resend this series, copying me with these patches, so
Andrew doesn't have to keep alerting me to your patches. Thanks.
On Mon, Jan 27, 2020 at 04:13:51PM +0100, Andrew Lunn wrote:
> ----- Forwarded message from Madalin Bucur <madalin.bucur@oss.nxp.com> -----
>
> Date: Mon, 27 Jan 2020 17:07:49 +0200
> From: Madalin Bucur <madalin.bucur@oss.nxp.com>
> To: davem@davemloft.net
> Cc: andrew@lunn.ch, f.fainelli@gmail.com, hkallweit1@gmail.com, netdev@vger.kernel.org, ykaukab@suse.de, Madalin
> Bucur <madalin.bucur@oss.nxp.com>
> Subject: [PATCH v2 0/2] net: phy: aquantia: indicate rate adaptation
> X-Spam-Status: No, score=-6.9 required=4.0 tests=BAYES_00,
> HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI,
> RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no
> version=3.4.4-rc1
>
> Changes since v1:
> rewrote commit messages to evidentiate that this is a PHY
> generic feature, not a particular feature of the Aquantia
> PHYs and added more details on how the 1G link issue this
> is circumventing came about.
>
> This patch-set introduces a bit into the phy_device
> structure to indicate the PHYs ability to do rate
> adaptation between the system and line interfaces and
> sets this bit for the Aquantia PHYs that have this feature.
>
> By taking into account the presence of the said bit, address
> an issue with the LS1046ARDB board 10G interface no longer
> working with an 1G link partner after autonegotiation support
> was added for the Aquantia PHY on board in
>
> commit 09c4c57f7bc4 ("net: phy: aquantia: add support for auto-negotiation configuration")
>
> Before this commit the values advertised by the PHY were not
> influenced by the dpaa_eth driver removal of system-side unsupported
> modes as the aqr_config_aneg() was basically a no-op. After this
> commit, the modes removed by the dpaa_eth driver were no longer
> advertised thus autonegotiation with 1G link partners failed.
>
> Madalin Bucur (2):
> net: phy: aquantia: add rate_adaptation indication
> dpaa_eth: support all modes with rate adapting PHYs
>
> drivers/net/ethernet/freescale/dpaa/dpaa_eth.c | 10 +++++++---
> drivers/net/phy/aquantia_main.c | 3 +++
> include/linux/phy.h | 3 +++
> 3 files changed, 13 insertions(+), 3 deletions(-)
>
> --
> 2.1.0
>
>
> ----- End forwarded message -----
>
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
parent reply other threads:[~2020-01-27 16:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20200127151351.GG13647@lunn.ch>]
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=20200127161618.GY25745@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=madalin.bucur@oss.nxp.com \
--cc=netdev@vger.kernel.org \
--cc=ykaukab@suse.de \
/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).