1. 09 4月, 2016 1 次提交
  2. 15 3月, 2016 2 次提交
  3. 02 3月, 2016 1 次提交
  4. 26 2月, 2016 2 次提交
  5. 24 2月, 2016 1 次提交
  6. 08 12月, 2015 1 次提交
  7. 24 11月, 2015 1 次提交
  8. 02 11月, 2015 1 次提交
  9. 22 10月, 2015 2 次提交
  10. 11 10月, 2015 3 次提交
  11. 19 8月, 2015 1 次提交
  12. 14 8月, 2015 1 次提交
  13. 12 8月, 2015 2 次提交
  14. 10 8月, 2015 1 次提交
  15. 30 3月, 2015 1 次提交
  16. 10 3月, 2015 1 次提交
    • F
      net: dsa: utilize of_find_net_device_by_node · 769a0202
      Florian Fainelli 提交于
      Using of_find_device_by_node() restricts the search to platform_device that
      match the specified device_node pointer. This is not even remotely true for
      network devices backed by a pci_device for instance.
      
      of_find_net_device_by_node() allows us to do a more thorough lookup to find the
      struct net_device corresponding to a particular device_node pointer.
      
      For symetry with the non-OF code path, we hold the net_device pointer in
      dsa_probe() just like what dev_to_net_dev() does when we call this
      function.
      Signed-off-by: NFlorian Fainelli <f.fainelli@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      769a0202
  17. 06 3月, 2015 1 次提交
  18. 26 2月, 2015 2 次提交
  19. 31 10月, 2014 3 次提交
  20. 18 10月, 2014 1 次提交
  21. 29 9月, 2014 2 次提交
  22. 23 9月, 2014 2 次提交
  23. 20 9月, 2014 1 次提交
  24. 16 9月, 2014 2 次提交
    • A
      dsa: Replace mii_bus with a generic host device · b4d2394d
      Alexander Duyck 提交于
      This change makes it so that instead of passing and storing a mii_bus we
      instead pass and store a host_dev.  From there we can test to determine the
      exact type of device, and can verify it is the correct device for our switch.
      
      So for example it would be possible to pass a device pointer from a pci_dev
      and instead of checking for a PHY ID we could check for a vendor and/or device
      ID.
      Signed-off-by: NAlexander Duyck <alexander.h.duyck@intel.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      b4d2394d
    • A
      dsa: Split ops up, and avoid assigning tag_protocol and receive separately · 5075314e
      Alexander Duyck 提交于
      This change addresses several issues.
      
      First, it was possible to set tag_protocol without setting the ops pointer.
      To correct that I have reordered things so that rcv is now populated before
      we set tag_protocol.
      
      Second, it didn't make much sense to keep setting the device ops each time a
      new slave was registered.  So by moving the receive portion out into root
      switch initialization that issue should be addressed.
      
      Third, I wanted to avoid sending tags if the rcv pointer was not registered
      so I changed the tag check to verify if the rcv function pointer is set on
      the root tree.  If it is then we start sending DSA tagged frames.
      
      Finally I split the device ops pointer in the structures into two spots.  I
      placed the rcv function pointer in the root switch since this makes it
      easiest to access from there, and I placed the xmit function pointer in the
      slave for the same reason.
      Signed-off-by: NAlexander Duyck <alexander.h.duyck@intel.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      5075314e
  25. 14 9月, 2014 1 次提交
  26. 28 8月, 2014 3 次提交