From: Vladimir Oltean <olteanv@gmail.com>
To: Ante Knezic <ante.knezic@helmholz.de>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, f.fainelli@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, linux-kernel@vger.kernel.org,
Russell King <linux@armlinux.org.uk>
Subject: Re: [PATCH net-next v4] net: dsa: mv88e6xxx: Add erratum 3.14 for 88E6390X and 88E6190X
Date: Thu, 27 Jul 2023 13:46:03 +0300 [thread overview]
Message-ID: <20230727104603.mqbnfrhri6riesrx@skbuf> (raw)
In-Reply-To: <20230727082550.15254-1-ante.knezic@helmholz.de>
On Thu, Jul 27, 2023 at 10:25:50AM +0200, Ante Knezic wrote:
> Fixes XAUI/RXAUI lane alignment errors.
> Issue causes dropped packets when trying to communicate over
> fiber via SERDES lanes of port 9 and 10.
> Errata document applies only to 88E6190X and 88E6390X devices.
> Requires poking in undocumented registers.
>
> Signed-off-by: Ante Knezic <ante.knezic@helmholz.de>
> ---
> V4 : Rework as suggested by Vladimir Oltean <olteanv@gmail.com>
> and Russell King <linux@armlinux.org.uk>
> * print error in case of failure to apply erratum
> * use mdiobus_c45_write instead of mdiodev_c45_write
> * use bool variable instead of embedding a chip pointer inside
> pcs struct.
> V3 : Rework to fit the new phylink_pcs infrastructure
> V2 : Rework as suggested by Andrew Lunn <andrew@lun.ch>
> * make int lanes[] const
> * reorder prod_nums
> * update commit message to indicate we are dealing with
> undocumented Marvell registers and magic values
> ---
> drivers/net/dsa/mv88e6xxx/pcs-639x.c | 45 ++++++++++++++++++++++++++++++++++++
> 1 file changed, 45 insertions(+)
>
> diff --git a/drivers/net/dsa/mv88e6xxx/pcs-639x.c b/drivers/net/dsa/mv88e6xxx/pcs-639x.c
> index 98dd49dac421..ba373656bfe1 100644
> --- a/drivers/net/dsa/mv88e6xxx/pcs-639x.c
> +++ b/drivers/net/dsa/mv88e6xxx/pcs-639x.c
> @@ -20,6 +20,7 @@ struct mv88e639x_pcs {
> struct mdio_device mdio;
> struct phylink_pcs sgmii_pcs;
> struct phylink_pcs xg_pcs;
> + bool erratum_3_14;
> bool supports_5g;
> phy_interface_t interface;
> unsigned int irq;
> @@ -205,13 +206,53 @@ static void mv88e639x_sgmii_pcs_pre_config(struct phylink_pcs *pcs,
> mv88e639x_sgmii_pcs_control_pwr(mpcs, false);
> }
>
> +static int mv88e6390_erratum_3_14(struct mv88e639x_pcs *mpcs)
> +{
> + const int lanes[] = { MV88E6390_PORT9_LANE0, MV88E6390_PORT9_LANE1,
> + MV88E6390_PORT9_LANE2, MV88E6390_PORT9_LANE3,
> + MV88E6390_PORT10_LANE0, MV88E6390_PORT10_LANE1,
> + MV88E6390_PORT10_LANE2, MV88E6390_PORT10_LANE3 };
> + int err, i;
> +
> + /* 88e6190x and 88e6390x errata 3.14:
> + * After chip reset, SERDES reconfiguration or SERDES core
> + * Software Reset, the SERDES lanes may not be properly aligned
> + * resulting in CRC errors
> + */
> +
> + for (i = 0; i < ARRAY_SIZE(lanes); i++) {
> + err = mdiobus_c45_write(mpcs->mdio.bus, lanes[i],
> + MDIO_MMD_PHYXS,
> + 0xf054, 0x400C);
> + if (err)
> + return err;
> +
> + err = mdiobus_c45_write(mpcs->mdio.bus, lanes[i],
> + MDIO_MMD_PHYXS,
> + 0xf054, 0x4000);
> + if (err)
> + return err;
> + }
> +
> + return 0;
> +}
> +
> static int mv88e639x_sgmii_pcs_post_config(struct phylink_pcs *pcs,
> phy_interface_t interface)
> {
> struct mv88e639x_pcs *mpcs = sgmii_pcs_to_mv88e639x_pcs(pcs);
> + int err;
>
> mv88e639x_sgmii_pcs_control_pwr(mpcs, true);
>
> + if (mpcs->erratum_3_14) {
> + err = mv88e6390_erratum_3_14(mpcs);
> + if (err)
> + dev_err(mpcs->mdio.dev.parent,
> + "failed to apply erratum 3.14: %pe\n",
> + ERR_PTR(err));
> + }
> +
> return 0;
> }
>
> @@ -524,6 +565,10 @@ static int mv88e6390_pcs_init(struct mv88e6xxx_chip *chip, int port)
> mpcs->xg_pcs.ops = &mv88e6390_xg_pcs_ops;
> mpcs->xg_pcs.neg_mode = true;
>
> + if (chip->info->prod_num == MV88E6XXX_PORT_SWITCH_ID_PROD_6190X ||
> + chip->info->prod_num == MV88E6XXX_PORT_SWITCH_ID_PROD_6390X)
> + mpcs->erratum_3_14 = true;
> +
> err = mv88e639x_pcs_setup_irq(mpcs, chip, port);
> if (err)
> goto err_free;
> --
> 2.11.0
>
It's good practice that, if you had a conversation with Russell on previous
versions of the patch, to keep him CCed on newer versions of it.
next prev parent reply other threads:[~2023-07-27 10:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 8:25 Ante Knezic
2023-07-27 10:46 ` Vladimir Oltean [this message]
2023-07-31 21:00 ` Jakub Kicinski
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=20230727104603.mqbnfrhri6riesrx@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=ante.knezic@helmholz.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@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 \
/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®