From: Andrew Lunn <andrew@lunn.ch>
To: Ante Knezic <ante.knezic@helmholz.de>
Cc: netdev@vger.kernel.org, f.fainelli@gmail.com, olteanv@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: dsa: mv88e6xxx: Add erratum 3.14 for 88E6390X and 88E6190X
Date: Fri, 14 Jul 2023 15:28:21 +0200 [thread overview]
Message-ID: <570d32ad-e475-4a0b-a6ee-a2bdf5f67b69@lunn.ch> (raw)
In-Reply-To: <20230714114717.18921-1-ante.knezic@helmholz.de>
> +static int mv88e6390x_serdes_erratum_3_14(struct mv88e6xxx_chip *chip)
> +{
> + 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 };
Please make this const. Otherwise you end up with two copies of it.
> + int err, i;
> +
> + /* 88e6390x-88e6190x 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 = mv88e6390_serdes_write(chip, lanes[i],
> + MDIO_MMD_PHYXS,
> + 0xf054, 0x400C);
Does Marvell give this register a name? If so, please add a #define.
Are the bits in the register documented?
> + if (!err && up) {
> + if (chip->info->prod_num == MV88E6XXX_PORT_SWITCH_ID_PROD_6390X ||
> + chip->info->prod_num == MV88E6XXX_PORT_SWITCH_ID_PROD_6190X)
6191X? 6193X?
Please sort these into numerical order.
Andrew
---
pw-bot: cr
next prev parent reply other threads:[~2023-07-14 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 11:47 Ante Knezic
2023-07-14 13:28 ` Andrew Lunn [this message]
2023-07-14 14:36 ` Ante Knezic
2023-07-14 14:44 ` Andrew Lunn
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=570d32ad-e475-4a0b-a6ee-a2bdf5f67b69@lunn.ch \
--to=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=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--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®