22 Jul, 2011

1 commit

  • Prior to this change, most PHY configuration parameters were passed
    into the STMMAC device as a separate PHY device. As well as being
    unusual, this made it difficult to make changes to the MAC/PHY
    relationship.

    This patch moves all the PHY parameters into the MAC configuration
    structure, mainly as a separate structure. This allows us to completely
    ignore the MDIO bus attached to a stmmac if desired, and not create
    the PHY bus. It also allows the stmmac driver to use a different PHY
    from the one it is connected to, for example a fixed PHY or bit banging
    PHY.

    Also derive the stmmac/PHY connection type (MII/RMII etc) from the
    mode can be passed into _configure_ethernet.
    STLinux kernel at git://git.stlinux.com/stm/linux-sh4-2.6.32.y.git
    provides several examples how to use this new infrastructure (that
    actually is easier to maintain and clearer).

    Signed-off-by: Stuart Menefy
    Signed-off-by: Giuseppe Cavallaro
    Signed-off-by: David S. Miller

    Giuseppe CAVALLARO
     

19 Jul, 2011

1 commit


04 May, 2011

1 commit

  • stmmac.h uses struct platform_device and doesn't include
    . Whereas drivers/net/stmmac/stmmac.h includes it, but
    doesn't directly use it. And so we get following compilation warning while using
    this file:
    warning: ‘struct platform_device’ declared inside parameter list

    This patch includes in linux/stmmac.h and removes it
    from drivers/net/stmmac/stmmac.h

    Signed-off-by: Viresh Kumar
    Acked-by: Giuseppe Cavallaro
    Signed-off-by: David S. Miller

    Viresh KUMAR
     

31 Mar, 2011

1 commit


25 Nov, 2010

1 commit

  • This patch adds in the plat_stmmacenet_data
    the init and exit callbacks that can be used
    for invoking specific platform functions.
    For example, on ST targets, these call the
    PAD manager functions to set PIO lines and
    syscfg registers.
    The patch removes the stmmac_claim_resource
    only used on STM Kernels as well.

    Signed-off-by: Giuseppe Cavallaro
    Signed-off-by: David S. Miller

    Giuseppe CAVALLARO
     

25 Sep, 2010

1 commit


18 Sep, 2010

2 commits

  • The first version of the driver had hard-coded the logic
    for handling the checksum offloading.
    This was designed according to the chips included in
    the STM platforms where:
    o MAC10/100 supports no COE at all.
    o GMAC fully supports RX/TX COE.

    This is not good for other chip configurations where,
    for example, the mac10/100 supports the tx csum in HW
    or when the GMAC has no IPC.

    Thanks to Johannes Stezenbach; he provided me a first
    draft of this patch that only reviewed the IPC for the
    GMAC devices.

    This patch also helps on SPEAr platforms where the
    MAC10/100 can perform the TX csum in HW.
    Thanks to Deepak SIKRI for his support on this.

    In the end, GMAC devices for STM platforms have
    a bugged Jumbo frame support that needs to have
    the Tx COE disabled for oversized frames (due to
    limited buffer sizes). This information is also
    passed through the driver's platform structure.

    Signed-off-by: Giuseppe Cavallaro
    Signed-off-by: Johannes Stezenbach
    Signed-off-by: Deepak SIKRI
    Signed-off-by: David S. Miller

    Giuseppe CAVALLARO
     
  • This patch adds the CSR Clock range selection.

    Original patch from Johannes Stezenbach fixed the CSR
    in the stmmac_mdio. We agreed to provide this through
    the platform instead of.
    Also thanks to Johannes for having tested it on ARM.

    Signed-off-by: Giuseppe Cavallaro
    Signed-off-by: Johannes Stezenbach
    Signed-off-by: David S. Miller

    Giuseppe CAVALLARO
     

26 Aug, 2010

1 commit


14 Apr, 2010

1 commit

  • The new enh_desc is used for selecting the enhanced descriptors
    structure. There are several scenarios; some chips (mac10/100
    or gmac) want to use the enhanced descriptors; others want the normal
    ones.
    For example, on ST platforms: MAC10/100 uses the normal desc structure
    and the GMAC uses the enhanced one.
    It can be useful to get this information from the platform.
    This could also be decided at run-time looking at the chip's ID number;
    but it could happen that chips with the same ID want to use different
    descriptor structure.

    Signed-off-by: Giuseppe Cavallaro
    Signed-off-by: David S. Miller

    Giuseppe CAVALLARO
     

08 Jan, 2010

1 commit