From: Peter Tyser <ptyser@xes-inc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] revert "tsec: Force TBI PHY to 1000Mbps fullduplex in SGMII mode"
Date: Fri, 19 Nov 2010 18:01:43 -0600 [thread overview]
Message-ID: <1290211303.20072.120.camel@petert> (raw)
In-Reply-To: <AANLkTik6s3UC4A01nm8v9Of1OUJO44Z1pHwDBQQLfny9@mail.gmail.com>
On Fri, 2010-11-19 at 13:53 +0800, Li Yang wrote:
> ><snip>
> >
> >> >My understanding is that the SGMII link is always at 1000Mbps speed -
> >> >see figure 1 from the app note. Additionally look at figure 3. My
> >> >understand from it, and the app note's text is that SGMII
> >> >auto-negotiation doesn't really occur - its just passing the PHY-side
> >> >auto-negotiation results to the Freescale MAC, which software then
> >> >configures. I'm not sure what the purpose of the "SGMII
> >> >auto-negotiation" is - its not really auto- negotiating and the same
> >> >information can be read from the PHY via its MDIO interface, which is
> >what is happening on X-ES boards currently.
> >>
> >> I guess the point is to save MDIO signals to the external PHY and read
> >> the negotiated result from the internal TBI PHY.
> >
> >Do the P2020DS, MPC8572DS and P1/P2 RDB boards not have an MDIO interface
> >to their PHYs'? I've never heard of a board that doesn't, and would guess
> >the tsec driver in U-Boot requires a PHY to be accessible via MDIO to use
> >the corresponding network interface.
>
> I'm not sure which specific silicon omits the MDIO signal. But quoting from
> the app note you mentioned:
>
> " Depending on the PowerQUICC part used, some eTSEC?s may or may not
> provide an external
> MDIO management interface. However, the TBI block for each eTSEC is
> associated in a one to one
> manner, even if that eTSEC does not have an external MDIO connection."
I believe some parts don't have an external MDIO interface for every
eTSEC. if my memory is correct the MPC8572 only has 2 MDIO ports and 3
eTSECS. But 1 MDIO port can be used to communicate with all 3 eTSECS'
PHYs assuming each PHY has a unique address. (eg eTSEC1, 2, and 3 use
eTSEC1's MDIO port).
> The auto-negotiation mechanism between TBI PHY and real PHY does make
> it possible
> to save external MDIO signals if only SGMII interface is used.
That seems like an awfully big sacrifice to save routing 2 signals.
I've never heard of anyone doing this. I don't think the current tsec
driver in U-Boot would support this configuration either, so I'm not
sure how much weight it holds.
> >I can forward you the email thread about SGMII auto-negotiation with
> >Freescale's FAE off-list if you'd like as well.
>
> Yes, please. Thanks
I just forwarded it.
Best,
Peter
next prev parent reply other threads:[~2010-11-20 0:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 9:43 [U-Boot] [PATCH] revert "tsec: Force TBI PHY to 1000Mbps full duplex in SGMII mode" Zhao Chenhui
2010-11-17 10:41 ` Mike Frysinger
2010-11-17 13:14 ` Wolfgang Denk
2010-11-17 15:49 ` Peter Tyser
2010-11-18 4:13 ` Li Yang-R58472
2010-11-18 5:01 ` Peter Tyser
2010-11-18 6:50 ` [U-Boot] [PATCH] revert "tsec: Force TBI PHY to 1000Mbps fullduplex " Li Yang-R58472
2010-11-18 15:34 ` Peter Tyser
2010-11-19 5:53 ` Li Yang
2010-11-20 0:01 ` Peter Tyser [this message]
2010-12-02 4:52 ` [U-Boot] [PATCH] revert "tsec: Force TBI PHY to 1000Mbps full duplex " Kumar Gala
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=1290211303.20072.120.camel@petert \
--to=ptyser@xes-inc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.