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: Id0536ded1035f371adb01ed50bbfbff47914cc6a
Add logbuffer_dual_batt to dumpstate.
Also fix some dual batt related dump pathes.
Bug: 263496320
Test: build pass, no related permission errors.
Change-Id: Ibfd3dfc18acc049052f07246c8d85ae04b4f95f5
Signed-off-by: Wasb Liu <wasbliu@google.com>
Depending on how the device is connected, sysfs path to leds can
have different directory path, to allow backlight controls, we
will provide access to all 'brightness' and 'multi_intensity'
nodes under sysfs directory of USB devices for whitechapel_pro.
Test: manual
Bug: 245506418
Change-Id: I9ca43f1b6d7950c56d08e300b6ac97320982e979
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
