The device under /dev/byte-cntr1 should be with permission
root diag.
Change-Id: Id5e45789995b706360742253fc93dc2304f70442
Signed-off-by: chrisl7 <wandersonrodriguesf1@gmail.com>
For now, this is for 5.10 only. 5.4 and others may upgrade
at some point. Until then, 5.4 uses media-5.4
and pre-5.4 uses media-legacy.
Change-Id: I7dccc184f81d5b1733852397c59d36ca0c3489ca
Blobs are updated to LA.VENDOR.1.0.r1-16000-WAIPIO.QSSI13.0
Configs are updated to to LA.VENDOR.1.0.r1-15600-WAIPIO.0
This does not work yet on pre-5.10 SoCs.
Those SoCs will use the perf-legacy
component until that is fixed (or indefinitely
depending on the complexity of the fix).
Note: I am aware that there are conditions in perf
that only apply to legacy and conditions in perf-legacy
that only apply to perf. We need to nail down the
supported targets before I can clean up completely.
Change-Id: I7925042da82fac6e5353c1a4b1660b3ca9e128d7
Currently, this only works on 5.4 and 5.10,
so pre-5.4 devices will stay on 5.4
binaries for the time being. This
renames components to the below:
adreno: 5.4/5.10 (LA.VENDOR.1.0.r1-16000-WAIPIO.QSSI13.0)
adreno-6xx-legacy: 4.9-4.19 (LA.UM.9.14.r1-20200-LAHAINA.QSSI13.0)
adreno-5xx: 3.18/4.4 (LA.UM.10.6.2.r1-01600-89xx.0)
Change-Id: I892e3b2e3c5c1d6d95d7c0ab4674075aa5546a3a
Maintainers should not need to manually select
the appropriate variant of a component for
their SoC. We know what does and does not
work for an SoC. Automatically select
the necessary component. This allows us
to be more flexible when new SoCs launch
and components may need to be renamed or
refactored.
Change-Id: Ibe9815ba7f70ec760c7b0cbd3771707af2e59854
[1] - The old definition wasn't working, and init post_boot.sh and early_boot.sh
was being used on legacy devices, which shouldn't happen.
[2] - Yes I've tried other ways to pin but only this worked.
Change-Id: I2b3f41b34ba6297fe1019773c2e7d5fd7d17d00c
Signed-off-by: chrisl7 <wandersonrodriguesf1@gmail.com>
[1] - In Android 13 this is set via properties
Change-Id: Ic610b67c9f4e5d834f54d992565769240b3e6451
Signed-off-by: chrisl7 <wandersonrodriguesf1@gmail.com>
mediserver is looking for QSPM hwservice to initiate adreno profile processing.
libadreno_app_profiles checks for QSPM hwservice access to get memory pointer from QSPM
for adreno profile processing.
So it is required for us to allow mediaserver access to fetch QSPM HAL service.
This fixes following warning
E SELinux : avc: denied { find } for interface=vendor.qti.qspmhal::IQspmhal sid=u:r:mediaserver:s0 pid=1437 scontext=u:r:mediaserver:s0 tcontext=u:object_r:vendor_hal_qspmhal_hwservice:s0 tclass=hwservice_manager permissive=0
W Adreno-AppProfiles: Could not find QSPM HAL service. Skipping adreno profile processing.
Change-Id: If0460b4bf7e8981aa98521824b34c1326f243c15
Signed-off-by: UtsavBalar1231 <utsavbalar1231@gmail.com>
Signed-off-by: Omkar Chandorkar <gotenksIN@aospa.co>
Signed-off-by: chrisl7 <wandersonrodriguesf1@gmail.com>
- devices like alioth ship with vendor_boot on kona
Signed-off-by: Omkar Chandorkar <gotenksIN@aospa.co>
Change-Id: Icc0ca6d1eaa2602e0ba927a85e1c639ae30c5a5f
system-background should only include efficiency cores
and restricted should do the same in order to save
power while the screen is off. Copy system-background
CPUs instead of hardcoding to account for platforms
with varying numbers of efficiency cores.
Change-Id: I3a46190a2fa76eb1e9061a605c6a2e74006975de
init.qti.kernel.rc waits for vendor.all.modules.ready to be
set before finishing init. This is never set when there
are no modules present. Adding vendor_modprobe_no_modules.sh
to unconditionally set vendor.all.modules.ready and boot.
Change-Id: I59f9ae8408f1341469ab7dd02c2ad1222f711fae
This fixes ANDR-PERF-CLIENT-SYS not being accessed by flipendo
E SELinux : avc: denied { find } for interface=vendor.qti.hardware.perf::IPerf sid=u:r:flipendo:s0:c199,c256,c512,c768 pid=21903 scontext=u:r:flipendo:s0:c199,c256,c512,c768 tcontext=u:object_r:vendor_hal_perf_hwservice:s0 tclass=hwservice_manager permissive=0
E ANDR-PERF-CLIENT-SYS: IPerf:: Perf HAL Service 2.2 is not available.
Change-Id: I42a582864309f17e183e10baf04cbd01eba04913
Signed-off-by: UtsavBalar1231 <utsavbalar1231@gmail.com>
Signed-off-by: Omkar Chandorkar <gotenksIN@aospa.co>
This allows legacy devices to keep working with
new init without increasing maintenance or affecting
more recent SoCs.
Change-Id: Ia66fa4b044bc9d7f2fabe9a0f6e4b18f6f1189e9
Remove init.qcom.factory.rc because it is not needed.
init.kernel* and init.qti.* are from LA.VENDOR.1.0.r1-15600-WAIPIO.QSSI13.0
Change-Id: Ia16d51b80f402634bd918314ee3cf7691421668d
Qualcomm removed them at
"removing some of the target dir from the component.", which
we reverted.
Change-Id: If2d407c03c112099b67bcd88d2ec4b31c0425642
These were added back at 'Revert "removing some of the target dir from the component."',
however, taro uses the taro directory.
Change-Id: Ide946d9db03f1f2ffbabab0203090238b18475f3
Alexander Koskovich
Vishalcj17
Sarthak Garg
Yuanfang Zhang
Qi Jin
Vinoth Jayaram
chrisl7
Jyotiraditya Panda
Arian
Jake Weinstein
Pullakavi Srinivas
Omkar Chandorkar
UtsavBalar1231
Sandeep Singh
kocolin
Himanshu Agrawal
PainKiller3