From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Corentin Labbe <clabbe.montjoie@gmail.com>,
linus.walleij@linaro.org, ulli.kroll@googlemail.com,
kuba@kernel.org, davem@davemloft.net, hkallweit1@gmail.com,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: net: phy: marvell: network working with generic PHY and not with marvell PHY
Date: Tue, 4 Jan 2022 14:57:33 +0000 [thread overview]
Message-ID: <YdRgXbpK6CFB/eCU@shell.armlinux.org.uk> (raw)
In-Reply-To: <YdRdu3jFPnGd1DsH@lunn.ch>
On Tue, Jan 04, 2022 at 03:46:19PM +0100, Andrew Lunn wrote:
> > @@ -1227,16 +1227,18 @@ static int m88e1118_config_init(struct phy_device *phydev)
> > {
> > int err;
> >
> > - /* Change address */
> > - err = marvell_set_page(phydev, MII_MARVELL_MSCR_PAGE);
> > - if (err < 0)
> > - return err;
> > -
> > /* Enable 1000 Mbit */
> > - err = phy_write(phydev, 0x15, 0x1070);
> > + err = phy_write_paged(phydev, MII_MARVELL_MSCR_PAGE,
> > + MII_88E1121_PHY_MSCR_REG, 0x1070);
>
> Ah, yes, keeping this makes it more backwards compatible.
>
> It would be nice to replace the 0x1070 with #defines.
>
> We already have:
>
> #define MII_88E1121_PHY_MSCR_RX_DELAY BIT(5)
> #define MII_88E1121_PHY_MSCR_TX_DELAY BIT(4)
> #define MII_88E1121_PHY_MSCR_DELAY_MASK (BIT(5) | BIT(4))
>
> Bits 6 is the MSB of the default MAC speed.
> Bit 13 is the LSB of the default MAC speed. These two should default to 10b = 1000Mbps
> Bit 12 is reserved, and should be written 1.
Hmm, seems odd that these speed bits match BMCR, and I'm not sure why
the default MAC speed would have any bearing on whether gigabit mode
is enabled. If they default to 10b, then the write should have no effect
unless boot firmware has changed them.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2022-01-04 14:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 10:58 net: phy: marvell: network working with generic PHY and not with marvell PHY Corentin Labbe
2022-01-04 11:14 ` Russell King (Oracle)
2022-01-04 11:33 ` Corentin Labbe
2022-01-04 11:41 ` Russell King (Oracle)
2022-01-04 12:09 ` Corentin Labbe
2022-01-04 12:17 ` Russell King (Oracle)
2022-01-04 12:11 ` Russell King (Oracle)
2022-01-04 13:57 ` Corentin Labbe
2022-01-04 14:11 ` Corentin Labbe
2022-01-04 14:27 ` Russell King (Oracle)
2022-01-04 14:46 ` Andrew Lunn
2022-01-04 14:57 ` Russell King (Oracle) [this message]
2022-01-04 15:02 ` Andrew Lunn
2022-01-04 15:04 ` Corentin Labbe
2022-01-04 14:36 ` Andrew Lunn
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=YdRgXbpK6CFB/eCU@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=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ulli.kroll@googlemail.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).