[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170111225948.GH13033@lunn.ch>
Date: Wed, 11 Jan 2017 23:59:48 +0100
From: Andrew Lunn <andrew@...n.ch>
To: "Kwok, WingMan" <w-kwok2@...com>
Cc: "rmk+kernel@....linux.org.uk" <rmk+kernel@....linux.org.uk>,
"charles-antoine.couret@...vision.fr"
<charles-antoine.couret@...vision.fr>,
"Karicheri, Muralidharan" <m-karicheri2@...com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: Marvell Phy (1510) issue since v4.7 kernel
> looping in Charles-Antoine (author of patch
> with commit id 6cfb3bcc)
>
> Charles-Antoine,
>
> Do you have the ID of Marvell PHY 88E1512?
I suspect that is the wrong question to ask.
The Marvell driver is being loaded, so it must be using on of the IDs
in the driver. There is no ID in the driver specifically for the
88E1512. It seems like the 88E1512 uses the 88E1510 ID.
So i think the correct question should be, how can we tell the 88E1512
from the 88E1510 if they have the same ID in register 3.
It appears that for the 88E1512, page 0 are the copper registers and
page 1 is the fibre registers. Maybe the 88E1512 has an ID in page 1
register 3? Maybe the 88E1510 does not have an ID in page 1 register
3?
Andrew
Powered by blists - more mailing lists