| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Simply guard it using BOARD_HAVE_QCOM_FM flag and allow devices
that don't set TARGET_BOARD_PLATFORM to build it anyway.
Change-Id: I574c146d441f3f54186e73ceb105b1c8799f5234
|
| |
|
|
| |
Change-Id: I4dd67cc02b31c43cecb0bdcca9be3c5efd0d8f4d
|
| |
|
|
|
|
| |
* Due to a few moved core jni headers, add the new include path
Change-Id: I9a1c5885d1c14151d2f3303e429081d1fc214a7d
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Not all boards require a firmware download for FM. Set
TARGET_QCOM_NO_FM_FIRMWARE if the device doesn't require
a fw image to run FM
Change-Id: If18650af934f840a54f53fa9474a3341df0e3e68
jni: Confine the firmware-load skipping to the actual loading
Change If18650af934f840a54f53fa9474a3341df0e3e68 removed the
property-setting steps from the initialization routine. Bring it
back, as we may want to use those properties to trigger module
state changes from init. The recommended flow for devices with
the latest IRIS driver is the following:
on property:vendor.hw.fm.init=0
write /sys/module/radio_iris_transport/parameters/fmsmd_set 0
on property:vendor.hw.fm.init=1
write /sys/module/radio_iris_transport/parameters/fmsmd_set 1
Change-Id: Ifddf678398fec2e4bfa9688c044da7d75898e056
|
| |
|
|
|
|
|
| |
This is done tempararily to test FM with O rel
in bringup of new chipset
Change-Id: I6acf159d1bc6ece9e506587e1035b15727240cf2
|
|
|
Implement HAL layer that can be plugged in
with Android FM APP to get fm functionalities.
Change-Id: Id16d37a320fdbacb505ba7ecc431622db17bd4d7
|
