1. 18 11月, 2013 1 次提交
    • J
      watchdog: Get rid of MODULE_ALIAS_MISCDEV statements · 487722cf
      Jean Delvare 提交于
      I just can't find any value in MODULE_ALIAS_MISCDEV(WATCHDOG_MINOR)
      and MODULE_ALIAS_MISCDEV(TEMP_MINOR) statements.
      
      Either the device is enumerated and the driver already has a module
      alias (e.g. PCI, USB etc.) that will get the right driver loaded
      automatically.
      
      Or the device is not enumerated and loading its driver will lead to
      more or less intrusive hardware poking. Such hardware poking should be
      limited to a bare minimum, so the user should really decide which
      drivers should be tried and in what order. Trying them all in
      arbitrary order can't do any good.
      
      On top of that, loading that many drivers at once bloats the kernel
      log. Also many drivers will stay loaded afterward, bloating the output
      of "lsmod" and wasting memory. Some modules (cs5535_mfgpt which gets
      loaded as a dependency) can't even be unloaded!
      
      If defining char-major-10-130 is needed then it should happen in
      user-space.
      Signed-off-by: NJean Delvare <jdelvare@suse.de>
      Acked-by: NGuenter Roeck <linux@roeck-us.net>
      Signed-off-by: NWim Van Sebroeck <wim@iguana.be>
      Cc: Stephen Warren <swarren@wwwdotorg.org>
      Cc: Mike Frysinger <vapier.adi@gmail.com>
      Cc: Wan ZongShun <mcuos.com@gmail.com>
      Cc: Ben Dooks <ben-linux@fluff.org>
      Cc: Kukjin Kim <kgene.kim@samsung.com>
      Cc: Zwane Mwaikambo <zwane@arm.linux.org.uk>
      Cc: Jim Cromie <jim.cromie@gmail.com>
      487722cf
  2. 28 3月, 2012 2 次提交
  3. 20 9月, 2011 1 次提交
  4. 01 3月, 2011 1 次提交
  5. 18 6月, 2009 2 次提交
  6. 25 3月, 2009 1 次提交
  7. 29 10月, 2008 1 次提交
  8. 06 8月, 2008 1 次提交
    • W
      [WATCHDOG] Coding style - Indentation - part 2 · 0c06090c
      Wim Van Sebroeck 提交于
      This brings the watchdog drivers into line with coding style.
      This patch takes cares of the indentation as described in chapter 1.
      Main changes:
      * Re-structure the ioctl switch call for all drivers as follows:
      	switch (cmd) {
      	case WDIOC_GETSUPPORT:
      	case WDIOC_GETSTATUS:
      	case WDIOC_GETBOOTSTATUS:
      	case WDIOC_GETTEMP:
      	case WDIOC_SETOPTIONS:
      	case WDIOC_KEEPALIVE:
      	case WDIOC_SETTIMEOUT:
      	case WDIOC_GETTIMEOUT:
      	case WDIOC_GETTIMELEFT:
      	default:
      	}
      
      This to make the migration from the drivers to the uniform watchdog
      device driver easier in the future.
      Signed-off-by: NWim Van Sebroeck <wim@iguana.be>
      0c06090c
  9. 21 6月, 2008 1 次提交
  10. 18 10月, 2007 1 次提交
  11. 28 1月, 2007 1 次提交
  12. 03 10月, 2006 1 次提交
  13. 04 7月, 2006 1 次提交
  14. 01 7月, 2006 1 次提交
  15. 08 2月, 2006 1 次提交
  16. 04 2月, 2006 1 次提交
  17. 15 1月, 2006 1 次提交
    • C
      [PATCH] Watchdog: Winsystems EPX-C3 SBC · eed6565f
      Calin A. Culianu 提交于
      This is a 2.6 patch that adds support for the watchdog timer built into the
      EPX-C3 single board computer manufactured by Winsystems, Inc.
      
      Driver details:
      
      This is for x86 only.  This watchdog is pretty basic and simple.  It is
      only configurable via jumpers on the SBC, and it only has either a 1.5s or
      200s interval.  The watchdog can either be auto-configured to start as soon
      as the machine powers up (bad idea for the 1.5s interval!) or it can be
      enabled and disabled by writing to io port 0x1ee.  Petting the watchdog
      involves writing any value to io port 0x1ef.
      
      The only unfortunate thing about this watchdog (and it is not at all
      uncommmon in watchdogs that linux supports) is that it is not a PCI or
      ISA-PNP device and as such it isn't at all probeable.  Either the watchdog
      exists as 2 bytes at 0x1ee, or it doesn't.  Thus, using this driver on a
      machine that doesn't have that watchdog can potentially hang/crash the
      system, etc.  So only use this driver if you in fact are on a Winsystems
      EPX-C3 SBC.
      
      Anyway this driver fits into the already-existing watchdog framework quite
      nicely and I already tested it on my EPX-C3 and it works like a charm.
      Signed-off-by: NCalin A. Culianu <calin@ajvar.org>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      eed6565f