From: Andrew Lunn <andrew@lunn.ch>
To: Robert Hancock <robert.hancock@calian.com>
Cc: netdev@vger.kernel.org, hkallweit1@gmail.com,
linux@armlinux.org.uk, davem@davemloft.net, kuba@kernel.org
Subject: Re: [PATCH net-next v2 2/3] net: phy: at803x: add fiber support
Date: Wed, 12 Jan 2022 01:10:40 +0100 [thread overview]
Message-ID: <Yd4cgGZ2tHzjBLqS@lunn.ch> (raw)
In-Reply-To: <20220111215504.2714643-3-robert.hancock@calian.com>
> #define AT803X_MODE_CFG_MASK 0x0F
> -#define AT803X_MODE_CFG_SGMII 0x01
> +#define AT803X_MODE_CFG_BASET_RGMII 0x00
> +#define AT803X_MODE_CFG_BASET_SGMII 0x01
> +#define AT803X_MODE_CFG_BX1000_RGMII_50 0x02
> +#define AT803X_MODE_CFG_BX1000_RGMII_75 0x03
> +#define AT803X_MODE_CFG_BX1000_CONV_50 0x04
> +#define AT803X_MODE_CFG_BX1000_CONV_75 0x05
> +#define AT803X_MODE_CFG_FX100_RGMII_50 0x06
> +#define AT803X_MODE_CFG_FX100_CONV_50 0x07
> +#define AT803X_MODE_CFG_RGMII_AUTO_MDET 0x0B
> +#define AT803X_MODE_CFG_FX100_RGMII_75 0x0E
> +#define AT803X_MODE_CFG_FX100_CONV_75 0x0F
Hi Robert
What do these _50, and _75 mean?
> #define AT803X_PSSR 0x11 /*PHY-Specific Status Register*/
> #define AT803X_PSSR_MR_AN_COMPLETE 0x0200
> @@ -283,6 +295,8 @@ struct at803x_priv {
> u16 clk_25m_mask;
> u8 smarteee_lpi_tw_1g;
> u8 smarteee_lpi_tw_100m;
> + bool is_fiber;
Is maybe is_100basefx a better name? It makes it clearer it represents
a link mode?
> + bool is_1000basex;
> struct regulator_dev *vddio_rdev;
> struct regulator_dev *vddh_rdev;
> struct regulator *vddio;
> @@ -784,7 +798,33 @@ static int at803x_probe(struct phy_device *phydev)
> return ret;
> }
>
> + if (phydev->drv->phy_id == ATH8031_PHY_ID) {
> + int ccr = phy_read(phydev, AT803X_REG_CHIP_CONFIG);
> + int mode_cfg;
> +
> + if (ccr < 0)
> + goto err;
> + mode_cfg = ccr & AT803X_MODE_CFG_MASK;
> +
> + switch (mode_cfg) {
> + case AT803X_MODE_CFG_BX1000_RGMII_50:
> + case AT803X_MODE_CFG_BX1000_RGMII_75:
> + priv->is_1000basex = true;
> + fallthrough;
> + case AT803X_MODE_CFG_FX100_RGMII_50:
> + case AT803X_MODE_CFG_FX100_RGMII_75:
> + priv->is_fiber = true;
O.K, now i'm wondering what AT803X_MODE_CFG_FX100_* actually means. I
was thinking it indicated 100BaseFX? But the fall through suggests
otherwise.
> static int at803x_config_init(struct phy_device *phydev)
> {
> + struct at803x_priv *priv = phydev->priv;
> int ret;
>
> if (phydev->drv->phy_id == ATH8031_PHY_ID) {
> - /* Some bootloaders leave the fiber page selected.
> - * Switch to the copper page, as otherwise we read
> - * the PHY capabilities from the fiber side.
> - */
> + /* Some bootloaders leave the fiber page selected.
Looks like you have a tab vs space problem with the previous patch?
Otherwise this first line should not of changed.
Andrew
next prev parent reply other threads:[~2022-01-12 0:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 21:55 [PATCH net-next v2 0/3] at803x fiber/SFP support Robert Hancock
2022-01-11 21:55 ` [PATCH net-next v2 1/3] net: phy: at803x: move page selection fix to config_init Robert Hancock
2022-01-12 3:51 ` Jakub Kicinski
2022-01-11 21:55 ` [PATCH net-next v2 2/3] net: phy: at803x: add fiber support Robert Hancock
2022-01-12 0:10 ` Andrew Lunn [this message]
2022-01-12 0:42 ` Robert Hancock
2022-01-12 19:49 ` Andrew Lunn
2022-01-12 23:56 ` Robert Hancock
2022-01-11 21:55 ` [PATCH net-next v2 3/3] net: phy: at803x: Support downstream SFP cage Robert Hancock
2022-01-12 0:14 ` Andrew Lunn
2022-01-12 0:24 ` Robert Hancock
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=Yd4cgGZ2tHzjBLqS@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=robert.hancock@calian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.