From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] NET: add ENC28J60 driver using SPI framework
Date: Tue, 21 Sep 2010 01:52:45 -0400 [thread overview]
Message-ID: <201009210152.46272.vapier@gentoo.org> (raw)
In-Reply-To: <4C9840EA.1010600@emk-elektronik.de>
On Tuesday, September 21, 2010 01:21:46 Reinhard Meyer wrote:
> > On Monday, September 20, 2010 17:44:38 Mike Frysinger wrote:
> >> finally got around to testing this. seems like the init needs some
> >> work. if i power on the system (cold boot), boot Linux over the on-chip
> >> mac, and let Linux program the enc part, it works fine under Linux.
> >> then i do a software reset back into u-boot, it can use the enc fine
> >> too.
> >>
> >> but if i cold boot u-boot and try to use the enc part, i get:
> >> timeout waiting for CLKRDY
> >>
> >> enabling DEBUG doesnt show any additional output though.
> >
> > comparing the linux and u-boot drivers leads me to this fix:
> >
> > --- a/drivers/net/enc28j60.c
> > +++ b/drivers/net/enc28j60.c
> > @@ -632,6 +632,8 @@ static int enc_clock_wait(enc_dev_t *enc)
> >
> > {
> >
> > uint64_t etime;
> >
> > + enc_bclr(enc, CTL_REG_ECON2, ENC_ECON2_PWRSV);
> > +
> >
> > /* one second timeout */
> >
> > etime = get_ticks() + get_tbclk();
>
> The Bit PWRSV is cleared (according to data sheet) on every Reset.
> If that patch really helps in your case either the data sheet is wrong
> (for your mask of the chip) OR there is another reason while the timeout
> occurs in your case (I never had this timeout).
>
> I don't mind explicitly clearing this bit, but I suspect that this just
> covers another problem.
>
> Could you read and print ECON2 in your case and see if PWRSV is really set?
well, now i cant reproduce the issue, cold or warm booting :/. so i guess
ignore this change until i can reproduce things and get a register dump.
although, earlier i was testing when the sun was out and shining on the board
but now it's night, so maybe it's a cold-blooded part :x.
i looked at the linux driver again and i think i misread it. it isnt clearing
ECON2 at reset, just when leaving low power mode. it clears ECON1 after doing
a soft reset.
> Or, does the timeout really come to be 1 second - does get_tbclk()
> really return the timer increments per second? On many architectures
> get_tblck() simply returns CONFIG_SYS_HZ and not the number of timer
> increments per second (which can be a different and much higher value).
the Blackfin timer is just fine thanks :P. it was pausing about 1 second
between display of "enc0.18" and "CLKRDY timeout". it wasnt an instantaneous
display of the two lines.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20100921/13e03982/attachment.pgp
next prev parent reply other threads:[~2010-09-21 5:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 5:21 [U-Boot] [PATCH v3] NET: add ENC28J60 driver using SPI framework Reinhard Meyer
2010-09-21 5:52 ` Mike Frysinger [this message]
2010-09-21 6:12 ` Reinhard Meyer
2010-09-21 13:40 ` Ben Warren
-- strict thread matches above, loose matches on Subject: below --
2010-09-12 14:23 Reinhard Meyer
2010-09-13 4:21 ` Ben Warren
2010-09-20 21:44 ` Mike Frysinger
2010-09-20 23:44 ` Mike Frysinger
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=201009210152.46272.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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