Skip to content
Snippets Groups Projects
Select Git revision
0 results
Search by author
  • Any Author
0 authors
  1. Aug 20, 2014
    • Shaohui Xie's avatar
      powerpc/T4240QDS/eth: some fix for XFI · 9bf499ac
      Shaohui Xie authored 
      
XFI is supported on T4QDS-XFI board, which removed slot3, and four LANEs
of serdes2 are routed to a SFP+ cages, which to house fiber cable or
direct attach cable(copper), the copper cable is used to emulate the
10GBASE-KR scenario.

So, for XFI usage, there are two scenarios, one will use fiber cable,
another will use copper cable. For fiber cable, there is NO PHY, while
for copper cable, we need to use internal PHY which exist in Serdes to
do auto-negotiation and link training, which implemented in kernel.
We use hwconfig to define cable type for XFI, and fixup dtb based on the
cable type.

For copper cable, set below env in hwconfig:

fsl_10gkr_copper:<10g_mac_name>

the <10g_mac_name> can be fm1_10g1, fm1_10g2, fm2_10g1, fm2_10g2. The
four <10g_mac_name>s do not have to be coexist in hwconfig. For XFI ports,
if a given 10G port will use the copper cable for 10GBASE-KR, set the
<10g_mac_name> of the port in hwconfig, otherwise, fiber cable will be
assumed to be used for the port.

For ex. if four XFI ports will both use copper cable, the hwconfig
should contain:

fsl_10gkr_copper:fm1_10g1,fm1_10g2,fm2_10g1,fm2_10g2

For fiber cable:

1. give PHY address to a XFI port, otherwise, the XFI ports will not be
available in U-boot, there is no PHY physically for XFI when using fiber
cable, this is just to make U-boot happy and we can use the XFI ports
in U-boot.
2. fixup dtb to use fixed-link in case of fiber cable which has no PHY.
Kernel requests that a MAC must have a PHY or fixed-link.

When using XFI protocol, the MAC 9/10 on FM1 should init as 10G interface.

Change serdes 2 protocol 56 to 55 which has same feature as 56 since 56
is not valid any longer.

Signed-off-by: default avatarShaohui Xie <Shaohui.Xie@freescale.com>
Reviewed-by: default avatarYork Sun <yorksun@freescale.com>
      9bf499ac
    • Valentin Longchamp's avatar
      km-powerpc: define CONFIG_PRAM to protect PHRAM and PNVRAM · 24753676
      Valentin Longchamp authored 
      
When u-boot initializes the RAM (early in boot) it looks for the "pram"
env variable to know which is area it cannot use. If the "pram" env variable
is not found, the default CONFIG_PRAM value is used.

This value used to be 0 (no protection at all). This patch sets it to a
value that covers PHRAM and PNVRAM that must be protected in our case.

Signed-off-by: default avatarValentin Longchamp <valentin.longchamp@keymile.com>
Signed-off-by: default avatarHolger Brunck <holger.brunck@keymile.com>
Reviewed-by: default avatarYork Sun <yorksun@freescale.com>
      24753676
    • Vijay Rai's avatar
      driver/qe: update status of QE microcode · 12eeb135
      Vijay Rai authored 
      
This Patch updates error print for QE which should be easily understood

Signed-off-by: default avatarVijay Rai <vijay.rai@freescale.com>
Reviewed-by: default avatarYork Sun <yorksun@freescale.com>
      12eeb135
    • Shaveta Leekha's avatar
      powerpc/mpc85xx: Enabling CPC conditionally based on hwconfig options · 390619dd
      Shaveta Leekha authored 
      
If hwconfig does not contains "en_cpc" then by default all cpcs are enabled
If this config is defined then only those individual cpcs which are defined
in the subargument of "en_cpc" will be enabled e.g en_cpc:cpc1,cpc2; (this
will enable cpc1 and cpc2) or en_cpc:cpc2; (this enables just cpc2)

Signed-off-by: default avatarShaveta Leekha <shaveta@freescale.com>
Signed-off-by: default avatarSandeep Singh <Sandeep@freescale.com>
Reviewed-by: default avatarYork Sun <yorksun@freescale.com>
      390619dd
  3. Aug 12, 2014
  5. Aug 09, 2014