[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230609080305.546028-1-maxime.chevallier@bootlin.com>
Date: Fri, 9 Jun 2023 10:03:03 +0200
From: Maxime Chevallier <maxime.chevallier@...tlin.com>
To: davem@...emloft.net
Cc: Maxime Chevallier <maxime.chevallier@...tlin.com>,
netdev@...r.kernel.org,
linux-kernel@...r.kernel.org,
thomas.petazzoni@...tlin.com,
Andrew Lunn <andrew@...n.ch>,
Florian Fainelli <f.fainelli@...il.com>,
Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
linux-arm-kernel@...ts.infradead.org,
Horatiu.Vultur@...rochip.com,
Allan.Nielsen@...rochip.com,
UNGLinuxDriver@...rochip.com,
Vladimir Oltean <vladimir.oltean@....com>,
Simon Horman <simon.horman@...igine.com>
Subject: [PATCH net v2 0/2] fixes for Q-USGMII speeds and autoneg
This is the second version of a small changeset for QUSGMII support,
fixing inconsistencies in reported max speed and control word parsing.
As reported here [1], there are some inconsistencies for the Q-USGMII
mode speeds and configuration. The first patch in this fixup series
makes so that we correctly report the max speed of 1Gbps for this mode.
The second patch uses a dedicated helper to decode the control word.
This is necessary as although USGMII control words are close to USXGMII,
they don't support the same speeds.
Thanks,
Maxime
[1] : https://lore.kernel.org/netdev/ZHnd+6FUO77XFJvQ@shell.armlinux.org.uk/
V1->V2: Fix decoding logic for usgmii control word, as per Russell's review
Maxime Chevallier (2):
net: phylink: report correct max speed for QUSGMII
net: phylink: use a dedicated helper to parse usgmii control word
drivers/net/phy/phylink.c | 41 +++++++++++++++++++++++++++++++++++++--
1 file changed, 39 insertions(+), 2 deletions(-)
--
2.40.1
Powered by blists - more mailing lists