From: Andrew Lunn <andrew@lunn.ch>
To: "Kwok, WingMan" <w-kwok2@ti.com>
Cc: "rmk+kernel@arm.linux.org.uk" <rmk+kernel@arm.linux.org.uk>,
"charles-antoine.couret@nexvision.fr"
<charles-antoine.couret@nexvision.fr>,
"Karicheri, Muralidharan" <m-karicheri2@ti.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Marvell Phy (1510) issue since v4.7 kernel
Date: Wed, 11 Jan 2017 23:59:48 +0100 [thread overview]
Message-ID: <20170111225948.GH13033@lunn.ch> (raw)
In-Reply-To: <230CBA6E4B6B6B418E8730AC28E6FC7E15354AE5@DFLE11.ent.ti.com>
> 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
next prev parent reply other threads:[~2017-01-11 22:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 22:38 Marvell Phy (1510) issue since v4.7 kernel Murali Karicheri
2017-01-09 22:56 ` Andrew Lunn
2017-01-09 23:48 ` Kwok, WingMan
2017-01-09 23:55 ` Andrew Lunn
2017-01-10 1:37 ` Kwok, WingMan
2017-01-10 1:53 ` Andrew Lunn
2017-01-11 22:18 ` Kwok, WingMan
2017-01-11 22:27 ` Andrew Lunn
2017-01-11 22:32 ` Kwok, WingMan
2017-01-11 22:41 ` Kwok, WingMan
2017-01-11 22:59 ` Andrew Lunn [this message]
2017-01-11 23:09 ` Kwok, WingMan
2017-01-11 23:22 ` Andrew Lunn
2017-01-12 0:31 ` Kwok, WingMan
2017-01-12 1:06 ` Andrew Lunn
2017-01-12 21:31 ` Kwok, WingMan
2017-01-12 21:41 ` Russell King - ARM Linux
2017-01-12 22:40 ` Kwok, WingMan
2017-01-12 21:49 ` Andrew Lunn
2017-01-12 22:31 ` Russell King - ARM Linux
2017-01-12 22:49 ` Kwok, WingMan
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=20170111225948.GH13033@lunn.ch \
--to=andrew@lunn.ch \
--cc=charles-antoine.couret@nexvision.fr \
--cc=m-karicheri2@ti.com \
--cc=netdev@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=w-kwok2@ti.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;
as well as URLs for NNTP newsgroup(s).