1. 27 10月, 2015 2 次提交
  2. 21 9月, 2015 1 次提交
    • H
      net: add Hisilicon Network Subsystem support (config and documents) · fc7e37c6
      huangdaode 提交于
      The Hisilicon Network Subsystem is a long term evolution IP which is
      supposed to be used in Hisilicon ICT SoC. The IP, which is called hns
      for short, is a TCP/IP acceleration engine, which can directly decode
      TCP/IP stream and distribute them to different ring buffers.
      
      HNS can be configured to work on different mode for different scenario.
      This patch make use only some of the mode to make it as standard
      ethernet NIC. The other mode will be added soon.
      
      The whole function has 4 kernel sub-modules:
      
      hnae: the HNS acceleration engine framework. It provides a abstract
      interface between the engine and the upper layers which make use of the
      engine by ring buffer.
      
      hns_enet_drv: a standard ethernet driver that base on the ring buffer.
      
      hns_dsaf: one of the implementation of HNS acceleration engine, which is
      applied on Hililicon hip05, Hi1610 and other later-on SoCs
      
      hns_mdio: the mdio control to the PHY, used by acceleration engine
      
      This submit add basic config and documents
      Signed-off-by: Nhuangdaode <huangdaode@hisilicon.com>
      Signed-off-by: NKenneth Lee <liguozhu@huawei.com>
      Signed-off-by: NYisen Zhuang <Yisen.Zhuang@huawei.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      fc7e37c6
  3. 18 9月, 2015 1 次提交
  4. 16 9月, 2015 1 次提交
    • M
      drivers: net: cpsw: Add support to drive gpios for ethernet to be functional · 1d147ccb
      Mugunthan V N 提交于
      In DRA72x EVM, by default slave 1 is connected to the onboard
      phy, but slave 2 pins are also muxed with video input module
      which is controlled by pcf857x gpio and currently to select slave
      0 to connect to phy gpio hogging is used, but with
      omap2plus_defconfig the pcf857x gpio is built as module. So when
      using NFS on DRA72x EVM, board doesn't boot as gpio hogging do
      not set proper gpio state to connect slave 0 to phy as it is
      built as module and you do not see any errors for not setting
      gpio and just mentions dhcp reply not got.
      
      To solve this issue, introducing "mode-gpios" in DT when gpio
      based muxing is required. This will throw a warning when gpio
      get fails and returns probe defer. When gpio-pcf857x module is
      installed, cpsw probes again and ethernet becomes functional.
      Verified this on DRA72x with pcf as module and ramdisk.
      Signed-off-by: NMugunthan V N <mugunthanvnm@ti.com>
      Acked-by: NTony Lindgren <tony@atomide.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      1d147ccb
  5. 01 9月, 2015 2 次提交
  6. 21 8月, 2015 1 次提交
  7. 19 8月, 2015 1 次提交
    • A
      net: dsa: Allow multi hop routes to be expressed · 1e72e6f8
      Andrew Lunn 提交于
      With more than two switches in a hierarchy, it becomes necessary to
      describe multi-hop routes between switches. The current binding does
      not allow this, although the older platform_data did. Extend the link
      property to be a list rather than a single phandle to a remote switch.
      It is then possible to express that a port should be used to reach
      more than one switch and the switch maybe more than one hop away.
      Signed-off-by: NAndrew Lunn <andrew@lunn.ch>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      1e72e6f8
  8. 17 8月, 2015 1 次提交
  9. 11 8月, 2015 1 次提交
  10. 30 7月, 2015 1 次提交
    • W
      net: netcp: Fixes efuse mac addr swap on k2e and k2l · 71382bc0
      WingMan Kwok 提交于
      On some of the K2E and K2L platforms, the two DWORDs in
      efuse occupied by the pre-programmed mac address for
      slave port 1 are swapped.  To workaround this issue,
      this patch adds a new define NETCP_EFUSE_ADDR_SWAP (2)
      which signifies the occurrence of such swapping so that
      the driver can take proper action.  The flag can be
      enabled in the corresponding netcp interface dts binding
      as efuse-mac = <2>  under the corresponding netcp
      interface node.
      Signed-off-by: NWingMan Kwok <w-kwok2@ti.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      71382bc0
  11. 29 7月, 2015 1 次提交
  12. 22 7月, 2015 1 次提交
    • S
      of_mdio: add new DT property 'managed' to specify the PHY management type · 4cba5c21
      Stas Sergeev 提交于
      Currently the PHY management type is selected by the MAC driver arbitrary.
      The decision is based on the presence of the "fixed-link" node and on a
      will of the driver's authors.
      This caused a regression recently, when mvneta driver suddenly started
      to use the in-band status for auto-negotiation on fixed links.
      It appears the auto-negotiation may not work when expected by the MAC driver.
      Sebastien Rannou explains:
      << Yes, I confirm that my HW does not generate an in-band status. AFAIK, it's
      a PHY that aggregates 4xSGMIIs to 1xQSGMII ; the MAC side of the PHY (with
      inband status) is connected to the switch through QSGMII, and in this context
      we are on the media side of the PHY. >>
      https://lkml.org/lkml/2015/7/10/206
      
      This patch introduces the new string property 'managed' that allows
      the user to set the management type explicitly.
      The supported values are:
      "auto" - default. Uses either MDIO or nothing, depending on the presence
      of the fixed-link node
      "in-band-status" - use in-band status
      Signed-off-by: NStas Sergeev <stsp@users.sourceforge.net>
      
      CC: Rob Herring <robh+dt@kernel.org>
      CC: Pawel Moll <pawel.moll@arm.com>
      CC: Mark Rutland <mark.rutland@arm.com>
      CC: Ian Campbell <ijc+devicetree@hellion.org.uk>
      CC: Kumar Gala <galak@codeaurora.org>
      CC: Florian Fainelli <f.fainelli@gmail.com>
      CC: Grant Likely <grant.likely@linaro.org>
      CC: devicetree@vger.kernel.org
      CC: linux-kernel@vger.kernel.org
      CC: netdev@vger.kernel.org
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      4cba5c21
  13. 01 7月, 2015 1 次提交
  14. 23 6月, 2015 5 次提交
  15. 12 6月, 2015 1 次提交
  16. 11 6月, 2015 1 次提交
  17. 10 6月, 2015 1 次提交
  18. 09 6月, 2015 2 次提交
  19. 04 6月, 2015 1 次提交
  20. 31 5月, 2015 1 次提交
  21. 23 5月, 2015 1 次提交
  22. 16 5月, 2015 3 次提交
  23. 15 5月, 2015 1 次提交
    • F
      of: mdio: Add a "broken-turn-around" property · ab6016e0
      Florian Fainelli 提交于
      Some Ethernet PHY devices/switches may not properly release the MDIO bus
      during turn-around time, and fail to drive it low, which can be seen by
      some controllers as a read failure, while the data clocked in is still
      correct.
      
      Add a boolean property "broken-turn-around" which is parsed by the
      generic MDIO bus probing code and will set the corresponding bit in the
      MDIO bus phy_ignore_ta_mask bitmask for MDIO bus drivers to utilize that
      information.
      Signed-off-by: NFlorian Fainelli <f.fainelli@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      ab6016e0
  24. 10 5月, 2015 1 次提交
  25. 17 4月, 2015 1 次提交
  26. 09 4月, 2015 1 次提交
  27. 07 4月, 2015 1 次提交
    • P
      net: dsa: fix filling routing table from OF description · 30303813
      Pavel Nakonechny 提交于
      According to description in 'include/net/dsa.h', in cascade switches
      configurations where there are more than one interconnected devices,
      'rtable' array in 'dsa_chip_data' structure is used to indicate which
      port on this switch should be used to send packets to that are destined
      for corresponding switch.
      
      However, dsa_of_setup_routing_table() fills 'rtable' with port numbers
      of the _target_ switch, but not current one.
      
      This commit removes redundant devicetree parsing and adds needed port
      number as a function argument. So dsa_of_setup_routing_table() now just
      looks for target switch number by parsing parent of 'link' device node.
      
      To remove possible misunderstandings with the way of determining target
      switch number, a corresponding comment was added to the source code and
      to the DSA device tree bindings documentation file.
      
      This was tested on a custom board with two Marvell 88E6095 switches with
      following corresponding routing tables: { -1, 10 } and { 8, -1 }.
      Signed-off-by: NPavel Nakonechny <pavel.nakonechny@skitlab.ru>
      Reviewed-by: NAndrew Lunn <andrew@lunn.ch>
      Reviewed-by: NFlorian Fainelli <f.fainelli@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      30303813
  28. 28 3月, 2015 1 次提交
  29. 27 3月, 2015 1 次提交
  30. 26 3月, 2015 1 次提交
  31. 25 3月, 2015 1 次提交