1. 30 3月, 2015 4 次提交
  2. 28 3月, 2015 8 次提交
  3. 26 3月, 2015 1 次提交
  4. 25 3月, 2015 5 次提交
  5. 24 3月, 2015 15 次提交
  6. 23 3月, 2015 5 次提交
  7. 22 3月, 2015 1 次提交
    • O
      cx82310_eth: wait for firmware to become ready · f40bff42
      Ondrej Zary 提交于
      When the device is powered up, some (older) firmware versions fail to work
      properly if we send commands before the boot is complete (everything is OK
      when the device is hot-plugged). The firmware indicates its ready status by
      putting the link up.
      Newer firmwares delay the first command so they don't suffer from this problem.
      They also report the link being always up.
      
      Wait for firmware to become ready (link up) before sending any commands and/or
      data.
      
      This also allows lowering CMD_TIMEOUT value to a reasonable time.
      
      Tested with 4.1.0.9 (old) and 4.1.0.30 (new) firmware versions.
      Signed-off-by: NOndrej Zary <linux@rainbow-software.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      f40bff42
  8. 21 3月, 2015 1 次提交
    • W
      net: netcp: ethss: enhancement to support NetCP 1.5 ethss · 9a391c7b
      WingMan Kwok 提交于
      NetCP 1.5 available on newer K2 SoCs such as K2E and K2L introduced 3
      variants of the ethss subsystem, 9 port, 5 port and 2 port. These have
      one host port towards the CPU and N external slave ports.
      
      To customize the driver for these new ethss sub systems, multiple
      compatibility strings are introduced. Currently some of parameters that
      are different on different variants such as number of ALE ports, stats
      modules and number of ports are defined through constants. These are now
      changed to variables in gbe_priv data that get set based on the
      compatibility string. This is required as there are no hardware
      identification registers available to distinguish among the variants
      of NetCP 1.5 ethss. However there is identification register available
      to differentiate between NetCP 1.4 vs NetCP 1.5 and the same is made use
      of in the code to differentiate them.
      
      For more reading on the details of this peripheral, please refer to the
      User Guide available at http://www.ti.com/lit/pdf/spruhz3Signed-off-by: NMurali Karicheri <m-karicheri2@ti.com>
      Signed-off-by: NWingMan Kwok <w-kwok2@ti.com>
      CC: "David S. Miller" <davem@davemloft.net>
      CC: Mugunthan V N <mugunthanvnm@ti.com>
      CC: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
      CC: Grygorii Strashko <grygorii.strashko@ti.com>
      CC: Christoph Jaeger <cj@linux.com>
      CC: Lokesh Vutla <lokeshvutla@ti.com>
      CC: Markus Pargmann <mpa@pengutronix.de>
      CC: Kumar Gala <galak@codeaurora.org>
      CC: Ian Campbell <ijc+devicetree@hellion.org.uk>
      CC: Mark Rutland <mark.rutland@arm.com>
      CC: Pawel Moll <pawel.moll@arm.com>
      CC: Rob Herring <robh+dt@kernel.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      9a391c7b