From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Revert "net: phy: delay only if reset handler is registered"
Date: Thu, 19 Nov 2015 09:13:09 +0100 [thread overview]
Message-ID: <1447920789.3204.14.camel@embedded.rocks> (raw)
In-Reply-To: <CAOMZO5AuNGPyhPipaA5J_bD7_wm5UKt16G0eJ6z0QvsLij97cA@mail.gmail.com>
On Mi, 2015-11-18 at 09:34 -0200, Fabio Estevam wrote:
> Hi J?rg,
>
> On Wed, Nov 18, 2015 at 6:44 AM, J?rg Krause
> <joerg.krause@embedded.rocks> wrote:
>
> > I think this is not the right thing to do here. It is true that the
> > AR8035 ethernet chip of the RioTboard needs the clock to be stable
> > for
> > at least 1ms before RESET can be deasserted. This why it fails, if
> > there is no MII reset function defined.
>
> In my case I am testing on a mx6sxsabresd which has two AR8031 chips.
>
> >
> > I think the right place to handle reset delays is the
> > board_eth_init().
> > The value of 15ms currently used looks to me like an arbitrary
> > value. I
> > am not sure where this value is comming from. Some chips need more,
> > some less time to delay after a reset.
> >
> > This is snippet of how I do it for a custom i.MX28-EVK-based board:
> >
> > int board_eth_init(bd_t *bis) {
> > ? cpu_eth_init(bis);
> > ? /* Power-on FEC */
> > ? gpio_direction_output(MX28_PAD_LCD_D21__GPIO_1_21, 0);
> > ? /* Reset FEC PHY */
> > ? gpio_direction_output(MX28_PAD_ENET0_RX_CLK__GPIO_4_13, 0);
> > ? /* Deassert nRST after 25 ms from power-up on (= t_purstd) */
> > ? udelay(25000);
> > ? gpio_set_value(MX28_PAD_ENET0_RX_CLK__GPIO_4_13, 1);
> > ? fecmxc_initialize_multi(bis, 0, 0, MXS_ENET0_BASE);
> > }
>
> We currently reset the Ethernet PHY inside setup_fec() inside
> board_eth_init().
>
> Please check board/freescale/mx6sxsabresd/mx6sxsabresd.c.
Ok, I checked. This is what happens in?setup_fec():
1) Enable AR8031 power
2) Assert AR8031 RESET
3) Delay 0.5ms
4) Deassert AR8031 RESET
5) Enable anatop clock
Shouldn't the clock be enabled and become stable before deasserting the
RESET line?
> I have also tried increasing the reset time and still do not have
> Ethernel functional.
The AR8031 datasheets recommands a delay of 10ms.
Best regards
J?rg Krause
next prev parent reply other threads:[~2015-11-19 8:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 16:25 [U-Boot] [PATCH] Revert "net: phy: delay only if reset handler is registered" Fabio Estevam
2015-11-18 5:54 ` Stefan Roese
2015-11-18 11:30 ` Fabio Estevam
2015-11-18 8:44 ` Jörg Krause
2015-11-18 11:34 ` Fabio Estevam
2015-11-19 8:13 ` Jörg Krause [this message]
2015-11-20 20:37 ` Fabio Estevam
2015-11-23 18:16 ` Fabio Estevam
2015-11-23 20:08 ` Jörg Krause
2015-12-23 15:42 ` Fabio Estevam
2016-01-04 11:19 ` Fabio Estevam
2016-01-04 12:49 ` Jörg Krause
2016-01-04 12:57 ` Fabio Estevam
2016-01-04 13:48 ` Jörg Krause
2016-01-04 14:24 ` Fabio Estevam
2016-01-04 18:35 ` Joe Hershberger
2016-01-04 18:37 ` Fabio Estevam
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=1447920789.3204.14.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--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