The iphb module uses rtc alarms to wakeup from suspend

The rtc alarm is set to closest maximum time of client wakeup
requests. This allows us to wake up from suspend to serve aligned
timers.

The next (clock/calendar/etc) alarm time is tracked (via listening
to "next_bootup_event" signals from timed) and considered when
setting the rtc alarm time.

When dsme wakes up due to rtc alarm, it takes a wakelock, wakes
up clients with elapsed timers and signals cpu-keepalive wakeup
to mce via asynchronous D-Bus method call. The wakelock will
be released by mce once it has handled the method call.

Since dsme now has /dev/rtc open all the time, it effectively
blocks other processes from updating the rtc time. To overcome
this, iphb module synchronizes rtc time to system time when
a) dsme starts up b) while processing heatbeat wakeups c) when
"settings_changed" signal is received from timed.

Also fixes issues on module startup failure and unload paths.
Skip warning if we can't remove non-existing lockfile
Do not spam the console

Since systemd captures stderr too, this just leads to duplicate
entries in journal.
Add type checking to dbus message parsing functions

Warning message will be emitted if message content differs from
what caller expected.

Removed message_iter_next() since it left the iterator pointing
to the last element instead of moving past it - i.e. you could
read the last element N times without errors.

Also fixed a type mismatch found due to type checking.
Change default logging level from LOG_INFO to LOG_NOTICE
Merge pull request #3 from spiiroin/iphb_uses_rtc

The iphb module uses rtc alarms to wakeup from suspend