From: Florian Fainelli <f.fainelli@gmail.com>
To: Robert Hancock <robert.hancock@calian.com>,
andrew@lunn.ch, hkallweit1@gmail.com, davem@davemloft.net,
kuba@kernel.org
Cc: f.fainelli@gmail.com, linux@armlinux.org.uk,
bcm-kernel-feedback-list@broadcom.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] net: phy: broadcom: Set proper 1000BaseX/SGMII interface mode for BCM54616S
Date: Fri, 12 Feb 2021 17:26:02 -0800 [thread overview]
Message-ID: <87f06cb4-3bee-3ccb-bb21-ce6943e75336@gmail.com> (raw)
In-Reply-To: <20210213002825.2557444-2-robert.hancock@calian.com>
On 2/12/2021 4:28 PM, 'Robert Hancock' via BCM-KERNEL-FEEDBACK-LIST,PDL
wrote:
> The default configuration for the BCM54616S PHY may not match the desired
> mode when using 1000BaseX or SGMII interface modes, such as when it is on
> an SFP module. Add code to explicitly set the correct mode using
> programming sequences provided by Bel-Fuse:
>
> https://www.belfuse.com/resources/datasheets/powersolutions/ds-bps-sfp-1gbt-05-series.pdf
> https://www.belfuse.com/resources/datasheets/powersolutions/ds-bps-sfp-1gbt-06-series.pdf
>
> Signed-off-by: Robert Hancock <robert.hancock@calian.com>
> ---
> drivers/net/phy/broadcom.c | 83 ++++++++++++++++++++++++++++++++------
> include/linux/brcmphy.h | 4 ++
> 2 files changed, 75 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/net/phy/broadcom.c b/drivers/net/phy/broadcom.c
> index 0472b3470c59..78542580f2b2 100644
> --- a/drivers/net/phy/broadcom.c
> +++ b/drivers/net/phy/broadcom.c
> @@ -64,6 +64,63 @@ static int bcm54612e_config_init(struct phy_device *phydev)
> return 0;
> }
>
> +static int bcm54616s_config_init(struct phy_device *phydev)
> +{
> + int rc, val;
> +
> + if (phydev->interface == PHY_INTERFACE_MODE_SGMII ||
> + phydev->interface == PHY_INTERFACE_MODE_1000BASEX) {
Can you reverse the condition so as to save a level of identation?
> + /* Ensure proper interface mode is selected. */
> + /* Disable RGMII mode */
> + val = bcm54xx_auxctl_read(phydev, MII_BCM54XX_AUXCTL_SHDWSEL_MISC);
> + if (val < 0)
> + return val;
> + val &= ~MII_BCM54XX_AUXCTL_SHDWSEL_MISC_RGMII_EN;
> + rc = bcm54xx_auxctl_write(phydev, MII_BCM54XX_AUXCTL_SHDWSEL_MISC,
> + val);
> + if (rc < 0)
> + return rc;
I don't think this write is making it through since you are not setting
MII_BCM54XX_AUXCTL_MISC_WREN in val, I know this is an annoying detail,
and we could probably fold that to be within bcm54xx_auxctl_write()
directly, similarly to what bcm_phy_write_shadow() does.
The reset of the sequence and changes looks fine to me.
--
Florian
next prev parent reply other threads:[~2021-02-13 1:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-13 0:28 [PATCH net-next 0/2] Broadcom PHY driver updates Robert Hancock
2021-02-13 0:28 ` [PATCH net-next 1/2] net: phy: broadcom: Set proper 1000BaseX/SGMII interface mode for BCM54616S Robert Hancock
2021-02-13 1:26 ` Florian Fainelli [this message]
2021-02-13 1:45 ` Robert Hancock
2021-02-13 2:55 ` Florian Fainelli
2021-02-13 0:28 ` [PATCH net-next 2/2] net: phy: broadcom: Do not modify LED configuration for SFP module PHYs Robert Hancock
2021-02-13 1:17 ` Florian Fainelli
2021-02-13 1:41 ` Vladimir Oltean
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=87f06cb4-3bee-3ccb-bb21-ce6943e75336@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--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 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).