Use a moderate boost instead of fmax out of thermal constraints.
Bug: 284039815
Test: boot ab tests
Change-Id: I5787a62ca26f9e128e73c7bf9d60c4d2216d5e0c
rt_uclamp_min and sf_uclamp_min have been made redundant in Pixel by
ADPF for sf, so we are just going to remove them outright rather than
worrying about overriding them later
Bug: 285248880
Test: manual
Change-Id: I5abdf2e16dd769f1fece28a1dc630a9a8e3ddd14
Background:
* Not all secure storage files had the correct ownership transitions.
Bug: 280325952
Test: Changed permissions and confirmed user transitions
Change-Id: I306209fe04256ca48ea7b6246a6c8718a29b149b
Signed-off-by: Donnie Pollitz <donpollitz@google.com>
Add temperature residency reset path
chown to system to reset from pixelstats
Bug: 193833982
Test: Local build and verify statsD logs
adb shell cmd stats print-logs && adb logcat -b all | grep -i 105045
Change-Id: Id73badfb8f8ff97a1a75b0544d3e1457ad0e2f84
With bg group throttle set to 30 percent of cpu capacity, we need to
relax background cpuset as well.
Bug: 201260585
Test: value set as expected.
Change-Id: I4a4dca2d077386d58fa06b6445e040906818c7dd
The UVC gadget requires some setup in configfs before it can be used by
the gadget HAL. This CL adds that setup to usb specific init.rc file.
Currently, UVC is setup to advertise mjpeg streams at 720p and 1080p at
60, 30, 24, and 15 fps each.
Bug: 242344221
Test: Manually tested that UVC is correctly set up on boot.
Change-Id: Ic597e5a1ec1bd31d73899e5a885f8cb0d0753bd5
This is required so Lyric is able to talk to smfc driver
Bug: 257084044
Test: ls -la /dev/video12 shows proper file permissions
Change-Id: I181c8f8d1647d91d092d83887f28bef640e3b464
dock-defend is enabled in kernel code.
Bug: 262322247
Test: dock-defend is enabled by default
Change-Id: Ibbd83fc2442e2a6d68d7f506ccd29d452947931c
Signed-off-by: Jack Wu <wjack@google.com>
the file node was removed so also remove these
dummy setting
Bug: 260806701
Change-Id: I23044f7f32cf4b2b2cc93205ec5751525f05ee7f
Signed-off-by: Chungkai Mei <chungkai@google.com>
To enhance system performance and save power, chagne idle governor to TEO.
Test: boot to home
Bug: 175800838
Signed-off-by: Chungkai Mei <chungkai@google.com>
Change-Id: I591c1ff8d0c9ed8d5a3b4861c9c5b715ed1c3eae
The folder will be used for place the necessary libraries that used by
catpipe functions.
Bug: 249274299
Test: build pass, check the folder with user build
Change-Id: I275af8e716de8dc433f0b43afb20866a9eff8642
1. If the device is powered off by users, boot to charger mode
after plugging in the charger. Otherwise, boot to OS.
2. Disable this feature by default
3. Enable this feature by persist.sys.boot.charger_mode.enable=1
Bug: 251680171
Test: can enter charger mode from power off
Signed-off-by: Jack Wu <wjack@google.com>
Change-Id: Ibd1f88c961d884d8e6f9d0019cf550fd0de1192d
To support input device lights manager feature in frameworks, provide
sysfs node access to system server process.
DD: go/pk_backlight_control (For keyboard backlight control for external
keyboards)
Kernel provides a standardized LED interface to expose LED controls
over sysfs: https://docs.kernel.org/leds/leds-class.html
The feature will be provided for devices with kernel sysfs class led
support and vendor kernel driver for input controllers that do have
lights. The kernel sysfs class led support is a kernel config option
(LEDS_CLASS), and an input device driver will create the sysfs class
node interface.
By giving system_server the access to these sysfs nodes, the feature
will work on devices with the kernel option and kernel input/hid driver
support. We do use CTS tests to enforce the kernel options and the
input device drivers.
What's already supported:
- We already expose paths for UHID based LED nodes which covers all
bluetooth based peripherals that have custom vendor drivers to expose
LED sysfs nodes. (see CL aosp/1546377)
What's included in this CL:
- Exposing paths for sysfs nodes for external USB based devices that
expose LED nodes using vendor specific drivers using standard LED
interface provided by Kernel
- We are using specific paths for USB devices instead of
/sys/class/leds to avoid giving access to system LED nodes that would
also appear under /sys/class/leds (see discussion in aosp/1546377)
NOTE: Light HAL should never touch the HID device sysfs light, as the
light HAL only defines a number of lights supported
(https://android.googlesource.com/platform/hardware/interfaces/+/master/light/2.0/types.hal)
but not include input device lights, so we shouldn't have conflict
for managing these lights.
NOTE: External keyboard backlight is different for HAL light type
KEYBOARD which is for devices with attached keyboards.
Test: manual
Bug: 245506418
Change-Id: I2e9f3cbce55f3f894ca346bafa5ded280086a3ca
