init [1/4]: set permissions on governors sysfs nodes

1. interactive
2. ondemand
3. assume smp uses shared cpufreq policy for all CPUs

also, set permission for boostpulse
it will fix some permission issues like:

E/S5PC110 PowerHAL(  482): Error writing to boostpulse: No such device
E/S5PC110 PowerHAL(  482): Error opening interactive boostpulse interface: Permission denied
E/S5PC110 PowerHAL(  495): Error opening /sys/devices/system/cpu/cpufreq/interactive/timer_rate: Permission denied

Signed-off-by: Humberto Borba <humberos@gmail.com>
Change-Id: I581aaa1daf2ba5911e89398a4f8a1567fd6569c9
init [2/4]: set permissions on schedulers sysfs nodes

Signed-off-by: Humberto Borba <humberos@gmail.com>
Change-Id: Ib7653a008bbeb978ea1bca77cb76ab4e609d48b6
init [3/4]: allow system to modify ksm control files

Signed-off-by: Humberto Borba <humberos@gmail.com>
Change-Id: Id4e70992f34c8039c06ab1131b9cc2195f6e3b63
init [4]: set permissions on notify_on_migrate node

 * Used by PowerHAL

Signed-off-by: Humberto Borba <humberos@gmail.com>
Change-Id: Ifbf58c145522d82d220fbae39a6b7319971ecbb5
vendor/omni: minor code cleanup

Replaced tabs with four space, and alpabetized packages.mk

Change-Id: I846be29a6dfff81e01dacdf643846651d34a398a
Merge "vendor/omni: minor code cleanup" into android-4.4
Merge changes Ifbf58c14,Id4e70992,Ib7653a00,I581aaa1d into android-4.4

* changes:
  init [4]: set permissions on notify_on_migrate node
  init [3/4]: allow system to modify ksm control files
  init [2/4]: set permissions on schedulers sysfs nodes
  init [1/4]: set permissions on governors sysfs nodes
Omni: Changes default Apn for XL-Axiata Indonesia

Change-Id: I98d1f91c446e43dcfc5149be8b8eace7f1b2e14c
Mackay ROM

Change-Id: Ie881215e05451ef85cd72411b6f57c0b13faf0bd
Changed package selection

Change-Id: I22e41eff8928cce4d75095370b10fcbbb46b6ce8
sepolicy[1/2]: Start OmniROM Common sepolicy

Rather than having to maintain out of tree changes, it is often
easier to maintain a hiearchy of changes, starting with the vendors
common config file. From there, inheriting products can pick up a base
and start to add or remove certain bits from it, making use of the
BOARD_SEPOLICY_* functions documented in external/sepolicy/README.

appended line as example below:
line 1 "vendor/omni/sepolicy/file_contexts"

It requires: https://gerrit.omnirom.org/#/c/4795/

Signed-off-by: Humberto Borba <humberos@gmail.com>
Signed-off-by: William Roberts<wroberts@tresys.com>
Change-Id: I13244e5c6fc64ef5c3f94ff2bc03fcbc96619490