diff options
| author | Ricardo Cerqueira <ricardo@cyngn.com> | 2016-01-26 13:43:39 +0000 |
|---|---|---|
| committer | Zhao Wei Liew <zhaoweiliew@gmail.com> | 2017-02-12 09:58:50 +0800 |
| commit | 524e9723ebaa42a4468faefda646cf042413ae97 (patch) | |
| tree | e06933ebaf7ae893396303f4bdcd820b252f85ba /fmapp2/res/values-uk/strings.xml | |
| parent | 483cfdb4bd0070ff8c33ef129043dc046265defd (diff) | |
| download | android_hardware_qcom_fm-524e9723ebaa42a4468faefda646cf042413ae97.tar.gz android_hardware_qcom_fm-524e9723ebaa42a4468faefda646cf042413ae97.tar.bz2 android_hardware_qcom_fm-524e9723ebaa42a4468faefda646cf042413ae97.zip | |
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:hw.fm.init=0
write /sys/module/radio_iris_transport/parameters/fmsmd_set 0
on property:hw.fm.init=1
write /sys/module/radio_iris_transport/parameters/fmsmd_set 1
This change mirrors the change done for libfm_jni:
Id1997a51d83b82425630f6975f4020d4a2a448c4
Change-Id: Ifddf678398fec2e4bfa9688c044da7d75898e056
Diffstat (limited to 'fmapp2/res/values-uk/strings.xml')
0 files changed, 0 insertions, 0 deletions