1. 25 1月, 2008 1 次提交
    • D
      [POWERPC] Enable RTC for Ebony and Walnut (v2) · 22258fa4
      David Gibson 提交于
      This patch extends the Ebony and Walnut platform code to instantiate
      the existing ds1742 RTC class driver for the DS1743 RTC/NVRAM chip
      found on both those boards.  The patch uses a helper function to scan
      the device tree and instantiate the appropriate platform_device based
      on it, so it should be easy to extend for other boards which have mmio
      mapped RTC chips.
      
      Along with this, the device tree binding for the ds1743 chips is
      tweaked, based on the existing DS1385 OF binding found at:
      	http://playground.sun.com/1275/proposals/Closed/Remanded/Accepted/346-it.txt
      Although that document covers the NVRAM portion of the chip, whereas
      here we're interested in the RTC portion, so it's not entirely clear
      if that's a good model.
      
      This implements only RTC class driver support - that is /dev/rtc0, not
      /dev/rtc, and the low-level get/set time callbacks remain
      unimplemented.  That means in order to get at the clock you will
      either need a modified version of hwclock which will look at
      /dev/rtc0, or you'll need to configure udev to symlink rtc0 to rtc.
      Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Signed-off-by: NJosh Boyer <jwboyer@linux.vnet.ibm.com>
      22258fa4
  2. 24 12月, 2007 7 次提交
  3. 20 10月, 2007 3 次提交
  4. 11 10月, 2007 1 次提交
    • D
      Device tree aware EMAC driver · 1d3bb996
      David Gibson 提交于
      Based on BenH's earlier work, this is a new version of the EMAC driver
      for the built-in ethernet found on PowerPC 4xx embedded CPUs.  The
      same ASIC is also found in the Axon bridge chip.  This new version is
      designed to work in the arch/powerpc tree, using the device tree to
      probe the device, rather than the old and ugly arch/ppc OCP layer.
      
      This driver is designed to sit alongside the old driver (that lies in
      drivers/net/ibm_emac and this one in drivers/net/ibm_newemac).  The
      old driver is left in place to support arch/ppc until arch/ppc itself
      reaches its final demise (not too long now, with luck).
      
      This driver still has a number of things that could do with cleaning
      up, but I think they can be fixed up after merging.  Specifically:
      	- Should be adjusted to properly use the dma mapping API.
      Axon needs this.
      	- Probe logic needs reworking, in conjuction with the general
      probing code for of_platform devices.  The dependencies here between
      EMAC, MAL, ZMII etc. make this complicated.  At present, it usually
      works, because we initialize and register the sub-drivers before the
      EMAC driver itself, and (being in driver code) runs after the devices
      themselves have been instantiated from the device tree.
      Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      1d3bb996
  5. 07 9月, 2007 1 次提交
  6. 20 8月, 2007 1 次提交
  7. 17 5月, 2007 1 次提交
  8. 08 5月, 2007 1 次提交