30 Oct, 2015

1 commit

  • MDIO controller base on FMAN2 was defined as CONFIG_SYS_FSL_FM2_ADDR
    plus offset, but CONFIG_SYS_FSL_FM2_ADDR only defined when there are two
    FMANs, so we should only define MDIO controller base on FMAN2 when there
    is FMAN2.

    Signed-off-by: Shaohui Xie
    Signed-off-by: Mingkai Hu
    Signed-off-by: Gong Qianyu
    Reviewed-by: York Sun

    Shaohui Xie
     

06 Dec, 2014

1 commit

  • fm_standard_init() initializes each 10G port by FM_TGEC_INFO_INITIALIZER.
    but it needs different implementation of FM_TGEC_INFO_INITIALIZER on different SoCs.
    on SoCs earlier(e.g. T4240, T2080), the notation between 10GEC and MAC as below:
    10GEC1->MAC9, 10GEC2->MAC10, 10GEC3->MAC1, 10GEC4->MAC2
    on SoCs later(e.g. T1024, etc), the notation between 10GEC and MAC as below:
    10GEC1->MAC1, 10GEC2->MAC2

    so we introduce CONFIG_FSL_FM_10GEC_REGULAR_NOTATION to fit the new SoCs on
    which 10GEC enumeration is consistent with MAC enumeration.

    Signed-off-by: Shengzhou Liu
    Reviewed-by: York Sun

    Shengzhou Liu
     

09 Sep, 2014

1 commit

  • fsl_enet.h defines the mapping of the usual MII management
    registers, which are included in the MDIO register block
    common to Freescale ethernet controllers. So it shouldn't
    depend on the CPU architecture but it should be actually
    part of the arch independent fsl_mdio.h.

    To remove the arch dependency, merge the content of
    asm/fsl_enet.h into fsl_mdio.h.
    Some files (like fm_eth.h) were simply including fsl_enet.h
    only for phy.h. These were updated to include phy.h instead.

    Signed-off-by: Claudiu Manoil

    Claudiu Manoil
     

26 Nov, 2013

1 commit


25 Oct, 2013

1 commit

  • This can be useful if one wants to disable an interface in u-boot
    because u-boot should not manage it but then later reenable it for FDT
    fixing or if the kernel uses this interface.

    Signed-off-by: Valentin Longchamp
    [York Sun: fix conflict in fm_eth.h]
    Acked-by: York Sun

    Valentin Longchamp
     

17 Oct, 2013

1 commit

  • Fix PHY addresses for QSGMII Riser Card working in
    SGMII mode on board P3041/P5020/P4080/P5040/B4860.

    QSGMII Riser Card can work in SGMII mode, but
    having the different PHY addresses.
    So the following steps should be done:
    1. Confirm whether QSGMII Riser Card is used.
    2. If yes, set the proper PHY address.
    Generally, the function is_qsgmii_riser_card() is
    for step 1, and set_sgmii_phy() for step 2.

    However, there are still some special situations,
    take P5040 and B4860 as examples, the PHY addresses
    need to be changed when serdes protocol is changed,
    so it is necessary to confirm the protocol before
    setting PHY addresses.

    Signed-off-by: Zhao Qiang

    Zhao Qiang
     

24 Jul, 2013

1 commit


15 May, 2013

1 commit

  • 1. fix 10G mac offset by plus 8;
    2. add second 10G port info for FM1 & FM2 when init ethernet info;
    3. fix 10G lanes name to match lane protocol table;

    Signed-off-by: Shaohui Xie
    Signed-off-by: Roy Zang
    Signed-off-by: Andy Fleming

    Shaohui Xie
     

23 Oct, 2012

