From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: "Marek Behún" <kabel@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Felix Fietkau <nbd@nbd.name>, Jakub Kicinski <kuba@kernel.org>,
John Crispin <john@phrozen.org>,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Mark Lee <Mark-MC.Lee@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Sean Wang <sean.wang@mediatek.com>
Subject: Re: [PATCH RFC 00/12] mtk_eth_soc phylink updates
Date: Mon, 11 Apr 2022 14:30:19 +0100 [thread overview]
Message-ID: <YlQta3Qu1aM4De9n@shell.armlinux.org.uk> (raw)
In-Reply-To: <Yk2k9D40QojsRhoo@shell.armlinux.org.uk>
A gentle reminder to those who either worked on or who look after
this driver to test this series and report back please.
Thanks.
On Wed, Apr 06, 2022 at 03:34:28PM +0100, Russell King (Oracle) wrote:
> Hi,
>
> This series ultimately updates mtk_eth_soc to use phylink_pcs, with some
> fixes along the way.
>
> Previous attempts to update this driver (which is now marked as legacy)
> have failed due to lack of testing. I am hoping that this time will be
> different; Marek can test RGMII modes, but not SGMII. So all that we
> know is that this patch series probably doesn't break RGMII.
>
> 1) remove unused mac_mode and sgmii flags members from structures.
> 2) remove unnecessary interpretation of speed when configuring 1000
> and 2500 Base-X
> 3) move configuration of SGMII duplex setting from mac_config() to
> link_up()
> 4) only pass in interface mode to mtk_sgmii_setup_mode_force()
> 5) move decision about which mtk_sgmii_setup_mode_*() function to call
> into mtk_sgmii.c
> 6) add a fixme comment for RGMII explaning why the call to
> mtk_gmac0_rgmii_adjust() is completely wrong - this needs to be
> addressed by someone who has the hardware and can test an appropriate
> fix. This fixme means that the driver still can't become non-legacy.
> 7) move gmac setup from mac_config() to mac_finish() - this preserves
> the order that we write to the hardware when we eventually convert to
> phylink_pcs()
> 8) move configuration of syscfg0 in SGMII/802.3z mode to mac_finish()
> for the same reasons as (7).
> 9) convert mtk_sgmii.c code structure and the mtk_sgmii structure to
> suit conversion to phylink_pcs
> 10) finally convert to phylink_pcs
>
> It would be nice to get these changes fully tested, but past experience
> has shown that for this driver, that's unfortunately very unlikely. So,
> I propose that the merging plan for this is that if there are no
> comments after three weeks to a month, I'll send this for inclusion in
> net-next.
>
> drivers/net/ethernet/mediatek/mtk_eth_soc.c | 103 +++++++++-------
> drivers/net/ethernet/mediatek/mtk_eth_soc.h | 40 +++----
> drivers/net/ethernet/mediatek/mtk_sgmii.c | 174 ++++++++++++++++------------
> 3 files changed, 185 insertions(+), 132 deletions(-)
>
> --
> RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
> FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
>
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
prev parent reply other threads:[~2022-04-11 13:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 14:34 [PATCH RFC 00/12] mtk_eth_soc phylink updates Russell King (Oracle)
2022-04-06 14:34 ` [PATCH RFC net-next 01/12] net: mtk_eth_soc: remove unused mac->mode Russell King (Oracle)
2022-04-06 14:35 ` [PATCH RFC net-next 02/12] net: mtk_eth_soc: remove unused sgmii flags Russell King (Oracle)
2022-04-06 14:35 ` [PATCH RFC net-next 03/12] net: mtk_eth_soc: add mask and update PCS speed definitions Russell King (Oracle)
2022-04-06 14:35 ` [PATCH RFC net-next 04/12] net: mtk_eth_soc: correct 802.3z speed setting Russell King (Oracle)
2022-04-06 14:35 ` [PATCH RFC net-next 05/12] net: mtk_eth_soc: correct 802.3z duplex setting Russell King
2022-04-06 14:35 ` [PATCH RFC net-next 06/12] net: mtk_eth_soc: stop passing phylink state to sgmii setup Russell King (Oracle)
2022-04-06 14:35 ` [PATCH RFC net-next 07/12] net: mtk_eth_soc: provide mtk_sgmii_config() Russell King (Oracle)
2022-04-06 14:35 ` [PATCH RFC net-next 08/12] net: mtk_eth_soc: add fixme comment for state->speed use Russell King (Oracle)
2022-04-06 14:35 ` [PATCH RFC net-next 09/12] net: mtk_eth_soc: move MAC_MCR setting to mac_finish() Russell King (Oracle)
2022-04-06 14:35 ` [PATCH RFC net-next 10/12] net: mtk_eth_soc: move restoration of SYSCFG0 " Russell King (Oracle)
2022-04-06 14:35 ` [PATCH RFC net-next 11/12] net: mtk_eth_soc: convert code structure to suit split PCS support Russell King (Oracle)
2022-04-06 14:35 ` [PATCH RFC net-next 12/12] net: mtk_eth_soc: partially convert to phylink_pcs Russell King (Oracle)
2022-04-11 13:30 ` Russell King (Oracle) [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=YlQta3Qu1aM4De9n@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=Mark-MC.Lee@mediatek.com \
--cc=davem@davemloft.net \
--cc=john@phrozen.org \
--cc=kabel@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sean.wang@mediatek.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).