From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Corentin Labbe <clabbe.montjoie@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org
Subject: [PATCH net-next 0/2] Fix RGMII delays for 88E1118
Date: Tue, 4 Jan 2022 16:37:21 +0000 [thread overview]
Message-ID: <YdR3wYFkm4eJApwb@shell.armlinux.org.uk> (raw)
Hi,
This series fixes the RGMII delays for 88E1118 Marvell PHYs, after a
report by Corentin Labbe that the Marvell driver fails to work.
Patch 1 cleans up the paged register accesses in m88e1118_config_init()
and patch 2 adds the RGMII delay configuration.
This comes with an element of risk as existing DT may need to be fixed
for this in a similar way as we have done in the recent past for other
PHY drivers that have misinterpreted the RGMII interface modes.
drivers/net/phy/marvell.c | 26 +++++++++++++-------------
1 file changed, 13 insertions(+), 13 deletions(-)
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next reply other threads:[~2022-01-04 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 16:37 Russell King (Oracle) [this message]
2022-01-04 16:38 ` [PATCH net-next 1/2] net: phy: marvell: use phy_write_paged() to set MSCR Russell King (Oracle)
2022-01-04 16:44 ` Andrew Lunn
2022-01-04 19:53 ` Corentin Labbe
2022-01-04 16:38 ` [PATCH net-next 2/2] net: phy: marvell: configure RGMII delays for 88E1118 Russell King (Oracle)
2022-01-04 16:45 ` Andrew Lunn
2022-01-05 18:40 ` [PATCH net-next 0/2] Fix " 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=YdR3wYFkm4eJApwb@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=clabbe.montjoie@gmail.com \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/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).