From: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
To: Qingtao Cao <qingtao.cao.au@gmail.com>
Cc: Qingtao Cao <qingtao.cao@digi.com>, Andrew Lunn <andrew@lunn.ch>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: v2 [PATCH 1/1] net: phy: marvell: avoid bringing down fibre link when autoneg is bypassed
Date: Thu, 3 Oct 2024 08:53:50 +0200 [thread overview]
Message-ID: <4f4baf9c-b9e9-4add-89d4-75f3150264b0@intel.com> (raw)
In-Reply-To: <20241003044516.373102-1-qingtao.cao@digi.com>
On 10/3/2024 6:45 AM, Qingtao Cao wrote:
> On 88E151x the SGMII autoneg bypass mode defaults to be enabled. When it is
> activated, the device assumes a link-up status with existing configuration
> in BMCR, avoid bringing down the fibre link in this case
>
> Test case:
> 1. Two 88E151x connected with SFP, both enable autoneg, link is up with speed
> 1000M
checkpatch.pl complains about this line, it exceeds 75 chars allowed for
commit msg. Please adjust.
> 2. Disable autoneg on one device and explicitly set its speed to 1000M
> 3. The fibre link can still up with this change, otherwise not.
>
> Signed-off-by: Qingtao Cao <qingtao.cao@digi.com>
> ---
> drivers/net/phy/marvell.c | 23 ++++++++++++++++++++++-
> 1 file changed, 22 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/phy/marvell.c b/drivers/net/phy/marvell.c
> index 9964bf3dea2f..e3a8ad8b08dd 100644
> --- a/drivers/net/phy/marvell.c
> +++ b/drivers/net/phy/marvell.c
> @@ -195,6 +195,10 @@
>
> #define MII_88E1510_MSCR_2 0x15
>
> +#define MII_88E1510_FSCR2 0x1a
Please use GENMASK_ULL for creating mask.
> +#define MII_88E1510_FSCR2_BYPASS_ENABLE BIT(6)
> +#define MII_88E1510_FSCR2_BYPASS_STATUS BIT(5)
> +
> #define MII_VCT5_TX_RX_MDI0_COUPLING 0x10
> #define MII_VCT5_TX_RX_MDI1_COUPLING 0x11
> #define MII_VCT5_TX_RX_MDI2_COUPLING 0x12
> @@ -1623,11 +1627,28 @@ static void fiber_lpa_mod_linkmode_lpa_t(unsigned long *advertising, u32 lpa)
> static int marvell_read_status_page_an(struct phy_device *phydev,
> int fiber, int status)
> {
> + int fscr2;
> int lpa;
> int err;
>
> if (!(status & MII_M1011_PHY_STATUS_RESOLVED)) {
> - phydev->link = 0;
> + if (!fiber) {
> + phydev->link = 0;
> + } else {
> + fscr2 = phy_read(phydev, MII_88E1510_FSCR2);
> + if (fscr2 > 0) {
> + if ((fscr2 & MII_88E1510_FSCR2_BYPASS_ENABLE) &&
> + (fscr2 & MII_88E1510_FSCR2_BYPASS_STATUS)) {
> + if (genphy_read_status_fixed(phydev) < 0)
> + phydev->link = 0;
> + } else {
> + phydev->link = 0;
> + }
> + } else {
> + phydev->link = 0;
> + }
> + }
> +
> return 0;
> }
>
So many levels of indentation... Couldn't it be merged somehow? I do not
know, maybe create local variable, store the current state of
phydev->link, then set phydev->link = 0 and restore it from local
variable only if (fiber && fscr2 > 0 && (fscr2 &
MII_88E1510_FSCR2_BYPASS_ENABLE) && (fscr2 &
MII_88E1510_FSCR2_BYPASS_STATUS) && genphy_read_status_fixed(phydev) >=0
) ...
or other way? Now you have 5 (!) levels of indentation and almost
everywhere you just set phydev->link to 0 depends on the condition.
BTW. We put "v2" inside the tag in the topic and specify the tree, so
instead of:
v2 [PATCH 1/1] net: phy: marvell: avoid bringing down fibre link when
autoneg is bypassed
it should be:
[PATCH net-next v2 1/1] net: phy: marvell: avoid bringing down fibre
link when autoneg is bypassed
next prev parent reply other threads:[~2024-10-03 6:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 4:45 Qingtao Cao
2024-10-03 6:53 ` Mateusz Polchlopek [this message]
[not found] ` <CAPcThSGqLiv-B+VUNtJoq9NsgtCWfiposknbJySkWzLJkC78dg@mail.gmail.com>
2024-10-03 7:36 ` Mateusz Polchlopek
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=4f4baf9c-b9e9-4add-89d4-75f3150264b0@intel.com \
--to=mateusz.polchlopek@intel.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qingtao.cao.au@gmail.com \
--cc=qingtao.cao@digi.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
all inboxes | Powered by JetHome®