1. 27 7月, 2011 5 次提交
    • A
      watchdog: Add Xilinx watchdog timer driver · e9659e69
      Alejandro Cabrera 提交于
      Watchdog timer device driver for Xilinx xps_timebase_wdt compatible ip cores.
      It takes watchdog timer configuration from device tree and it needs that its
      parent has defined the property "clock-frecuency".
      It is compatible with watchdog timer kernel API, so user apps like watchdogd
      may talk with it.
      Signed-off-by: NAlejandro Cabrera <aldaya@gmail.com>
      Signed-off-by: NWim Van Sebroeck <wim@iguana.be>
      e9659e69
    • W
      watchdog: remove empty pm-functions · 2fc5d52b
      Wolfram Sang 提交于
      While checking what watchdog drivers usually do in suspend/resume to
      spot common behaviour for the watchdog framework, I found these drivers
      which do nothing but add some cruft. Remove it, it is superfluous. New
      approaches should probably be done with pm_ops anyway.
      Signed-off-by: NWolfram Sang <w.sang@pengutronix.de>
      Signed-off-by: NWim Van Sebroeck <wim@iguana.be>
      2fc5d52b
    • N
      watchdog: sp805: Flush posted writes in enable/disable. · 081d83a3
      Nick Bowler 提交于
      There are no reads in these functions, so if MMIO writes are posted,
      the writes in enable/disable may not have completed by the time these
      functions return.  If the functions run from different CPUs, it's
      in theory possible for the writes to be interleaved, which would be
      disastrous for this driver.
      
      At the very least, we need an mmiowb() before releasing the lock, but
      since it seems desirable for the watchdog timer to be actually stopped
      or reset when these functions return, read the lock register to force
      the writes out.
      Signed-off-by: NNick Bowler <nbowler@elliptictech.com>
      Signed-off-by: NWim Van Sebroeck <wim@iguana.be>
      081d83a3
    • N
      watchdog: sp805: Don't write 0 to the load value register. · da3e5150
      Nick Bowler 提交于
      At least on the Versatile Express' V2M, calling wdt_disable followed by
      wdt_enable, for instance by running the following sequence:
      
        echo V > /dev/watchdog; echo V > /dev/watchdog
      
      results in an immediate reset.  The wdt_disable function writes 0 to the
      load register; while the watchdog interrupts are disabled at this point,
      this special value is defined to trigger an interrupt immediately.  It
      appears that in this instance, the reset happens when the interrupts
      are subsequently enabled by wdt_enable.
      
      Putting in a short delay after writing a new load value in wdt_enable
      solves the issue, but it seems cleaner to simply never write 0 to the
      load register at all: according to the hardware docs, writing 0 to the
      control register suffices to stop the counter, and the write of 0 to
      the load register is questionable anyway since this register resets to
      0xffffffff.
      Signed-off-by: NNick Bowler <nbowler@elliptictech.com>
      Signed-off-by: NWim Van Sebroeck <wim@iguana.be>
      da3e5150
    • S
      watchdog: imx2_wdt: add device tree probe support · f5a427ee
      Shawn Guo 提交于
      Adds device tree probe support for imx2_wdt driver.
      Signed-off-by: NShawn Guo <shawn.guo@linaro.org>
      Cc: Grant Likely <grant.likely@secretlab.ca>
      Cc: Wolfram Sang <w.sang@pengutronix.de>
      Signed-off-by: NWim Van Sebroeck <wim@iguana.be>
      f5a427ee
  2. 22 7月, 2011 8 次提交
  3. 17 7月, 2011 1 次提交
    • R
      watchdog: hpwdt depends on PCI · f71d26bb
      Randy Dunlap 提交于
      hpwdt is a PCI driver so it should depend on PCI.
      Fixes these build errors:
      
      drivers/watchdog/hpwdt.c:762: error: implicit declaration of function 'pci_iomap'
      drivers/watchdog/hpwdt.c:762: warning: assignment makes pointer from integer without a cast
      drivers/watchdog/hpwdt.c:797: error: implicit declaration of function 'pci_iounmap'
      Signed-off-by: NRandy Dunlap <rdunlap@xenotime.net>
      Signed-off-by: NWim Van Sebroeck <wim@iguana.be>
      Cc: Thomas Mingarelli <thomas.mingarelli@hp.com>
      f71d26bb
  4. 16 7月, 2011 1 次提交
  5. 29 6月, 2011 1 次提交
  6. 28 6月, 2011 6 次提交
  7. 27 5月, 2011 1 次提交
    • S
      mfd: Use mfd cell platform_data for rdc321x cells platform bits · 9abd768a
      Samuel Ortiz 提交于
      With the addition of a platform device mfd_cell pointer, MFD drivers
      can go back to passing platform data back to their sub drivers.
      This allows for an mfd_cell->mfd_data removal and thus keep the
      sub drivers MFD agnostic. This is mostly needed for non MFD aware
      sub drivers.
      
      Cc: Grant Likely <grant.likely@secretlab.ca>
      Cc: Wim Van Sebroeck <wim@iguana.be>
      Cc: Florian Fainelli <florian@openwrt.org>
      Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      9abd768a
  8. 19 5月, 2011 3 次提交
  9. 26 4月, 2011 1 次提交
  10. 10 4月, 2011 1 次提交
  11. 08 4月, 2011 1 次提交
  12. 31 3月, 2011 1 次提交
  13. 29 3月, 2011 5 次提交
  14. 23 3月, 2011 1 次提交
  15. 16 3月, 2011 4 次提交