22 Aug, 2014

14 commits


21 Aug, 2014

7 commits

  • Tom Rini
     
  • There is the requirement on the chassis's backplane that when the clocks
    have been enabled, they then should not disappear.

    Resetting the Zarlink clocking chips at unit reset violates this
    requirement because the backplane clocks are not supplied during the
    reset time.

    To avoid this side effect, both the Zarlink clocking chips are reset
    only at power up.

    Signed-off-by: Valentin Longchamp

    Valentin Longchamp
     
  • Board specific README file should be moved to board folder.

    Signed-off-by: York Sun

    York Sun
     
  • 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:

    the can be fm1_10g1, fm1_10g2, fm2_10g1, fm2_10g2. The
    four 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
    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: Shaohui Xie
    Reviewed-by: York Sun

    Shaohui Xie
     
  • 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: Valentin Longchamp
    Signed-off-by: Holger Brunck
    Reviewed-by: York Sun

    Valentin Longchamp
     
  • This Patch updates error print for QE which should be easily understood

    Signed-off-by: Vijay Rai
    Reviewed-by: York Sun

    Vijay Rai
     
  • 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: Shaveta Leekha
    Signed-off-by: Sandeep Singh
    Reviewed-by: York Sun

    Shaveta Leekha
     

20 Aug, 2014

4 commits


13 Aug, 2014

15 commits