From: Segher Boessenkool <segher@kernel.crashing.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Alexandre Bounine <Alexandre.Bounine@tundra.com>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: TSI ethernet PHY question
Date: Fri, 25 May 2007 16:17:32 +0200 [thread overview]
Message-ID: <e97f5fb5861fe4177dc6b37bdc0e0244@kernel.crashing.org> (raw)
In-Reply-To: <20070525020059.GA13575@localhost.localdomain>
>> Since the specific bug we're talking about here is not a
>> problem with the PHY, but a miswiring on the board, I wouldn't
>> put a flag for the workaround in the phy node in the device
>> tree. It certainly is an option though.
>
> Uh.. something to bear in mind is that although it is a board
> miswiring, it's of a type that it will plausibly occur in other
> boards.
It is possible yes.
> IIRC, if a LED is attached to this PHY the workaround is
> necessary, or something similar.
Only if it is attached the wrong way, so it acts as a
pull-up (or was it pull-down) during chip reset.
> So there is value in having a
> particular flag for this rather than just looking at the board model.
A bit, maybe.
Segher
prev parent reply other threads:[~2007-05-25 14:17 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
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 [this message]
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=e97f5fb5861fe4177dc6b37bdc0e0244@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).