linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Alexandre Bounine" <Alexandre.Bounine@tundra.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: TSI ethernet PHY question
Date: Wed, 23 May 2007 17:55:45 +0200	[thread overview]
Message-ID: <30282286f39c1489db7ad5b05acbc1bd@kernel.crashing.org> (raw)
In-Reply-To: <1B5F013528140F45B5C671039279CA5701BBBDE3@NANUK.pc.tundra.com>

> On power up, because this pin is pulled high by the LED, the
> TXC_RXC_DELAY mode is enabled, causing a 1.9ns delay between the clock
> and data on the GMII interface. Tsi109 could not operate properly with
> this delay. The TXC_RXC_DELAY mode has to be disabled by software.
>
> If the Quality/TXC_RXC_DELAY pin is left not connected PHY will work in
> normal mode without delay and therefore the workaround is not required.

So it is a board-specific workaround.

> I think that for situations like one on the Holly board we may need
> board-specific hooks which modify normal initialization. As in our 
> case:
> no LED - no trouble.

Should be initiated from the platform code yes; it could
be as simple as passing a flag to the init function.

> -----Original Message-----

Don't top-post :-)


Segher

  reply	other threads:[~2007-05-23 15:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23  7:03 TSI ethernet PHY question Benjamin Herrenschmidt
2007-05-23 13:43 ` Alexandre Bounine
2007-05-23 15:55   ` Segher Boessenkool [this message]
2007-05-23 22:52   ` Benjamin Herrenschmidt
2007-05-24 18:53     ` Andy Fleming
2007-05-24 22:51       ` Benjamin Herrenschmidt
2007-05-24 23:54         ` Segher Boessenkool
2007-05-25  0:01           ` Benjamin Herrenschmidt
2007-05-25  0:57             ` Segher Boessenkool
2007-05-25  1:53               ` Benjamin Herrenschmidt
2007-05-25 14:24                 ` Segher Boessenkool
2007-05-25  6:02               ` Paul Mackerras
2007-05-25 14:25                 ` Segher Boessenkool
2007-05-25  2:00           ` David Gibson
2007-05-25  7:35             ` Zang Roy-r61911
2007-05-25 14:17             ` Segher Boessenkool

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=30282286f39c1489db7ad5b05acbc1bd@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=Alexandre.Bounine@tundra.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=linuxppc-dev@ozlabs.org \
    /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).