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: Ifbb212707fa7eba551b77e061a0ad4285d80bb97
Set /dev/acd-audio_rtp_rx and /dev/acd-audio_rtp_tx permissions
to system:radio so that ImsMedia can use them for VoWIFI.
BUG: 259874554
Change-Id: Ie5e0500b09c91b450f55d5748fd7e9abd6b65510
Signed-off-by: brucepo@google.com
The nodes /dev/acd-audio_rtp_rx and /dev/acd-audio_rtp_tx permissions
should be set system:audio so that ImsMedia can use them, for VoWIFI.
BUG: 259874554
Change-Id: I245bd3f2539ba30cb557525eaf95b300efff5d37
Signed-off-by: brucepo@google.com
dock-defend is enabled in kernel code.
Bug: 262322247
Test: dock-defend is enabled by default
Change-Id: Ib7c7381f9d7d6d818e034911115e8c9045d5d0b6
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>
Move permissiion setting for logbuffer to eraly-boot to avoid timing
problem.
Bug: 260678111
Test: Ensure that the owner of necessary logbuffers is system/system
Change-Id: I6a3a48ce31e95b8b781c8a90237c10aa7a0c4210
Signed-off-by: Wasb Liu <wasbliu@google.com>
For charging efficiency certification swap CPU6 with CPU4 while in
off-mode charging.
Bug: 260019919
Test: measure power consumption in charger mode
Change-Id: Iffccde0c3161e3fa4768d5f7c7ec2212dbab1a73
Signed-off-by: Jack Wu <wjack@google.com>
add persist battery folder for BatteryDefender
Bug: 258535661
Bug: 260878511
Test: confirm the BatteryDefenter feature works fine
Change-Id: I5e2925d4fe188e0a104f2b20e7b230d60d7f8039
Signed-off-by: Wasb Liu <wasbliu@google.com>
Signed-off-by: Ken Tsou <kentsou@google.com>
(cherry picked from commit a573337875)
add persist battery folder for BatteryDefender
Bug: 258535661
Test: confirm the BatteryDefenter feature works fine
Change-Id: I5e2925d4fe188e0a104f2b20e7b230d60d7f8039
Signed-off-by: Wasb Liu <wasbliu@google.com>
Since retry times of kernel driver are 24 during USB enumeration,
the total time of bad USB enumeration will waste 48 seconds.
This patch will reduce the timeout from 2 seconds to 500ms, so the
total time is changed to 12 seconds.
(cherry-pick from commit dd9bb5578cd197b44f32c0c19aca79610b5bdd54)
Bug: 256100001
Test: the timeout value is 500
Change-Id: I6c30e3c9168242f5c22443cbd5622892617e0520
Signed-off-by: Puma Hsu <pumahsu@google.com>
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)
Similar CL: ag/20102346
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: I17031179b7c1e56b0e841d4047859006d005fd21
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
Increase watermark_scale_factor to 200 to better handle
burst memory allocation.
Bug: 251881967
Test: boot
Signed-off-by: Martin Liu <liumartin@google.com>
Change-Id: Ibe663456671892f2ec0e5e20e592b80c96bd371b
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: Ibb54e7c0b171f355ee2b71099533afe15ba09e99
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: I872caa1f54fe8e17bcbcc5bc9407d0da21e83bca
Instead of relying on vendor.thermal.link_ready property to gate write
to BCL's SYSFS node, adding mitigation ready SYSFS so that writes to
BCL's SYSFS node would not cause NULL pointer dereference.
Bug: 249130916
Test: Confirm property vendor.brownout.mitigation.ready is set
Signed-off-by: George Lee <geolee@google.com>
Change-Id: Ic643a07ddb657cfc7e22537d5d25d0d99324e31c
Test: Tested with tablet with dock. Userspace is able to read
and clear sysfs node successfully
Bug: 218802317
Signed-off-by: Prasanna Prapancham <prapancham@google.com>
Change-Id: Ice5ec79d912f154203a548c6c40470952d806289
A0 and B0 chips have different performance characteristics when it comes
to the hypervisor because B0 waits for SysMMU_SYNCs to complete during
every memory ownership transaction.
Set debug.hypervisor.metrics_tag=hwrev_a0 on PROTO1.x and EVT1.0
devices. EVT1.1 and later are B0 and benchmarks are representative of
production devices. This is only done on userdebug/eng builds.
Test: 'getprop | grep hypervisor' on A0/B0 devices
Change-Id: I0c81a0e4706a13cd63358de23048087a9190b9da
As part of pa/2288829, this node becomes unsupported.
Prevents -ENOTSUPP errors when trying to write to Mali's ifpo sysfs
node.
Test: Boot to homescreen
Bug: 247571932
Change-Id: I0b579728a5b2a4355d648020113dda0592f904aa
Signed-off-by: Jeremy Kemp <jeremykemp@google.com>
