Vendor sched procfs path hierarchy gets updated in kernel.
Update the paths in powerhint json file to match the change.
Bug: 289151587
Test: Uibench ab test
Change-Id: I08b099b8267a8744ec50175d3284fb48a404c285
am skip reason: Merged-In Iee0db5d439442fe7c689aaecfa214ea90dbe76b4 with SHA-1 54a353165c is already in history
Original change: https://android-review.googlesource.com/c/device/google/bluejay-sepolicy/+/2776401
Change-Id: Ic9d21331812a576ee81b94d32465b534c1209bd3
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Iecbf06a898f2c57da1ec29f6e5eb35241a3ec4f3 with SHA-1 0ea630f587 is already in history
Original change: https://android-review.googlesource.com/c/device/google/bluejay/+/2775835
Change-Id: I55b7b127458cd9be84243c05c6e92c2b0cc0bef9
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Iee0db5d439442fe7c689aaecfa214ea90dbe76b4 with SHA-1 54a353165c is already in history
Original change: https://android-review.googlesource.com/c/device/google/bluejay-sepolicy/+/2776401
Change-Id: I9356b4a7581fd56e0905e2e69f93bc41cb1ac3ca
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Iecbf06a898f2c57da1ec29f6e5eb35241a3ec4f3 with SHA-1 0ea630f587 is already in history
Original change: https://android-review.googlesource.com/c/device/google/bluejay/+/2775835
Change-Id: I21193dd2a51d86c0c5ed04d48c188f906557be7c
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Iee0db5d439442fe7c689aaecfa214ea90dbe76b4 with SHA-1 54a353165c is already in history
Original change: https://android-review.googlesource.com/c/device/google/bluejay-sepolicy/+/2776401
Change-Id: Iee6d4902d5ae737a4f03d17f5a842187fdedaacf
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Iecbf06a898f2c57da1ec29f6e5eb35241a3ec4f3 with SHA-1 0ea630f587 is already in history
Original change: https://android-review.googlesource.com/c/device/google/bluejay/+/2775835
Change-Id: I4d0f567451d80160a5db8595f2e9151393bfdda9
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Iee0db5d439442fe7c689aaecfa214ea90dbe76b4 with SHA-1 54a353165c is already in history
Original change: https://android-review.googlesource.com/c/device/google/bluejay-sepolicy/+/2776401
Change-Id: I2e3756fa1b0690963fd5c9bcd86b0aeb5cd6c71b
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Iecbf06a898f2c57da1ec29f6e5eb35241a3ec4f3 with SHA-1 0ea630f587 is already in history
Original change: https://android-review.googlesource.com/c/device/google/bluejay/+/2775835
Change-Id: Iaf4888b74fd9817762fe4cf0d3b3d372c8affd9e
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Iee0db5d439442fe7c689aaecfa214ea90dbe76b4 with SHA-1 54a353165c is already in history
Original change: https://android-review.googlesource.com/c/device/google/bluejay-sepolicy/+/2776401
Change-Id: If26733c497a61f2d165057ee18d4c3f18c228149
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Iecbf06a898f2c57da1ec29f6e5eb35241a3ec4f3 with SHA-1 0ea630f587 is already in history
Original change: https://android-review.googlesource.com/c/device/google/bluejay/+/2775835
Change-Id: I7882c11a29328f5077626b90364f28562b969df2
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
The i2c-7/7-0043 label is shared with both i2c-7/i2c-cs40l25a and
i2c-7/i2c-cs40l26a nodes. To make it clear that these all are related,
let's move i2c-7/i2c-cs40l26a to gs101-sepolicy and have all the gs101
vibrator policy labels together.
Test: build on b3 and verify i2c nodes on r4
Bug: 291606723
Change-Id: I58be5961120c0ec5597a947c5ab6caa52aeb7bce
Add DISPLAY_CHANGE hint for display layout change due to rotation or
switching between inner and outer panels.
Bug: 298150450
Test: build pass
Change-Id: I397334d53c89b65af54e91455b76f0036754738e
If auto rotation is enabled, it will trigger LAUNCH hint while
camera is running if device rotates, which could limit camera_hal
tasks to little cores. So, disable it first until there is a new
hint for the rotation event.
Bug: 297273578
Test: build pass
Change-Id: Ib92bb1ee5833924a1e34b8c91e15f6cb26a0e645
This change needs to be merged with the corresponding kernel change that
sets the i2c bus aliases correctly to match the existing v5.10 bus
probe ordering.
To verify the sepolicy labeling doesn't change, run the below commands
and diff the stdout on builds with and without the changes. For extra
credit, verify the nodes are labeled the same when upgrading the kernel
to v6.1 (with the correct i2c aliases to match the existing policy):
acpm_bus_array=("acpm_mfd_bus@17500000" "acpm_mfd_bus@17510000")
for bus in ${acpm_bus_array[@]}; do
adb shell ls -ZR /sys/devices/platform/${bus}/i2c-*;
done
bus_array=("10960000" "10970000" "10d50000" "10900000")
for bus in ${bus_array[@]}; do
adb shell ls -ZR /sys/devices/platform/${bus}.hsi2c/i2c-*;
done
Test: verify on b3
Bug: 291606723
Change-Id: I36e41d7e2379b731c2092a679dc4e4042e0d3651
This reverts commit 89f99fd401.
Reason for revert: With stream use case VIDEO_CALL + logical stream power is well within the permissible limit of 3W.
Bug: 300166920
Change-Id: I2d764fdf2dc3124d3f60513c5e76108b52ed8f7b
