am skip reason: Merged-In I29c5dc48dadf203f04d366823ce5955f37214543 with SHA-1 4db2ff2478 is already in history
Original change: https://android-review.googlesource.com/c/device/google/bluejay-sepolicy/+/2989952
Change-Id: I719ba35cb1de947453bea92287a032eabc9a935d
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I29c5dc48dadf203f04d366823ce5955f37214543 with SHA-1 4db2ff2478 is already in history
Original change: https://android-review.googlesource.com/c/device/google/bluejay-sepolicy/+/2989952
Change-Id: I49c4d8321fb0beab5e530d78c8311fe7ceaeddca
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I08dbe6e19be27bc944766d6ac5c7bb3679215a22 with SHA-1 e109383517 is already in history
Original change: https://android-review.googlesource.com/c/device/google/bluejay-sepolicy/+/2866039
Change-Id: If66f2d8ac6aad2d40a80eb85ac4e7b2f6cc86d88
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I08dbe6e19be27bc944766d6ac5c7bb3679215a22 with SHA-1 e109383517 is already in history
Original change: https://android-review.googlesource.com/c/device/google/bluejay-sepolicy/+/2866039
Change-Id: I2b8b18f8836bf5d8f344dad43558d8e73958f207
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I08dbe6e19be27bc944766d6ac5c7bb3679215a22 with SHA-1 e109383517 is already in history
Original change: https://android-review.googlesource.com/c/device/google/bluejay-sepolicy/+/2866039
Change-Id: I202e62350835cce3c19f2eec43d06eacf81e5fc8
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: Ic9d21331812a576ee81b94d32465b534c1209bd3
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 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 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 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>
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
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
Sometimes the I2C will not be in the usual allowlist, need to
enumerate possible paths to prevent unexpected vibrator behaviors.
Bug: 284969808
Test: full build
Test: Check normal and audio-coupled haptics function
Change-Id: I84772c484022b47cc6db79ecd96b327279f7dfbc
The ffu selinux rule don't work because it's not included by
BOARD_VENDOR_SEPOLICY_DIRS. Move it to bluejay folder and fix the
not working problem.
Bug: 273305600
Test: local build and test on B3
Change-Id: I7c9034b72b237508ecd9893fe86dee51d47c3c88
Signed-off-by: Leo Liou <leoliou@google.com>
