From: Mason <slash.tmp@free.fr>
To: Daniel Mack <daniel@zonque.org>, 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:58:52 +0200 [thread overview]
Message-ID: <5526A1BC.5060609@free.fr> (raw)
In-Reply-To: <55269BAB.5020201@zonque.org>
On 09/04/2015 17:32, Daniel Mack wrote:
> 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().
My dump code:
void mydump(struct phy_device *phydev, int *foo, int *bar)
{
int i;
for (i = 0; i < 32; ++i) foo[i] = phy_read(phydev, i);
for (i = 0; i < 20; ++i) {
phy_write(phydev, 0x1d, i);
mdelay(1);
bar[i] = phy_read(phydev, 0x1e);
}
}
[ 0.738528] IDX=0x01 796d != 7949
[ 0.741860] IDX=0x05 c1e1 != 0000
[ 0.745191] IDX=0x06 000f != 0004
[ 0.748521] IDX=0x0a 3800 != 0000
[ 0.751851] IDX=0x11 bc10 != 0012
[ 0.755182] IDX=0x13 7400 != 0000
[ 0.758513] IDX=0x1b 060e != 0600
[ 0.761842] DEBUG REGS
[ 0.764211] IDX=0x01 ffd0 != 0032
[ 0.767542] IDX=0x02 3f0f != 3110
[ 0.770872] IDX=0x03 3fff != 3f00
[ 0.774203] IDX=0x0c 0800 != 1801
[ 0.777533] IDX=0x0d 0100 != 0000
[ 0.780863] IDX=0x0e 0023 != 0040
Differences in debug registers only occur in undocumented registers.
(Only 0x00, 0x05, 0x10, 0x11, 0x12 are documented.)
Regards.
next prev parent reply other threads:[~2015-04-09 15:59 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
2015-04-09 15:58 ` Mason [this message]
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=5526A1BC.5060609@free.fr \
--to=slash.tmp@free.fr \
--cc=daniel@zonque.org \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=mugunthanvnm@ti.com \
--cc=netdev@vger.kernel.org \
--cc=ujhelyi.m@gmail.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).