From: Felix Radensky <felix@embedded-sol.com>
To: Timur Tabi <timur@freescale.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: Connecting SGMII PHY to eTSEC1 on P1022
Date: Thu, 23 Jun 2011 23:43:03 +0300 [thread overview]
Message-ID: <4E03A557.2010008@embedded-sol.com> (raw)
In-Reply-To: <4E02229B.50707@embedded-sol.com>
Hi,
On 06/22/2011 08:12 PM, Felix Radensky wrote:
> Hi Timur,
>
> On 06/22/2011 07:18 PM, Timur Tabi wrote:
>> Felix Radensky wrote:
>>> What am I doing wrong ?
>> Can you debug the PHY driver to see if it's getting called and
>> trying to talk to
>> the PHY itself?
>>
> I'll do that tomorrow and report back.
I've found the problem by looking at the code. My SGMII PHY is Marvell
88E1112.
Marvell PHY driver claims it supports that PHY, but in reality it
doesn't. It uses
routines initially written for 88E1111 to configure 88E1112,
essentially writing
to registers that do not exist on that PHY. After disabling Marvell
PHY driver my
PHY started working.
Felix.
prev parent reply other threads:[~2011-06-23 20:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 15:58 Connecting SGMII PHY to eTSEC1 on P1022 Felix Radensky
2011-06-22 16:18 ` Timur Tabi
2011-06-22 17:12 ` Felix Radensky
2011-06-23 20:43 ` Felix Radensky [this message]
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=4E03A557.2010008@embedded-sol.com \
--to=felix@embedded-sol.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=timur@freescale.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).