Laurent Vivier 9491e9bc01 i6300esb: remove muldiv64() ... Originally, timers were ticks based, and it made sense to add ticks to current time to know when to trigger an alarm. But since commit: 7447545 change all other clock references to use nanosecond resolution accessors All timers use nanoseconds and we need to convert ticks to nanoseconds, by doing something like: y = muldiv64(x, get_ticks_per_sec(), PCI_FREQUENCY) where x is the number of device ticks and y the number of system ticks. y is used as nanoseconds in timer functions, it works because 1 tick is 1 nanosecond. (get_ticks_per_sec() is 10^9) But as PCI frequency is 33 MHz, we can also do: y = x * 30; /* 33 MHz PCI period is 30 ns */ Which is much more simple. This implies a 33.333333 MHz PCI frequency, but this is correct. Signed-off-by: Laurent Vivier <lvivier@redhat.com>		2015-09-25 14:52:17 +02:00
..
Makefile.objs	s390x/watchdog: introduce diag288 watchdog device	2015-06-11 17:45:49 +02:00
watchdog.c	watchdog: Add new Virtual Watchdog action INJECT-NMI	2015-06-11 17:45:50 +02:00
wdt_diag288.c	watchdog/diag288: correctly register for system reset requests	2015-07-14 19:10:03 +02:00
wdt_i6300esb.c	i6300esb: remove muldiv64()	2015-09-25 14:52:17 +02:00
wdt_ib700.c	vmstate: accept QEMUTimer in VMSTATE_TIMER*, add VMSTATE_TIMER_PTR*	2015-01-26 12:22:44 +01:00