From: Troy Kisky <troy.kisky@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] mx6cuboxi: Make Ethernet functional
Date: Mon, 4 Jan 2016 15:06:27 -0700 [thread overview]
Message-ID: <568AECE3.1020004@boundarydevices.com> (raw)
In-Reply-To: <CAOMZO5AUvPWPj20RxWwg=-cZoh6g6uDSBKx1gYw9ir1uGD0-vA@mail.gmail.com>
On 1/4/2016 2:50 PM, Fabio Estevam wrote:
> Hi Troy,
>
> On Mon, Jan 4, 2016 at 6:40 PM, Troy Kisky
> <troy.kisky@boundarydevices.com> wrote:
>
>> Except for clearing bit 2 (which is undocumented), this looks just like the default
>> implementation, which you are still calling below.
>>
>> So, it looks like this subroutine can be replaced with an appropriate delay.
>> If bit 2 does matter, perhaps the default ar8035_config should be changed instead.
>
> Just realized that ar8035_config() is never called in my case, so doing:
>
> int board_phy_config(struct phy_device *phydev)
> {
> mx6_rgmii_rework(phydev);
>
> return 0;
> }
>
> , is enough here.
>
> Any idea as to why ar8035_config() is never called?
>
=> mii read 6 2
004D
=> mii read 6 3
D072
=>
Do you get a different value?
next prev parent reply other threads:[~2016-01-04 22:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 16:36 [U-Boot] [PATCH 1/2] mx6cuboxi: Fix the delay for the AR8035 PHY Fabio Estevam
2016-01-04 16:36 ` [U-Boot] [PATCH 2/2] mx6cuboxi: Make Ethernet functional Fabio Estevam
2016-01-04 19:59 ` Tom Rini
2016-01-04 20:40 ` Troy Kisky
2016-01-04 21:50 ` Fabio Estevam
2016-01-04 22:06 ` Troy Kisky [this message]
2016-01-04 22:08 ` Fabio Estevam
2016-01-04 22:10 ` Fabio Estevam
2016-01-04 22:45 ` Troy Kisky
2016-01-04 22:50 ` Fabio Estevam
2016-01-04 23:11 ` Troy Kisky
2016-01-04 23:26 ` Fabio Estevam
2016-01-04 22:30 ` Troy Kisky
2016-01-04 19:59 ` [U-Boot] [PATCH 1/2] mx6cuboxi: Fix the delay for the AR8035 PHY Tom Rini
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=568AECE3.1020004@boundarydevices.com \
--to=troy.kisky@boundarydevices.com \
--cc=u-boot@lists.denx.de \
/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