From: Heiko Schocher <hs@denx.de>
To: "Varlese, Christopher" <Christopher.Varlese@keymile.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] 83xx: add support for the kmeter1 board.
Date: Fri, 08 May 2009 07:44:12 +0200 [thread overview]
Message-ID: <4A03C6AC.5080007@denx.de> (raw)
In-Reply-To: <D839955AA28B9A42A61B9181506E27C40182F50E@SRVCHBER1212.ch.keymile.net>
Hello Christopher,
Varlese, Christopher wrote:
> (FYI I working on the kmeter1)
>
> kmeter1.c reuses the same QE_ENET10 RGMII errata workaround code from mpc836x_mds.c (MPC8360EMDS eval board).
>
> In my view errata nodes in the dts is overkill. Maybe the errata code can go into a reusable function somewhere in 83xx/ or in ucc_geth.c?
To put an errata node in the dts was just an idea ;-)
I also mentioned putting this code in the ucc_geth.c driver ...
> I also think the original errata code needs improving:
> - mask some SVR bits so activated for all matching CPU models, e.g. MPC8360 & MPC8360E.
Did a first try in my v2 patch, see:
http://ozlabs.org/pipermail/linuxppc-dev/2009-April/071384.html
but I got no response yet.
> - The code in mpc836x_mds.c and kmeter1.c does not do exactly what Freescale errata says!
:-(
> Here the errata document:
> http://www.freescale.com/files/32bit/doc/errata/MPC8360ECE.pdf
>
> Because kmeter1 is using an MPC8360 CPU model the workaround doesn't actually trigger. So to kill 2 birds with 1 stone we tested a Uboot patch (below) doing what QE_ENET10 says. It seemed to work fine for us.
> /* RGMII timing Errata workaround for rev 2.1 silicon
> * (ref: MPC8360ECE rev.1 12/2007 QE_ENET10 UCC2 option 1)
> */
> void *reg = (void *)(CONFIG_SYS_IMMR + 0x14ac);
> clrsetbits_be32 (reg, 0x000000F0, 0x000000A0);
>
>>From my point of view:
> - The workaround code in kmeter1.c could go for now.
> - An improved errata workaround for 836x boards would be nice (..who is motivated? :-))
I can make this errata, if someone gives advice, where to put ...
I vote for putting it into the ucc_geth.c driver, and activating it
maybe through the "phy-connection-type" if it activates the rgmii
mode ... ?
bye
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
prev parent reply other threads:[~2009-05-08 5:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 6:09 [PATCH] 83xx: add support for the kmeter1 board Heiko Schocher
2009-04-23 14:25 ` Kumar Gala
2009-04-23 14:50 ` Heiko Schocher
2009-04-27 5:38 ` Heiko Schocher
2009-04-27 18:05 ` Scott Wood
2009-04-28 4:42 ` Heiko Schocher
2009-04-28 16:35 ` Scott Wood
2009-04-29 4:48 ` [PATCH v2] " Heiko Schocher
2009-06-11 2:43 ` Kumar Gala
2009-06-11 6:03 ` Heiko Schocher
2009-06-11 6:16 ` [PATCH v3] " Heiko Schocher
2009-06-11 14:10 ` Kumar Gala
2009-06-11 18:08 ` Heiko Schocher
2009-06-11 18:10 ` [PATCH v4] " Heiko Schocher
2009-06-12 1:13 ` David Gibson
2009-06-12 5:27 ` Heiko Schocher
2009-06-15 2:42 ` David Gibson
2009-06-15 7:38 ` [PATCH v5] " Heiko Schocher
2009-06-16 3:16 ` Kumar Gala
2009-05-07 17:49 ` [PATCH] " Varlese, Christopher
2009-05-08 5:44 ` Heiko Schocher [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=4A03C6AC.5080007@denx.de \
--to=hs@denx.de \
--cc=Christopher.Varlese@keymile.com \
--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).