Remove redundant settings in init.rc for cpu scaling_max_freq

The uevent.rc will setup owner/group/permissions in all the conditions
including device boot, cpu hotplugs, and cpu online/offline.
Since ueventd always regenerates uevents at boot, we could remove the
redundant settings in init.rc.

Bug: 230291215
Test: Build and check scaling_max_freq on Cuttlefish and B3 device
Change-Id: I4fcc440f2a950967667f88da574faa501b3e227c
This commit is contained in:
Richard Chang 2022-05-10 06:22:12 +00:00
parent abff801ae6
commit 6f554d1a2a

View file

@ -1135,12 +1135,6 @@ on boot
chown system system /sys/devices/system/cpu/cpufreq/interactive/io_is_busy
chmod 0660 /sys/devices/system/cpu/cpufreq/interactive/io_is_busy
# Assume SMP uses shared cpufreq policy for all CPUs in the same cluster.
# Here is for initial cluster (cpu0...) which is not hot-plugged in most cases.
# The rest of hot-plugged clusters are covered by ueventd.rc.
chown system system /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
chmod 0664 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
chown system system /sys/class/leds/vibrator/trigger
chown system system /sys/class/leds/vibrator/activate
chown system system /sys/class/leds/vibrator/brightness