From: Daniel Mack <daniel@zonque•org>
To: Mason <slash.tmp@free•fr>, netdev@vger•kernel.org
Cc: Florian Fainelli <f.fainelli@gmail•com>,
Mugunthan <mugunthanvnm@ti•com>,
"David S. Miller" <davem@davemloft•net>,
Matus Ujhelyi <ujhelyi.m@gmail•com>
Subject: Re: Atheros 8035 PHY only works when at803x_config_init() is commented out
Date: Thu, 09 Apr 2015 17:32:59 +0200 [thread overview]
Message-ID: <55269BAB.5020201@zonque.org> (raw)
In-Reply-To: <5526993F.1010304@free.fr>
On 04/09/2015 05:22 PM, Mason wrote:
> For the record, I dumped the PHY registers
> A) upon entering phy_init_hw
> B) before leaving phy_init_hw (thus right after at803x_config_init)
>
> IDX 1: b2 LINK STATUS, b5 AUTO-NEGOTIATION COMPLETE
> => Difference in status bits, seems reasonable
>
> IDX 5: Link partner ability (base page)
> => seems reasonable (no partner yet?)
>
> IDX 6: Auto-Negotiation Expansion
> => seems reasonable (no partner yet?)
>
> IDX 10: 1000 BASE-T Status (HW reset = SW reset = 0)
> (ALSO: Contents of this register clear after a read operation has occurred.)
> => Looks like my own read cleared it
>
> IDX 17: PHY-Specific Status
> b1 = "POLARITY (real time)"?
> => Difference in status bits, seems reasonable? (
>
> IDX 19: Interrupt Status
> => Looks like some interrupt requests might have been discarded?
>
> IDX 27: This register is undocumented
>
> Nothing looks suspicious, except maybe the Interrupt Status?
What about the debug registers, such as the one that configures the
RGMII TX/RX clock delay (4.2.25, 4.2.26). These are indirectly
addressed, see at803x_config_init().
Daniel
next prev parent reply other threads:[~2015-04-09 15:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 16:28 Atheros 8035 PHY only works when at803x_config_init() is commented out Mason
2015-04-08 17:29 ` Florian Fainelli
2015-04-08 21:37 ` Mason
2015-04-09 11:44 ` Mason
2015-04-09 13:15 ` Mason
2015-04-09 13:36 ` Daniel Mack
2015-04-09 14:38 ` Mason
2015-04-09 15:22 ` Mason
2015-04-09 15:32 ` Daniel Mack [this message]
2015-04-09 15:58 ` Mason
2015-04-09 17:25 ` Florian Fainelli
2015-04-09 18:52 ` Mason
2015-04-09 19:00 ` Florian Fainelli
2015-04-09 19:30 ` Mason
2015-04-09 20:26 ` Florian Fainelli
2015-04-09 22:10 ` Mason
2015-04-09 22:30 ` Florian Fainelli
2015-04-09 22:31 ` Fabio Estevam
2015-04-10 10:27 ` Fabio Estevam
2015-04-10 15:04 ` Mason
2015-04-10 9:33 ` Daniel Mack
2015-04-10 10:01 ` Mason
2015-04-10 10:21 ` Daniel Mack
2015-04-09 19:05 ` Mason
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=55269BAB.5020201@zonque.org \
--to=daniel@zonque$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=f.fainelli@gmail$(echo .)com \
--cc=mugunthanvnm@ti$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=slash.tmp@free$(echo .)fr \
--cc=ujhelyi.m@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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