[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230714143650.25818-1-ante.knezic@helmholz.de>
Date: Fri, 14 Jul 2023 16:36:50 +0200
From: Ante Knezic <ante.knezic@...mholz.de>
To: <andrew@...n.ch>
CC: <ante.knezic@...mholz.de>, <davem@...emloft.net>,
<edumazet@...gle.com>, <f.fainelli@...il.com>, <kuba@...nel.org>,
<linux-kernel@...r.kernel.org>, <netdev@...r.kernel.org>,
<olteanv@...il.com>, <pabeni@...hat.com>
Subject: Re: [PATCH net-next] net: dsa: mv88e6xxx: Add erratum 3.14 for 88E6390X and 88E6190X
>> +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.
will do.
>> + 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?
Unfortunately, no. This is one of those undocumented registers. I will
make a note of it in the commit message.
>> + 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?
Errata I have available refers only to 6190x and 6390x. Not sure about other devices.
>Please sort these into numerical order.
will do.
Powered by blists - more mailing lists