Update blanking inhibit also during frame buffer suspend/resume

The dim/blank timers are programmed after stable display state is
reached, but the inhibit flags must me evaluated also during the
transitional states.

[mce] Update blanking inhibit also during frame buffer suspend/resume
Block display ON/DIM D-Bus requests during call/alarm/proximity

Powering on display when we have active call or alarms could interfere
with the built-in rules for handling those situations.

And if proximity is covered, the display should turn on only via
power key press.

[mce] Block display ON/DIM D-Bus requests during call/alarm/proximity
Fix whitespace
Keep proximity sensor always enabled

Disabling proximity sensor during display DIM meant it was re-enabled
via sensord just before suspending, without guarantees that it actually
gets enabled before the device suspends.

It is still possible to use run time configuration to disable the
proximity sensor.

[mce] Keep proximity sensor always enabled
Do not turn display on after call ends

MCE has no way of knowing what has happened at UI side during the
call. Whether the display is on or off after the call ends should
be left for lipstick to decide.

[mce] Do not turn display on after call ends
Merge pull request #107 from spiiroin/dbus_display_on

Block display ON/DIM D-Bus requests during call/alarm/proximity
Bump mce version to 1.21.1
Add data pipe for signaling only real user activity

Triggered on actual - non synthesized - power key, double tap
and touch screen events.

The data pipe is used only for triggering, no data is passed
through.
Add support for led patterns that auto-disable on display on

LED patterns configured to use policy=6, will be visible only when
the display is off, and will automatically de-activated when the
display is turned on due to direct activity by the user.

[mce] Add support for led patterns that auto-disable on display on
Communication LED patterns use auto-disable policy

Missed call, SMS etc led patterns are de-activated when the user
unblanks the display device via power key or double tap.

[mce] Communication LED patterns use auto-disable policy
Add runtime config entry for CSD led pattern

To silence complaints of not having it.
Reduce severity of sensord not available diagnostics

These will trigger on mce startup before dbus name query finishes.
Do not warn about libhybris missing fb power controls

It is normal that direct power control is not available and it is
done indirectly via early suspend.
Silence diagnostic output accidentally left at WARNING level

These might be interesting during debug run, but not by default.
Merge pull request #108 from spiiroin/type_6_led

Add support for led patterns that auto-disable on display on
Merge pull request #109 from spiiroin/silence_debug

Tone down too agressive logging
Bump mce version to 1.22.0