[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170112010658.GA25391@lunn.ch>
Date: Thu, 12 Jan 2017 02:06:58 +0100
From: Andrew Lunn <andrew@...n.ch>
To: "Kwok, WingMan" <w-kwok2@...com>
Cc: "rmk+kernel@....linux.org.uk" <rmk+kernel@....linux.org.uk>,
"Karicheri, Muralidharan" <m-karicheri2@...com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: Marvell Phy (1510) issue since v4.7 kernel
> Hi Andrew,
>
> I double checked that ours is actually a 88E1514. According
> to Marvell's brief description, it seems that it does support
> fiber.
>
> Reading page 18 reg 30 returns 6.
O.K, that is consistent. Looking at the Marvell SDK:
phy/Include/madApiDefs.h:#define MAD_SUB_88E1510 4 /* 88E1510 */
phy/Include/madApiDefs.h:#define MAD_SUB_88E1518 5 /* 88E1518 */
phy/Include/madApiDefs.h:#define MAD_SUB_88E1512 6 /* 88E1512/88E1514 */
I took another look at the patch adding Fibre support. The
suspend/resume functions are wrong.
/* Suspend the fiber mode first */
if (!(phydev->supported & SUPPORTED_FIBRE)) {
The ! should not be there. Does removing them both fix your problem?
Andrew
Powered by blists - more mailing lists