Make way for kalama. The new naming matches
Qualcomm's branching strategy, which notes
the launch version of the SoC.
adreno-5xx-legacy is unchanged because
it predates GRF.
adreno-r should be used for Android 11 GRF
platforms, such as msmnile, kona, and lahaina.
adreno-s should be used for platforms launching
with Android 12, such as taro and parrot.
adreno-t (coming soon) should be used for platforms
launching with Android 13, such as kalama.
Note: adreno-t does not seem to support Adreno 6xx,
so platforms that upgraded kernel versions and
launching Android versions, such as kona and bengal
on 5.15 may use adreno-s, which is consistent with
Qualcomm's releases as well.
Change-Id: Id454e3b742622e69747ab3382b5b686dac4484ff
If either a device needs to override the variant in
device tree for a specific reason or all devices
on a particular kernel version and SoC
need to override the variant in common.mk,
they can do that.
USE ONLY IF YOU KNOW WHAT YOU'RE DOING
Change-Id: I2fa57d544956966b18b6d16fba056bb225e1a898
[cyberknight777: Use conditional assignment operators]
Signed-off-by: Cyber Knight <cyberknight755@gmail.com>
[1] - Qualcomm is using the exact same hal and GPS blobs for all SoC with A11 GRF, so we will define this as Common
[2] - Use HAL and Blobs from LA.UM.9.15.2.r1 because it updates faster than other platforms
[3] - HAL and blobs from LA.UM.9.15.2.r1-06600-KAMORTA.QSSI-13.0
Change-Id: Ia4c40020ff9155f178fd52e307ef278806f40046
Signed-off-by: chrisl7 <wandersonrodriguesf1@gmail.com>
* Based upon LA.UM.9.14.r1-21000-LAHAINA.QSSI12.0
LA.QSSI.13.0.r1-09700-qssi.0
Change-Id: I7085e5686c6cc2d63a62f84557bc1bac3d579e67
Signed-off-by: electimon <electimon@gmail.com>
* Does not work on A13 anymore
* legacy devices should use AOSP WFD instead.
Change-Id: I05b834b39720bb2b224eaaab24bb76cf9136ddb9
Signed-off-by: Jprimero15 <jprimero155@gmail.com>
[1] - C2 audio service is requesting AGM and PAL services in the logs, and this is only found in audio-ar.
Then revert bengal to media-legacy
Change-Id: Iab5eb30f8c79976ae4f4a768da4a9228a7d6d1db
There are different tags being used in different
components, hence this doesn't makes much sense.
Also, the mentioned tags are outdated with respect
to what the components are using at the moment.
Change-Id: Ie6d60343e2beec37ac0c9fe911bc12a26146bcee
* Some modules are merged in order to unblock projects
as well as to allow more visibility and therefore
subject it to more testing. This change allows
users to select all components as well as modules
not enabled in all because they are under testing.
Change-Id: Id027e407b1eec1c5265b725c839cda18b6cb83b2
Signed-off-by: electimon <electimon@gmail.com>
* Based upon LA.UM.9.16.r1-09800-MANNAR.QSSI12.0,
qseecomd module provides qseecomd stack for devices
on >5.4 kernels using DMABuf.
[TODO: Evaluate enabling this component on ALL]
Change-Id: I3b1c7a95193e296a173dc6e628e42ab66a96483f
Signed-off-by: electimon <electimon@gmail.com>
* Based upon LA.UM.9.12.r1-13500.01-SMxx50.QSSI12.0,
keymaster module provides keymaster/gatekeeper blobs
specifically version 4.1 which is compatible with devices
that use 4.0.
[TODO: Evaluate enabling this component on ALL]
Change-Id: I216b047ce7c3bcab5ba25eeb8c359c0d4cee5865
Signed-off-by: electimon <electimon@gmail.com>
* Based upon LA.UM.9.12.r1-13500.01-SMxx50.QSSI12.0,
This module contains *dsprpcd services with
a selector to enable the correct services
[TODO: Evaluate enabling this component on ALL]
Change-Id: I79aaa8fd359ba4c8450f5896b9cfb873cec1f468
Signed-off-by: electimon <electimon@gmail.com>
* Based upon LA.UM.9.12.r1-15100-SMxx50.QSSI13.0,
This module contains userspace charging blobs
typically provided to OEMs as prebuilts.
[TODO: Evaluate enabling this component on ALL]
Change-Id: I380ac70e40bc7dc8317d13ed7bee01e8c1125a68
Signed-off-by: electimon <electimon@gmail.com>
[1] - Everything being used here is also cane enabled on SM8450 audio hal.
Change-Id: Iee0cb5cd7dd872f72b5b9ebe8244f9910146c990
Signed-off-by: chrisl7 <wandersonrodriguesf1@gmail.com>
* NXP NFC is becoming increasingly popular as an alternative
to NQ NFC, especially on the PN5xx platform. Add support
for disabling NQ NFC in favor of NXP NFC. Rename QTI
component to reflect this change.
Change-Id: I63dd29357943d6e5a31e479e98e6ff79df9b5124
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
Jake Weinstein
chrisl7
electimon
Jprimero15
Kunmun
Alexander Koskovich
Omkar Chandorkar
Roman Rihter
Kunmun
Adithya R
Omkar Chandorkar
Vishalcj17