2 commits

  • The multirate ethernet media access controller (mEMAC) interfaces to
    10Gbps and below Ethernet/IEEE 802.3 networks via either RGMII/RMII
    interfaces or XAUI/XFI/SGMII/QSGMII using the high-speed SerDes interface.

    Signed-off-by: Sandeep Singh
    Signed-off-by: Poonam Aggrwal
    Signed-off-by: Roy Zang
    Signed-off-by: Andy Fleming

    Roy Zang
     
  • Add support for Freescale T4240 SoC. Feature of T4240 are
    (incomplete list):

    12 dual-threaded e6500 cores built on Power Architecture® technology
    Arranged as clusters of four cores sharing a 2 MB L2 cache.
    Up to 1.8 GHz at 1.0 V with 64-bit ISA support (Power Architecture
    v2.06-compliant)
    Three levels of instruction: user, supervisor, and hypervisor
    1.5 MB CoreNet Platform Cache (CPC)
    Hierarchical interconnect fabric
    CoreNet fabric supporting coherent and non-coherent transactions with
    prioritization and bandwidth allocation amongst CoreNet end-points
    1.6 Tbps coherent read bandwidth
    Queue Manager (QMan) fabric supporting packet-level queue management and
    quality of service scheduling
    Three 64-bit DDR3/3L SDRAM memory controllers with ECC and interleaving
    support
    Memory prefetch engine (PMan)
    Data Path Acceleration Architecture (DPAA) incorporating acceleration for
    the following functions:
    Packet parsing, classification, and distribution (Frame Manager 1.1)
    Queue management for scheduling, packet sequencing, and congestion
    management (Queue Manager 1.1)
    Hardware buffer management for buffer allocation and de-allocation
    (BMan 1.1)
    Cryptography acceleration (SEC 5.0) at up to 40 Gbps
    RegEx Pattern Matching Acceleration (PME 2.1) at up to 10 Gbps
    Decompression/Compression Acceleration (DCE 1.0) at up to 20 Gbps
    DPAA chip-to-chip interconnect via RapidIO Message Manager (RMAN 1.0)
    32 SerDes lanes at up to 10.3125 GHz
    Ethernet interfaces
    Up to four 10 Gbps Ethernet MACs
    Up to sixteen 1 Gbps Ethernet MACs
    Maximum configuration of 4 x 10 GE + 8 x 1 GE
    High-speed peripheral interfaces
    Four PCI Express 2.0/3.0 controllers
    Two Serial RapidIO 2.0 controllers/ports running at up to 5 GHz with
    Type 11 messaging and Type 9 data streaming support
    Interlaken look-aside interface for serial TCAM connection
    Additional peripheral interfaces
    Two serial ATA (SATA 2.0) controllers
    Two high-speed USB 2.0 controllers with integrated PHY
    Enhanced secure digital host controller (SD/MMC/eMMC)
    Enhanced serial peripheral interface (eSPI)
    Four I2C controllers
    Four 2-pin or two 4-pin UARTs
    Integrated Flash controller supporting NAND and NOR flash
    Two eight-channel DMA engines
    Support for hardware virtualization and partitioning enforcement
    QorIQ Platform's Trust Architecture 1.1

    Signed-off-by: York Sun
    Signed-off-by: Kumar Gala
    Signed-off-by: Andy Fleming
    Signed-off-by: Roy Zang
    Signed-off-by: Prabhakar Kushwaha
    Signed-off-by: Shengzhou Liu
    Signed-off-by: Andy Fleming

    York Sun
     

23 Aug, 2012

2 commits


03 Oct, 2011

1 commit


30 Sep, 2011

1 commit

  • The Frame Manager (FMan) on QorIQ SoCs with DPAA (datapath acceleration
    architecture) is the ethernet contoller block. Normally it is utilized
    via Queue Manager (Qman) and Buffer Manager (Bman). However for boot
    usage the FMan supports a mode similar to QE or CPM ethernet collers
    called Independent mode.

    Additionally the FMan block supports multiple 1g and 10g interfaces as a
    single entity in the system rather than each controller being managed
    uniquely. This means we have to initialize all of Fman regardless of
    the number of interfaces we utilize.

    Different SoCs support different combinations of the number of FMan as
    well as the number of 1g & 10g interfaces support per Fman.

    We add support for the following SoCs:
    * P1023 - 1 Fman, 2x1g
    * P4080 - 2 Fman, each Fman has 4x1g and 1x10g
    * P204x/P3041/P5020 - 1 Fman, 5x1g, 1x10g

    Signed-off-by: Dave Liu
    Signed-off-by: Andy Fleming
    Signed-off-by: Timur Tabi
    Signed-off-by: Roy Zang
    Signed-off-by: Dai Haruki
    Signed-off-by: Kim Phillips
    Signed-off-by: Ioana Radulescu
    Signed-off-by: Lei Xu
    Signed-off-by: Mingkai Hu
    Signed-off-by: Scott Wood
    Signed-off-by: Shaohui Xie
    Signed-off-by: Kumar Gala

    Kumar Gala