From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: "Marek Behún" <marek.behun@nic.cz>
Cc: Andrew Lunn <andrew@lunn.ch>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Baruch Siach <baruch@tkos.co.il>, Chris Healy <cphealy@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH RFC russell-king 2/4] net: phy: sfp: add support for multigig RollBall modules
Date: Tue, 11 Aug 2020 16:15:53 +0100 [thread overview]
Message-ID: <20200811151552.GM1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <20200810220645.19326-3-marek.behun@nic.cz>
On Tue, Aug 11, 2020 at 12:06:43AM +0200, Marek Behún wrote:
> This adds support for multigig copper SFP modules from RollBall/Hilink.
> These modules have a specific way to access clause 45 registers of the
> internal PHY.
>
> We also need to wait at least 25 seconds after deasserting TX disable
> before accessing the PHY. The code waits for 30 seconds just to be sure.
I wonder why it takes so long - the 88x3310 boots very quickly.
> +static int sfp_i2c_mii_probe(struct sfp *sfp)
> +{
> + struct mii_bus *i2c_mii;
> + int ret;
> +
> + if (sfp->rollball_mii)
> + i2c_mii = mdio_i2c_rollball_alloc(sfp->dev, sfp->i2c);
> + else
> + i2c_mii = mdio_i2c_alloc(sfp->dev, sfp->i2c);
> +
I think I'd prefer to find a way to teach the existing mdio_i2c code
about different protocols rather than having a load of different buses
that we have to select between. Maybe we can do that via the PHY
address, or maybe we should have a call into mdio_i2c that tells it
which protocol should be used?
The reason I don't like this approach is it seems to me to be very
heavy handed... using a sledge hammer to crack a nut.
> + rollball = (!memcmp(id.base.vendor_name, "OEM ", 16) &&
> + (!memcmp(id.base.vendor_pn, "SFP-10G-T ", 16) ||
> + !memcmp(id.base.vendor_pn, "RTSFP-10 ", 16) ||
> + !memcmp(id.base.vendor_pn, "RTSFP-2.5G ", 16)));
> + if (rollball) {
> + /* TODO: try to write this to EEPROM */
> + id.base.extended_cc = SFF8024_ECC_10GBASE_T_SFI;
Should we really be "fixing" vendors EEPROMs for 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:[~2020-08-11 15:15 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 22:06 [PATCH RFC russell-king 0/4] Support for RollBall 10G copper SFP modules Marek Behún
2020-08-10 22:06 ` [PATCH RFC russell-king 1/4] net: phy: add I2C mdio bus for RollBall compatible SFPs Marek Behún
2020-08-10 22:06 ` [PATCH RFC russell-king 2/4] net: phy: sfp: add support for multigig RollBall modules Marek Behún
2020-08-11 15:15 ` Russell King - ARM Linux admin [this message]
2020-08-12 13:33 ` Marek Behún
2020-08-12 14:33 ` Russell King - ARM Linux admin
2020-08-12 14:42 ` Marek Behún
2020-08-10 22:06 ` [PATCH RFC russell-king 3/4] net: phy: marvell10g: change MACTYPE according to phydev->interface Marek Behún
2020-08-11 15:21 ` Russell King - ARM Linux admin
2020-08-12 14:44 ` Marek Behún
2020-08-12 15:00 ` Russell King - ARM Linux admin
2020-08-12 15:37 ` Marek Behún
2020-08-12 15:48 ` Russell King - ARM Linux admin
2020-08-12 15:59 ` Marek Behún
2020-08-12 16:13 ` Marek Behún
2020-08-12 16:22 ` Russell King - ARM Linux admin
2020-08-12 16:28 ` Marek Behún
2020-08-12 16:30 ` Russell King - ARM Linux admin
2020-08-12 16:01 ` Russell King - ARM Linux admin
2020-08-12 16:15 ` Marek Behún
2020-08-12 15:44 ` Andrew Lunn
2020-08-12 15:54 ` Russell King - ARM Linux admin
2020-08-18 17:28 ` Marek Behún
2020-08-10 22:06 ` [PATCH RFC russell-king 4/4] net: phylink: don't fail attaching phy on 1000base-x/2500base-x mode Marek Behún
2020-08-11 15:08 ` [PATCH RFC russell-king 0/4] Support for RollBall 10G copper SFP modules Russell King - ARM Linux admin
2020-08-12 12:31 ` Marek Behún
2020-08-12 12:31 ` Marek Behún
2020-08-12 14:20 ` Marek Behún
2020-08-17 13:49 ` Russell King - ARM Linux admin
2020-08-18 13:43 ` Marek Behún
2020-08-18 15:08 ` Russell King - ARM Linux admin
2020-08-18 15:30 ` Marek Behún
2020-08-18 15:36 ` Russell King - ARM Linux admin
2020-08-18 15:47 ` Marek Behún
2020-08-18 16:34 ` Russell King - ARM Linux admin
2020-08-19 15:49 ` Marek Behún
2020-08-19 15:54 ` Marek Behún
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=20200811151552.GM1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=baruch@tkos.co.il \
--cc=cphealy@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=marek.behun@nic.cz \
--cc=maxime.chevallier@bootlin.com \
--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).