From: Jakub Kicinski <kuba@kernel.org>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: davem@davemloft.net, Rob Herring <robh+dt@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, thomas.petazzoni@bootlin.com,
Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org,
Richard Cochran <richardcochran@gmail.com>,
Horatiu.Vultur@microchip.com, Allan.Nielsen@microchip.com,
UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net-next v4 0/4] net: Introduce QUSGMII phy mode
Date: Mon, 1 Aug 2022 20:21:29 -0700 [thread overview]
Message-ID: <20220801202129.17174b5f@kernel.org> (raw)
In-Reply-To: <20220801073713.32290-1-maxime.chevallier@bootlin.com>
On Mon, 1 Aug 2022 09:37:09 +0200 Maxime Chevallier wrote:
> This is the V4 of a previous series [1] initially aimed at introducing
> inband extensions, with modes like QUSGMII. This mode allows passing
> info in the ethernet preamble between the MAC and the PHY, such s
> timestamps.
>
> This series has now become a preliminary series, that simply introduces
> the new interface mode, without support for inband extensions, that will
> come later.
>
> The reasonning is that work will need to be done in the networking
> subsystem, but also in the generic phy driver subsystem to allow serdes
> configuration for qusgmii.
>
> This series add the mode, the relevant binding changes, adds support for
> it in the lan966x driver, and also introduces a small helper to get the
> number of links a given phy mode can carry (think 1 for SGMII and 4 for
> QSGMII). This allows for better readability and will prove useful
> when (if) we support PSGMII (5 links on 1 interface) and OUSGMII (8
> links on one interface).
>
> V4 contains no change but the collected Reviewed-by from Andrew.
This series came in after the closing of net-next:
https://lore.kernel.org/all/20220731212214.1c733186@kernel.org/
let's defer it until after the merge window.
prev parent reply other threads:[~2022-08-02 3:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 7:37 [PATCH net-next v4 0/4] net: Introduce QUSGMII phy mode Maxime Chevallier
2022-08-01 7:37 ` [PATCH net-next v4 1/4] net: phy: Introduce QUSGMII PHY mode Maxime Chevallier
2022-08-01 7:37 ` [PATCH net-next v4 2/4] dt-bindings: net: ethernet-controller: add QUSGMII mode Maxime Chevallier
2022-08-01 7:37 ` [PATCH net-next v4 3/4] net: phy: Add helper to derive the number of ports from a phy mode Maxime Chevallier
2022-08-01 7:37 ` [PATCH net-next v4 4/4] net: lan966x: Add QUSGMII support for lan966x Maxime Chevallier
2022-08-02 3:21 ` Jakub Kicinski [this message]
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=20220801202129.17174b5f@kernel.org \
--to=kuba@kernel.org \
--cc=Allan.Nielsen@microchip.com \
--cc=Horatiu.Vultur@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.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).