1. 23 8月, 2017 1 次提交
  2. 25 9月, 2014 1 次提交
  3. 17 1月, 2014 1 次提交
    • G
      dt/bindings: Remove device_type "serial" from marvell,mv64360-mpsc · 482c4341
      Grant Likely 提交于
      device_type is deprecated. There is no need to check for it in device
      driver code and no need to specify it in the device tree. Remove the
      property from stock .dts files and remove the check for it from device
      drivers. This change should be 100% backwards compatible with old device
      trees.
      Signed-off-by: NGrant Likely <grant.likely@linaro.org>
      Cc: Rob Herring <rob.herring@calxeda.com>
      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: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      482c4341
  4. 29 10月, 2013 1 次提交
  5. 22 3月, 2013 1 次提交
    • F
      mv643xx_eth: convert to use the Marvell Orion MDIO driver · c3a07134
      Florian Fainelli 提交于
      This patch converts the Marvell MV643XX ethernet driver to use the
      Marvell Orion MDIO driver. As a result, PowerPC and ARM platforms
      registering the Marvell MV643XX ethernet driver are also updated to
      register a Marvell Orion MDIO driver. This driver voluntarily overlaps
      with the Marvell Ethernet shared registers because it will use a subset
      of this shared register (shared_base + 0x4 to shared_base + 0x84). The
      Ethernet driver is also updated to look up for a PHY device using the
      Orion MDIO bus driver.
      
      For ARM and PowerPC we register a single instance of the "mvmdio" driver
      in the system like it used to be done with the use of the "shared_smi"
      platform_data cookie on ARM.
      
      Note that it is safe to register the mvmdio driver only for the "ge00"
      instance of the driver because this "ge00" interface is guaranteed to
      always be explicitely registered by consumers of
      arch/arm/plat-orion/common.c and other instances (ge01, ge10 and ge11)
      were all pointing their shared_smi to ge00. For PowerPC the in-tree
      Device Tree Source files mention only one MV643XX ethernet MAC instance
      so the MDIO bus driver is registered only when id == 0.
      Signed-off-by: NFlorian Fainelli <florian@openwrt.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      c3a07134
  6. 02 3月, 2011 1 次提交
  7. 01 11月, 2010 1 次提交
  8. 24 7月, 2010 1 次提交
    • G
      of: Merge of_platform_bus_type with platform_bus_type · eca39301
      Grant Likely 提交于
      of_platform_bus was being used in the same manner as the platform_bus.
      The only difference being that of_platform_bus devices are generated
      from data in the device tree, and platform_bus devices are usually
      statically allocated in platform code.  Having them separate causes
      the problem of device drivers having to be registered twice if it
      was possible for the same device to appear on either bus.
      
      This patch removes of_platform_bus_type and registers all of_platform
      bus devices and drivers on the platform bus instead.  A previous patch
      made the of_device structure an alias for the platform_device structure,
      and a shim is used to adapt of_platform_drivers to the platform bus.
      
      After all of of_platform_bus drivers are converted to be normal platform
      drivers, the shim code can be removed.
      Signed-off-by: NGrant Likely <grant.likely@secretlab.ca>
      Acked-by: NDavid S. Miller <davem@davemloft.net>
      eca39301
  9. 17 2月, 2010 1 次提交
  10. 05 9月, 2008 1 次提交
    • L
      mv643xx_eth: remove force_phy_addr field · ac840605
      Lennert Buytenhek 提交于
      Currently, there are two different fields in the
      mv643xx_eth_platform_data struct that together describe the PHY
      address -- one field (phy_addr) has the address of the PHY, but if
      that address is zero, a second field (force_phy_addr) needs to be
      set to distinguish the actual address zero from a zero due to not
      having filled in the PHY address explicitly (which should mean
      'use the default PHY address').
      
      If we are a bit smarter about the encoding of the phy_addr field,
      we can avoid the need for a second field -- this patch does that.
      Signed-off-by: NLennert Buytenhek <buytenh@marvell.com>
      ac840605
  11. 14 5月, 2008 1 次提交
  12. 29 4月, 2008 1 次提交
  13. 24 4月, 2008 2 次提交
  14. 15 4月, 2008 3 次提交
  15. 26 1月, 2008 1 次提交
  16. 17 1月, 2008 1 次提交
  17. 25 7月, 2007 1 次提交
  18. 25 6月, 2007 1 次提交
  19. 12 5月, 2007 3 次提交