All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Pavel.Parkhomenko@baikalelectronics.ru
Cc: michael@stapelberg.de, afleming@gmail.com, f.fainelli@gmail.com,
	Alexey.Malahov@baikalelectronics.ru,
	Sergey.Semin@baikalelectronics.ru, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: phy: marvell: Fix RGMII Tx/Rx delays setting in 88e1121-compatible PHYs
Date: Fri, 4 Feb 2022 14:10:32 +0100	[thread overview]
Message-ID: <Yf0lyGi+2mEwmrEH@lunn.ch> (raw)
In-Reply-To: <96759fee7240fd095cb9cc1f6eaf2d9113b57cf0.camel@baikalelectronics.ru>

On Fri, Feb 04, 2022 at 05:29:11AM +0000, Pavel.Parkhomenko@baikalelectronics.ru wrote:
> It is mandatory for a software to issue a reset upon modifying RGMII
> Receive Timing Control and RGMII Transmit Timing Control bit fields of MAC
> Specific Control register 2 (page 2, register 21) otherwise the changes
> won't be perceived by the PHY (the same is applicable for a lot of other
> registers). Not setting the RGMII delays on the platforms that imply
> it's being done on the PHY side will consequently cause the traffic loss.
> We discovered that the denoted soft-reset is missing in the
> m88e1121_config_aneg() method for the case if the RGMII delays are
> modified but the MDIx polarity isn't changed or the auto-negotiation is
> left enabled, thus causing the traffic loss on our platform with Marvell
> Alaska 88E1510 installed. Let's fix that by issuing the soft-reset if the
> delays have been actually set in the m88e1121_config_aneg_rgmii_delays()
> method.

Hi Pavel

There appears to be another path which has the same issue.

m88e1118_config_aneg() calls marvell_set_polarity(), which also needs
a reset afterwards.

Could you fix this case as well?

Thanks
	Andrew

  parent reply	other threads:[~2022-02-04 13:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-04  5:29 [PATCH] net: phy: marvell: Fix RGMII Tx/Rx delays setting in 88e1121-compatible PHYs Pavel.Parkhomenko
2022-02-04  9:56 ` Serge Semin
2022-02-04 10:41   ` Russell King (Oracle)
2022-02-04 13:10 ` Andrew Lunn [this message]
2022-02-05 15:22   ` Pavel.Parkhomenko
2022-02-05 16:25     ` Andrew Lunn
2022-02-05  4:02 ` Jakub Kicinski
2022-02-05 19:08 ` [PATCH net v2] " Pavel Parkhomenko
2022-02-05 19:27   ` Serge Semin
2022-02-05 20:39 ` Pavel Parkhomenko
2022-02-07 17:40   ` Jakub Kicinski
2022-02-07 18:33     ` Serge Semin
2022-02-07 19:22       ` Jakub Kicinski
2022-02-08  3:58         ` Jakub Kicinski
2022-02-08  4:10   ` patchwork-bot+netdevbpf

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=Yf0lyGi+2mEwmrEH@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=Alexey.Malahov@baikalelectronics.ru \
    --cc=Pavel.Parkhomenko@baikalelectronics.ru \
    --cc=Sergey.Semin@baikalelectronics.ru \
    --cc=afleming@gmail.com \
    --cc=f.fainelli@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@stapelberg.de \
    --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 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.