1. 10 6月, 2019 2 次提交
  2. 29 5月, 2019 1 次提交
  3. 04 5月, 2019 1 次提交
    • J
      net: hns3: add support for multiple media type · 88d10bd6
      Jian Shen 提交于
      Previously, we can only identify copper and fiber type, the
      supported link modes of port information are always showing
      SR type. This patch adds support for multiple media types,
      include SR, LR CR, KR. Driver needs to query the media type
      from firmware periodicly, and updates the port information.
      
      The new port information looks like this:
      Settings for eth0:
              Supported ports: [ FIBRE ]
              Supported link modes:   25000baseCR/Full
                                      25000baseSR/Full
                                      1000baseX/Full
                                      10000baseCR/Full
                                      10000baseSR/Full
                                      10000baseLR/Full
              Supported pause frame use: Symmetric
              Supports auto-negotiation: No
              Supported FEC modes: None BaseR
              Advertised link modes:  Not reported
              Advertised pause frame use: No
              Advertised auto-negotiation: No
              Advertised FEC modes: Not reported
              Speed: 10000Mb/s
              Duplex: Full
              Port: FIBRE
              PHYAD: 0
              Transceiver: internal
              Auto-negotiation: off
              Current message level: 0x00000036 (54)
                                     probe link ifdown ifup
              Link detected: yes
      
      In order to be compatible with old firmware which only support
      sfp speed, we remained using the same query command, and kept
      the former logic.
      Signed-off-by: NJian Shen <shenjian15@huawei.com>
      Signed-off-by: NPeng Li <lipeng321@huawei.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      88d10bd6
  4. 27 4月, 2019 1 次提交
  5. 15 4月, 2019 2 次提交
    • J
      net: hns3: fix set port based VLAN issue for VF · 92f11ea1
      Jian Shen 提交于
      In original codes, ndo_set_vf_vlan() in hns3 driver was implemented
      wrong. It adds or removes VLAN into VLAN filter for VF, but VF is
      unaware of it.
      
      This patch fixes it. When VF loads up, it firstly queries the port
      based VLAN state from PF. When user change port based VLAN state
      from PF, PF firstly checks whether the VF is alive. If the VF is
      alive, then PF notifies the VF the modification; otherwise PF
      configure the port based VLAN state directly.
      
      Fixes: 46a3df9f ("net: hns3: Add HNS3 Acceleration Engine & Compatibility Layer Support")
      Signed-off-by: NJian Shen <shenjian15@huawei.com>
      Signed-off-by: NHuazhong Tan <tanhuazhong@huawei.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      92f11ea1
    • J
      net: hns3: fix set port based VLAN for PF · 21e043cd
      Jian Shen 提交于
      In original codes, ndo_set_vf_vlan() in hns3 driver was implemented
      wrong. It adds or removes VLAN into VLAN filter for VF, but VF is
      unaware of it.
      
      Indeed, ndo_set_vf_vlan() is expected to enable or disable port based
      VLAN (hardware inserts a specified VLAN tag to all TX packets for a
      specified VF) . When enable port based VLAN, we use port based VLAN id
      as VLAN filter entry. When disable port based VLAN, we use VLAN id of
      VLAN device.
      
      This patch fixes it for PF, enable/disable port based VLAN when calls
      ndo_set_vf_vlan().
      
      Fixes: 46a3df9f ("net: hns3: Add HNS3 Acceleration Engine & Compatibility Layer Support")
      Signed-off-by: NJian Shen <shenjian15@huawei.com>
      Signed-off-by: NHuazhong Tan <tanhuazhong@huawei.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      21e043cd
  6. 05 4月, 2019 1 次提交
  7. 25 2月, 2019 2 次提交
  8. 22 2月, 2019 2 次提交
  9. 03 2月, 2019 1 次提交
  10. 31 1月, 2019 1 次提交
  11. 27 1月, 2019 1 次提交
  12. 16 12月, 2018 1 次提交
  13. 18 11月, 2018 2 次提交
  14. 10 11月, 2018 3 次提交
    • H
      net: hns3: add PCIe FLR support for PF · 6b9a97ee
      Huazhong Tan 提交于
      This patch implements the .reset_prepare and .reset_done
      ops from pci framework to support the PF FLR.
      Signed-off-by: NHuazhong Tan <tanhuazhong@huawei.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      6b9a97ee
    • H
      net: hns3: add reset handling for VF when doing PF reset · aa5c4f17
      Huazhong Tan 提交于
      When PF performs a function reset, the hardware will reset both PF
      and all the VF belong to this PF. Hence, both PF's driver and VF's
      driver need to perform corresponding reset operations.
      
      Before PF driver asserting function reset to hardware, it firstly
      set up VF's hardware reset status, and inform the VF driver with
      HNAE3_VF_PF_FUNC_RESET, then VF driver sets this reset type to
      reset_pending and shechule reset task to stop IO and waits for the
      hardware reset status to clear. When PF driver has reinitialized the
      hardware and is ready to process mailbox from VF, PF driver clears
      VF's hardware reset status for VF to continue its reset process.
      
      Also, this patch uses readl_poll_timeout to simplify the hardware reset
      status waitting.
      Signed-off-by: NHuazhong Tan <tanhuazhong@huawei.com>
      Signed-off-by: NYunsheng Lin <linyunsheng@huawei.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      aa5c4f17
    • H
      net: hns3: adjust VF's reset process · dea846e8
      Huazhong Tan 提交于
      Currently when VF need to reset itself, it will send a cmd to PF,
      after receiving the VF reset requset, PF sends a cmd to inform
      VF to enter the reset process and send a cmd to firmware to do the
      actual reset for the VF, it is possible that firmware has resetted
      the VF, but VF has not entered the reset process, which may cause
      IO not stopped problem when firmware is resetting VF.
      
      This patch fixes it by adjusting the VF reset process, when VF
      need to reset itself, it will enter the reset process first, and
      it will tell the PF to send cmd to firmware to reset itself.
      
      Add member reset_pending to struct hclgevf_dev, which indicates that
      there is reset event need to be processed by the VF's reset task, and
      the VF's reset task chooses the highest-level one and clears other
      low-level one when it processes reset_pending.
      
      hclge_inform_reset_assert_to_vf function is unused now, but it will
      be used to support the PF reset with VF working, so declare it in
      the header file.
      Signed-off-by: NHuazhong Tan <tanhuazhong@huawei.com>
      Signed-off-by: NYunsheng Lin <linyunsheng@huawei.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      dea846e8
  15. 01 11月, 2018 1 次提交
  16. 06 10月, 2018 1 次提交
  17. 17 7月, 2018 2 次提交
  18. 02 7月, 2018 1 次提交
  19. 02 6月, 2018 2 次提交
  20. 29 5月, 2018 1 次提交
  21. 11 5月, 2018 1 次提交
  22. 02 5月, 2018 1 次提交
  23. 24 3月, 2018 1 次提交
  24. 23 3月, 2018 3 次提交
  25. 12 3月, 2018 3 次提交
  26. 09 3月, 2018 2 次提交